Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Doug the RockRat <rickyrockrat@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel cross compilation problem (at91sam9260)
Date: Mon, 11 Feb 2008 12:57:35 -0800 (PST)	[thread overview]
Message-ID: <121538.90243.qm@web62014.mail.re1.yahoo.com> (raw)
In-Reply-To: <9475874EB351DD4CBF4112EA18254D6601087D@zoe.synchroforge.com>

Is it possible that a boot logo was perhaps added?  
That does add a significant amount of size to the
kernel.
--- Rick Foos <rick@synchromeshcomputing.com> wrote:

> Hi,
>  
> I had the same problem going from 800k to 3MB
> kernels. It was not related to compilers. 
>  
> The size is due to a large initrd filesystem.
>  
> Clean everything out, the standard cleans don't seem
> to do it. 
>  
> I can't say what exactly gets it done, removing init
> ram filesystem, but it looks like toolchain rebuild
> as well is required.
>  
> , and in .config
>  
> # BR2_TARGET_ROOTFS_INITRAMFS is not set
>  
> Best Regards,
> Rick
> 
> ________________________________
> 
> From: buildroot-bounces at uclibc.org on behalf of
> Wayne Keenan
> Sent: Mon 2/11/2008 11:32 AM
> To: grego rigolo
> Cc: buildroot at uclibc.org
> Subject: Re: [Buildroot] kernel cross compilation
> problem (at91sam9260)
> 
> 
> Hi,
> 
> Dropping back to using gcc 3.4.6  and uclib x.x.28
> worked for me.  - not a proper fix, but it was a
> combination that worked andI was fed up of trying
> combinations :)
> 
> 
> Regards
> Wayne
> 
> 
> 
> On Feb 11, 2008 4:10 PM, grego rigolo
> <gregorigolo2002@yahoo.fr> wrote:
> 
> 
> 	hello,
> 	I'm using the buildroot-20080206.tar.bz2 package to
> build a rootfilesystem and a cross compilation
> toolchain for my embedded board (sam9260).
> 	I tried to cross compile (arm-linux-gcc-4.1.2) a
> 2.6.23 linux kernel seperately (not the one included
> in buildroot) , and i noticed that the size had
> increased by 3Mb respect to my old version.
> 	On the other hand when i try to use the generated
> kernel, it hangs at the stage 
> 	uncompressing Linux ....................
> 	Does anyone encounters this kind of problem ?
> 	greg
> 	
> 
> 
> ________________________________
> 
> 	Ne gardez plus qu'une seule adresse mail ! Copiez
> vos mails
>
<http://fr.rd.yahoo..com/mail/mail_taglines/trueswitch/SIG=11gshn0bu/**http%3A%2F%2Fwww.trueswitch.com%2Fyahoo-fr%2F>
>  vers Yahoo! Mail 
> 
> 	_______________________________________________
> 	buildroot mailing list
> 	buildroot at uclibc.org
> 	http://busybox.net/mailman/listinfo/buildroot
> 	
> 
> 
> > _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

  reply	other threads:[~2008-02-11 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 16:10 [Buildroot] kernel cross compilation problem (at91sam9260) grego rigolo
2008-02-11 17:32 ` Wayne Keenan
2008-02-11 19:38   ` Rick Foos
2008-02-11 20:57     ` Doug the RockRat [this message]
2008-02-15  8:33 ` Stéphane Champeau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=121538.90243.qm@web62014.mail.re1.yahoo.com \
    --to=rickyrockrat@yahoo.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox