ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Failure to Build - glibc - LPC32xx Target


From: Tim Nelson
Subject: Re: [Ltib] Failure to Build - glibc - LPC32xx Target
Date: Fri, 23 Jul 2010 16:01:15 -0500 (CDT)

That appears to be the issue. I reselected the 'from toolchain' option and the 
compile is happily chugging along.

Thank you!

--Tim

----- "Kevin Wells" <address@hidden> wrote:
> Hi Tim,
> 
> It looks like the C library included with the toolchain is -not- being
> used. Is this
> the library you meant to select?
> 
> If you didn't mean to change the original library, bring up the LTIB
> menu and make
> sure the C library package (???) ----> option is set for "from
> toolchain only". By
> default, the library included with the toolchain is used (and it's the
> only way
> I've tested it).
> 
> If you really need the library not included with the toolchain, please
> let me know
> and I'll take a look at it.
> 
> thanks,
> Kevin
> 
> 
> > -----Original Message-----
> > From: address@hidden [mailto:ltib-
> > address@hidden On Behalf Of Tim Nelson
> > Sent: Friday, July 23, 2010 12:17 PM
> > To: address@hidden
> > Subject: [Ltib] Failure to Build - glibc - LPC32xx Target
> > 
> > Greetings fellow ltib'ers-
> > 
> > In an attempt to build a fresh install for a development board, I'm
> > seeing glibc compilation crashing. The target board is a ucDragon
> > carrier + CPU board based on the NXP LPC3205 SoC which is (nearly?)
> > identical to the Phytec boards. As such, I've selected the Phytec
> board
> > as the target platform.
> > 
> > The version of ltib I'm using was checked out today from CVS. I've
> > attached a full log of the build session. However, the main culprit
> > appears to be this:
> > 
> > sysdeps/unix/sysv/linux/sys/syscall.h:25:24: error: asm/unistd.h:
> No
> > such file or directory
> > 
> > Any thoughts? Please let me know if you need additional information
> > (configs, package selections, etc).
> > 
> > Thank you!
> > 
> > --Tim



reply via email to

[Prev in Thread] Current Thread [Next in Thread]