ltib
[Top][All Lists]
Advanced

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

RE: [Ltib] Can't get: linux-2.6.16-mx31-sdio.patch at ./ltibline599.


From: Sesto, Vin
Subject: RE: [Ltib] Can't get: linux-2.6.16-mx31-sdio.patch at ./ltibline599.
Date: Fri, 8 Dec 2006 10:30:15 -0500

Hi Steve

Thanks for your reply. Ltib is currently building and am hoping it
builds OK before I venture onto the next step ... which is to build a
native gcc supporting eabi/nptl version 4.1.1 

I guess I need a little more clarification as to your statement of the
gcc spec file in ltib will need some work to build a native gcc for arm
eabi targets. I am new to this so don't mind my trivial questions.

Could you please give me some hints as to how I should go about
achieving the native gcc 4.1.1 build versus the 3.4.3? I guess that's
been part of my issue all along.

Thanks.

Vin




-----Original Message-----
From: Steve Papacharalambous [mailto:address@hidden 
Sent: Friday, December 08, 2006 10:20 AM
To: Sesto, Vin
Cc: Stuart Hughes; address@hidden
Subject: RE: [Ltib] Can't get: linux-2.6.16-mx31-sdio.patch at
./ltibline599.

Hi Vin,

Your approach is correct, once you have ltib installed you can normally
select the gcc package and it will build gcc for the target root file
system.  You don't need to put the cross compiler in your PATH as ltib
takes care of all this for you.

However the gcc spec file currently in ltib builds gcc-3.4.3, so if you
want a non eABI generic arm gcc then this should work for you, but if
you need an arm eABI toolchain then you need a later version of gcc.  In
summary the gcc spec file in ltib will need some work to build a native
gcc for amr eABI targets,

Best regards,

Steve

On Fri, 2006-12-08 at 09:46 -0500, Sesto, Vin wrote:
> Hi Stuart
> 
> I am going to try this ASAP.
> 
> Let me back up here for a second. My main goal is to get a rootfs and
a
> native gcc built using LTIB. How should I go about doing this.
> 
> Please tell me if my logic is in error below.
> 
> 1. Get the CVS fix you mentioned below
> 2. Run LTIB
> 3. This produces a gcc that runs on intel platform which generates ARM
> instructions.
> 4. This also produces a rootfs and a linux kernel image.
> 5. Next, I want to create a native gcc for the iMX31. How do I achieve
> this? I thought I could run ./ltib --configure and select gcc and
other
> necessary libs (ie, binutils etc) and it would produce a native ARM
gcc.
> I guess one thing I should be sure to do is to make the cross-compiled
> gcc be first in my PATH ...
> 
> Does this sound like the correct approach?
> 
> Thanks.
> 
> Vin
> 
> 
> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden 
> Sent: Friday, December 08, 2006 6:03 AM
> To: Sesto, Vin
> Cc: address@hidden
> Subject: Re: [Ltib] Can't get: linux-2.6.16-mx31-sdio.patch at ./ltib
> line599.
> 
> Hi Vin,
> 
> This patch got pushed out today, so it's now available.  If you try
> again the kernel should build.
> 
> Why do you need to build gcc-4.1.1? there is a toolchain already
> available for this BSP ("ARM gcc-4.1.1,VFP,gnueabi/glibc-2.4-nptl-3"),
> and it has had some testing.
> 
> Regards, Stuart
> 
> On Thu, 2006-12-07 at 10:12 -0500, Sesto, Vin wrote:
> > Hello
> > 
> >  
> > 
> > I have just updated my LTIB from CVS and got this error.
> > 
> >  
> > 
> > Can?t get: linux-2.6.16-mx31-sdio.patch at ./ltib line 599.
> > 
> >  
> > 
> > I am trying to build for an MX31 with eabi / nptl support.
> > 
> >  
> > 
> > I need to be able to build gcc 4.1.1 for this target, however, I
can?t
> > even build without making any changes before even attempting that
> > feat!
> > 
> >  
> > 
> > Thanks.
> > 
> >  
> > 
> > V
> > 
> > 
> > _______________________________________________
> > LTIB home page: http://bitshrine.org
> > 
> > Ltib mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/ltib
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
> 




reply via email to

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