public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Beena" <beena@gdatech•com>
To: "Silverton Aron-C1710C" <Aron.J.Silverton@motorola•com>,
	"'Ashwin Bihari'" <raz0redge@hotmail•com>, <listmember@orkun•us>,
	<linuxppc-embedded@lists•linuxppc.org>
Cc: <dank@kegel•com>
Subject: RE: Cross-compile package combinations
Date: Thu, 11 Dec 2003 15:15:48 -0800	[thread overview]
Message-ID: <FFELLIHDBBOAPGLCBDIPEEADCDAA.beena@gdatech.com> (raw)
In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A038ECB22@il02exm11>


I have observed the same errors when trying to build the bootstrap gcc
3.2.3. I understand that
this is because gcc 3.2.3 build (in case of powerpc) looks for some glibc
files. So I first built gcc 2.95.3,
then glibc 2.2.1 and then built bootstrap gcc 3.2.2(you could try with
3.2.3) and it compiled fine.

Hope this helps.
Beena

-----Original Message-----
From: owner-linuxppc-embedded@lists•linuxppc.org
[mailto:owner-linuxppc-embedded@lists•linuxppc.org]On Behalf Of
Silverton Aron-C1710C
Sent: Thursday, December 11, 2003 1:57 PM
To: 'Ashwin Bihari'; 'listmember@orkun•us';
'linuxppc-embedded@lists•linuxppc.org'
Cc: 'dank@kegel•com'
Subject: RE: Cross-compile package combinations



Continuing this top-posting madness:

I am trying to build gcc 3.2.3 for powerpc-linux on i386.  I have binutils
2.14 built already.  I have not done anything with glibc as of yet.  Here is
where I die:

[lots of stuff omitted]
mkdir libgcc
mkdir nof
mkdir libgcc/nof
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc/xgcc
-B/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc/
-B/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/bin/
-B/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/lib/ -isystem
/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/include -O2  -DIN_GCC
-DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
-I../../gcc-3.2.3/gcc -I../../gcc-3.2.3/gcc/. -I../../gcc-3.2.3/gcc/config
-I../../gcc-3.2.3/gcc/../include  -fPIC -mstrict-align -DL_muldi3 -c
../../gcc-3.2.3/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from tconfig.h:21,
                 from ../../gcc-3.2.3/gcc/libgcc2.c:36:
../../gcc-3.2.3/gcc/config/rs6000/linux.h:81:20: signal.h: No such file or
directory
../../gcc-3.2.3/gcc/config/rs6000/linux.h:82:26: sys/ucontext.h: No such
file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory
`/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory
`/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc'
make: *** [all-gcc] Error 2

I issued the commands:

$ ../gcc-3.2.3/configure --target=$TARGET --prefix=${PREFIX}
--without-headers --with-newlib --enable-langauges=c

$ make all-gcc

I am not using crosstools.  I may trie it if I can figure out how to specify
the paths to put everything where I want it.

Any suggestions?

Thanks,

Aron


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-12-11 23:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 21:57 Cross-compile package combinations Silverton Aron-C1710C
2003-12-11 23:15 ` Beena [this message]
2003-12-12  4:26   ` Dan Kegel
2003-12-16 18:21     ` Beena
  -- strict thread matches above, loose matches on Subject: below --
2003-12-16 19:34 Ashwin Bihari
2003-12-16 19:14 Silverton Aron-C1710C
2003-12-16 19:07 Ashwin Bihari
2003-12-16 18:53 Silverton Aron-C1710C
2003-12-16 20:14 ` Wolfgang Denk
2003-12-11 16:29 Ashwin Bihari
2003-12-11 14:29 Silverton Aron-C1710C
2003-12-11  0:28 Ashwin Bihari
2003-12-10 23:50 Silverton Aron-C1710C
2003-12-11  6:18 ` Dan Kegel
2003-12-11 16:06   ` listmember

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=FFELLIHDBBOAPGLCBDIPEEADCDAA.beena@gdatech.com \
    --to=beena@gdatech$(echo .)com \
    --cc=Aron.J.Silverton@motorola$(echo .)com \
    --cc=dank@kegel$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=listmember@orkun$(echo .)us \
    --cc=raz0redge@hotmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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