linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: "Bryan O'Donoghue" <typedef@eircom.net>
Cc: Wojciech Kromer <krom@dgt-lab.com.pl>, linuxppc-embedded@ozlabs.org
Subject: Re: any hints using gcc 3.4.3 for 2.4.25 kernel?
Date: Wed, 23 Feb 2005 16:42:55 +0100	[thread overview]
Message-ID: <200502231642.55758.g.jaeger@sysgo.com> (raw)
In-Reply-To: <421CA367.1010604@eircom.net>

On Wednesday 23 February 2005 16:38, Bryan O'Donoghue wrote:
> Gerhard Jaeger wrote:
> > On Monday 21 February 2005 15:12, Wojciech Kromer wrote:
> > 
> >>a)first i have:
> >>- 2.4.25 kernel (from denx cvs)
> >>- eldk with 2.95.4 compiler
> >>this one set works fine :)
> >>
> >>b)then, i've tried  to same sources with:
> >>gcc-3.4.3 , self build from uClibc buildroot
> >>new hernel hangs just after decompressing :(
> >>
> >>any tricks?
> >>
> > 
> > 
> > you can use the include/linux/init.h and compiler.h from 2.4.29
> > kernel + patching some header files, where the inlining does not
> > work any longer. I also suggest comparing with 2.4.29 kernel.
> > 
> > ciao,
> > Gerhard
> > 
> 
> If all you want is a cross compiler to make a kernel why not try this 
> procedure ?
> 
> Tested with :
> 
> gcc-3.4.2
> binutils-2.15.90.0.3
> dietlibc-0.28 or dietlibc cvs
> 
> 1
> untar all sources
> 
> 2
> binutils:
> 
> ./configure --prefix=/usr/local/powerpc-linux --target=powerpc-linux
> 
> make
> make install
> 
> 3
> gcc:
> 
> ./configure --prefix=/usr/local/powerpc-linux --target=powerpc-linux 
> --with-ecos --disable-nls --enable-threads=posix --disable-shared 
> --enable-languages=c --with-headers=../dietlibc/include
> 
> make
> make install
> 
> There might be a little error in gcc/unwind-dw2-fde-glibc.c and 
> gcc/unwind-dw2-fde.h
> 
> I can't remember the exact errors in those two files, but, hopefully 
> those should be easy enough to fix.
> 
> Once you work around the slight inconsistency between dietlibc & gcc in 
> those two files, and make install, you should have a full toolchain in 
> /usr/local/powerpc-linux
> 
> I had been thinking about making a small script for kernel people such 
> as yourself, who wanted just a toolchain for kernel cross compiles.
> Maybe I'll do that.
> 
> But, in any case, the above procedure gives me a 3.4.2 which is quite 
> happy to compile a 2.4.28-rc3 (though I haven't tried out the denx 
> 2.4.25... but, I can't see why that would fail).
> 
> Hope this helps.

I'm pretty sure, that it won't help on a 2.4.25 kernel. The 2.4.28-rc3 already
has the needed patches/changes applied, that's why it works for you ;)

ciao,
Gerhard

-- 
Gerhard Jaeger <gjaeger@sysgo.com>            
SYSGO AG                      Embedded and Real-Time Software
www.sysgo.com | www.elinos.com | www.pikeos.com | www.osek.de 

      reply	other threads:[~2005-02-23 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 14:12 any hints using gcc 3.4.3 for 2.4.25 kernel? Wojciech Kromer
2005-02-21 14:28 ` Ralph Siemsen
2005-02-23 14:54 ` Gerhard Jaeger
2005-02-23 15:38   ` Bryan O'Donoghue
2005-02-23 15:42     ` Gerhard Jaeger [this message]

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=200502231642.55758.g.jaeger@sysgo.com \
    --to=g.jaeger@sysgo.com \
    --cc=krom@dgt-lab.com.pl \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=typedef@eircom.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;
as well as URLs for NNTP newsgroup(s).