Messages

1

Zaurus - pdaXrom / latex

« on: January 10, 2005, 09:00:13 pm »

Yes, most likely an incompatibility due to the changes in fp-emulation. If recompiling is not an option, a quick and dirty solution would be to put the old libs from v1.0.5 (libc, libm, maybe libX*, etc) into a separate directory and make LD_LIBRARY_PATH wrappers (tiny shell scripts setting LD_LIBRARY_PATH to this dir and then exec'ing the true binaries) for the misbehaving apps.

2

Zaurus - pdaXrom / latex

« on: January 10, 2005, 01:02:38 pm »

Yes, my site is permanently down (hardware died), sorry for that. ScottYelich was kind enough to host a copy on his site. Note that this LaTeX setup has not been modified since May 2004 and has only been tested under pdaxrom 1.0.5. Good luck.

3

Zaurus - pdaXrom / Native SDK

« on: September 08, 2004, 03:37:01 pm »

And by the way, people, you should know that the compilation process creates some intermediate temporary files in /tmp, and that adds some flash wearing. It may be desirable to mount /tmp as tmpfs, dunno though if the RAM would be enough.

Or use gcc -pipe . Maybe we should put -pipe right into the onboard compiler's specs file so that it is always on.

4

Deals and Great Z Buys / KINGMAX 1GB SD 60X HighSpeed for $111 Shipped.

« on: September 06, 2004, 08:51:17 pm »

Just found this post about speed...I don't understand it as I thought most cards are 2MB/Sec...so perhaps someone can shed light as to why the "write speed is (considered) terrible"

QUOTE:

write speed is 6.6 Mbps
read speech is 180Mbps

The read speed is excellent, but write speed is terrible. "

Mbps are Mega-bit per second, not Mega-Byte.  

5

Zaurus - pdaXrom / Just got back from DefCon, idea for pdaXrom

« on: August 03, 2004, 10:26:48 am »

Bestcrypt  (www.jetico.com) runs nicely under pdaXrom 1.0.5.  I didn't notice any performance problems. I keep some compiled binaries here but since this is sensitive stuff you may wish to compile it yourself from original sources. There is no documentation in this binary package so you need to know what you are doing (mknod the devices, put the modules and everything else at reasonable places, run depmod -a, modprobe ..., maybe set up some startup script, etc). Note that this is commercial software.

6

Qt/Qtopia / running duke3d : "undefined symbol: __muldi3"

« on: July 05, 2004, 08:07:50 pm »

No need to build libgcc_s.so. Does the linking step find the muldi3 thing with -lgcc ?

7

Qt/Qtopia / running duke3d : "undefined symbol: __muldi3"

« on: July 05, 2004, 03:07:21 pm »

If there is a libgcc_s.so.1 somewhere in your arm devel tree, make a symlink to libgcc_s.so and try linking with -lgcc_s again. Otherwise try linking with -lgcc .

8

Qt/Qtopia / running duke3d : "undefined symbol: __muldi3"

« on: July 05, 2004, 10:26:12 am »

It is part of libgcc. Try adding -lgcc_s to the LIBS.

9

Zaurus - pdaXrom / New pdaXrom installer (to have just Root partition)

« on: June 28, 2004, 10:47:30 pm »

Is there anyone who has the current installer (v 0.3)? Please put it online...

I still have a copy. Use at your own risk.  

Edit: Hmm, the stupid board does not seem to allow the upload of files that are not images ("You cannot upload this type of file"). I've put a copy here.

10

Zaurus - pdaXrom / HOW TO: Brightness Buttons

« on: June 23, 2004, 03:08:53 pm »

Looks like the attachement didn't survive the forum transition. I have temporarily placed a copy here for download.

11

Zaurus - pdaXrom / What do you prefer...

« on: June 16, 2004, 09:33:10 am »

... I am complete linux-newbee but I am highly interested to give something from me to zaurus community but in that case I would be capable , probably after many mistakes to compile programs for zaurus.

It would be much more helpful if people (and complete newbies in particular) would spend their efforts to exhaustively test and validate applications, not to blindly compile new ones and making them available untested. After all, an application that can be compiled by a newbie can be compiled by anyone in a matter of minutes so what\'s the point? It is not helpful to clutter the distributions with loads of untested packages that may or may not work, and stripping essential documentation, man pages, configure options and other information to rebuild the package does not help either. It is nice and appreciated that people want to give something back to the zaurus community, but submitting your own untested compilations is not the best way to do it.

12

OpenZaurus/Opie/Qtopia / how to cross compile those ordinary ./configure programs?

« on: June 16, 2004, 08:28:47 am »

If the configure script is less well behaved (still runs gcc instead of arm-linux-gcc etc), a common trick is PATH=/usr/local/arm-linux/bin:$PATH ./configure --host=...

...

i have tried to run
$ PATH=/usr/local/tools/linux/arm/gcc-3.2.2/arm-linux/bin:$PATH ./configure --host=arm-linux

reating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... yes
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for c++... c++
checking whether the C++ compiler (c++  ) works... yes
checking whether the C++ compiler (c++  ) is a cross-compiler... yes
checking whether we are using GNU C++... yes

it did configure successfully, then i type
$ make

it did make successfully, then i type
$ file \"application_name\"

it showed \"ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped\"

instead of

\" ELF 32-bit LSB executable, ARM, version 1 (ARM), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), not stripped
\"
which means the application is run under PC instead of ARM, any ideaS?

If you configure with

PATH=/usr/local/tools/linux/arm/gcc-3.2.2/arm-linux/bin:$PATH ./configure --host=arm-linux

you must make with

PATH=/usr/local/tools/linux/arm/gcc-3.2.2/arm-linux/bin:$PATH make

or it will not work for obvious reasons. Sorry not to have included this above.

I has nothing to do with environment variables (other than PATH). A properly configured compiler (cross or native) does not need any environment variables to be set.

13

Deals and Great Z Buys / Simpletech Pro-X 256MB SD $54 shipped (no MIR)

« on: June 09, 2004, 12:22:43 pm »

Go to the Simpletech.com Estore, add the Simpletech ProX 256MB SD card to your shopping cart ($86), add coupon 24834-876 (-$32), S/H is free, makes it $54 shipped, no mail-in rebates.

I received mine about 5 weeks ago. This seems to be an ongoing promotion that was down for a while but is up again.

This is probably the highest quality (and fastest) SD card you could get right now, the exact opposite of those crappy Sandisks.

Now if only someone could find a good deal on the 512MB model...

14

Zaurus - pdaXrom / What do you prefer...

« on: June 08, 2004, 09:15:53 am »

Bonus question:
We are currently talking about replacing all the \"built-in\" prefs/settings programs with python+pygtk - how do you feel about that?

Didn\'t note that one before. Anything other than storing prefs/settings in editable plain ascii text files is pure evil and leads to disaster (windows registry anyone?). Any GUI tools to changes these settings must be optional. I will not install python on my Z, and I would hate to have to fork if it became a required component.

15

General Discussion / Zaurus has competition from Windows?!?

« on: June 08, 2004, 08:47:20 am »

:twisted: Microsoft Purchases Evil From Satan  :twisted: