[avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Galen Seitz
I successfully built 1.4.4 on an i386 GNU/Linux Fedora 4 system, but when I attempt the same build on my x86_64 GNU/Linux CentOS 4.3(RHEL clone), I get the error shown below. ...snip... ln gcrt1.o crttn861.o || cp gcrt1.o crttn861.o make[5]: Leaving directory

[avr-libc-dev] Math accuracy

2006-04-24 Thread David Carr
Just for fun I ran the savage benchmark on my Mega16 at 6MHz. I attempted to use double precision everywhere. (I say attempted because I'm no expert at this.) double d = 1; uint16_t i; for (i=1; i2500; i++) { d = tan(atan(exp(log(sqrt(d*d) + 1; } Here are the

[avr-libc-dev] more accuracy...

2006-04-24 Thread David Carr
Just as a point of reference: Execution times for the aforementioned benchmark 386 (with 387 co-processor) @ 33MHz .67s 486DX2 66MHz .121s Considering that the AVR is 8bit and has no hardware floating point, being only 12x slower than the 386 is impressive especially considering it runs at 1/5

Re: [avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Henrik Brix Andersen
On Mon, Apr 24, 2006 at 09:22:24AM +0200, Joerg Wunsch wrote: Under /usr/lib*? That sounds strange to me. The FreeBSD setup always locates all avr-libc files under /usr/[local/]avr/{include,lib}, independent of the host architecture. The GCC-installed files are under

[avr-libc-dev] math accuracy

2006-04-24 Thread David Carr
I'm resending this because I received my follow up but not the original message... Just for fun I ran the savage benchmark on my Mega16 at 6MHz. I attempted to use double precision everywhere. (I say attempted because I'm no expert at this.) double d = 1; uint16_t i; for (i=1;

Re: [avr-libc-dev] Math accuracy

2006-04-24 Thread Björn Haase
David Carr wrote on Montag, 24. April 2006 09:30 : Just for fun I ran the savage benchmark on my Mega16 at 6MHz. I attempted to use double precision everywhere. (I say attempted because I'm no expert at this.) A further test reveals (to me) that sizeof(float) == sizeof(double) == 4. Is

Re: [avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Joerg Wunsch
As Henrik Brix Andersen wrote: ... The GCC-installed files are under /usr/[local/]lib/gcc/avr/4.1.0. Under Gentoo Linux we also put the gcc files under /usr/lib/ So the trick would probably to explain to Galen what is needed for this to happen. I can't contribute much here, as this

Re: [avr-libc-dev] more accuracy...

2006-04-24 Thread Joerg Wunsch
As David Carr wrote: AVR float: 2476.245361328125 error: 23.754638671875 Which is fairly well in line with the 32-bit float results from the i386. Is there a way to have sizeof(double) == 8? Currently not. Volunteers are needed to hammer all this out, in

Re: [avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Henrik Brix Andersen
On Mon, Apr 24, 2006 at 03:51:37PM +0200, Joerg Wunsch wrote: So the trick would probably to explain to Galen what is needed for this to happen. I can't contribute much here, as this entire lib64 thing appears to be a Linux-specific one to me. FreeBSD, even on 64-bit archs, always uses

Re: [avr-libc-dev] Math accuracy

2006-04-24 Thread Matthew MacClary
On Mon, Apr 24, 2006 at 12:21:24AM +0200, Björn Haase wrote: Presently there is no difference concerning the code if you are writing double or float. The same calculations are definitely performed for both. However, I once ran a quick and dirty floating point benchmark that showed a small

Re: [avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Henrik Brix Andersen
On Mon, Apr 24, 2006 at 08:35:56AM -0700, Galen Seitz wrote: My problem was due to my lack of understanding of the rpm build system. I was using the rpmmacro %makeinstall. This was overriding the configured libdir with the system default for libdir. I've changed the install step to do the

Re: [avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Joerg Wunsch
As Galen Seitz wrote: I've changed the install step to do the following, though I'm not certain if this is the correct solution. make DESTDIR=$RPM_BUILD_ROOT install Probably it is. Both FreeBSD and Gentoo use portage, correct? Where do I look to see how these steps are performed on

Re: [avr-libc-dev] build fails on x86_64 GNU/Linux, missing stddef.h

2006-04-24 Thread Galen Seitz
Joerg Wunsch [EMAIL PROTECTED] wrote: As Galen Seitz wrote: I've changed the install step to do the following, though I'm not certain if this is the correct solution. make DESTDIR=$RPM_BUILD_ROOT install Probably it is. Both FreeBSD and Gentoo use portage, correct? Where do I