[Aboriginal] undefined reference to `finite'
onefang at gmail.com
Thu Apr 7 08:17:19 PDT 2011
On Thu, 7 Apr 2011 23:21:34 +1000 David Seikel <onefang at gmail.com>
> On Tue, 5 Apr 2011 06:35:02 -0500 Rob Landley <rlandley at parallels.com>
> > On 04/05/2011 05:12 AM, David Seikel wrote:
> > > I'm very tired, and slightly ill, and I can't figure this out.
> > >
> > > One of the packages from the UI library I want to use for this
> > > project uses a function called finite(double). As far as I can
> > > tell, uClibc should supply that function, since we have
> > > DO_C99_MATH=y in its baseconfig. It's not being found though.
> > >
> > > It's all buried in a forest of #ifdef's that my tired mind is in
> > > no condition to sort out.
> > >
> > > I'm only two packages away for having all my needed libraries
> > > installed before I can start cutting code. Time to sleep.
> > Hmmm... Posibly a question for the uClibc mailing list?
> > You didn't say which target you were using, so I'll poke at x86_64:
> I'm sticking with doing my builds for 486, since it's still possible
> that those tiny 486 based boards I looked at last year may be used.
> If they are not used, then 486 code will at least work fine on
> whatever we move to. Any board we move to will be a lot faster
> anyway, and I've already mentioned that speed is not important for
> this project.
> It appears that finite() is obsolete, and replaced with an isfinite()
> macro. A few things I found in my research pointed to that, including
> the man pages on Ubuntu, but the clincher was this -
> I'll poke the UI library development list about changing that, though
> the source I'm using is a stable release tarball, but they are
> thinking of cutting another release soon. Wont be a major change, I
> think they only use finite() once.
> Think I'll just stick a sed command in the build script for that
> library for now.
That did the trick. All the libraries and development tools I think
I'll need are now compiled. YAY!!
Got it all in a modified version of lfs-bootstrap, so that's the entire
thing automated. The actual application itself can be handled by just
one more small build script added to the end of that bootstrap. It was
all very easy thanks to Aboriginal Linux. I'm ahead of schedule.
Next steps - generate an actual bootable disk image that I can throw
at real hardware. Clean up some loose ends I kinda glossed over in the
effort to get it all done. Then... cut code. B-)
> > By the way, have you read this yet?
> > http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
> > One of the best quick and dirty "get familiar with elf file format"
> > things I've seen...
> Nope, but I'll look at it later.
Very interesting read. Would have been magical if he had been able to
squeeze a little more and get the total executable size down to 42
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: not available
More information about the Aboriginal