This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I had the same problem when I was trying to build my powerpc-eabi for linux. What I found is that you want to use the libiberty that is found in binutils. Sounds strange but it works. I looked at the libiberty in the latest binutils 2.9.1.something and in egcs1.1.1 and they were almost identical. Does anyone know how to get egcs to stop this? I used the following script found at ftp://ftp.cygnus.com/pub/embedded/crossgcc/one-tree-1.5.sh to build my system. I hacked the script so that it found the gcc directory as gcc-2.8.1 (or you could make it not care) :) Hope this helps, Vaughan ---root <vlebedev@aplio.fr> wrote: > > > Hi, > I'm struggling build a glibc based cross complier for m68k-linux running > on > Linux pc Host. > I've read the FAQ and cross-gcc FAQ too and it is still no go... > > The problem is that after the compiler itself is built it the makefile > tries to configure libibebrty for. The configure script runs the just > built compiler > which is incapable to perform the link stage because of missing target > startup object files and target libraries.... so the configure script > aborts. > > If i try to build glibc2.07 using partially built cross compiler i have > similar > problems during the make phase .... > > So i can't finish to build complier because i don't have a library and i > can't > build the library because i don't have a an installed compiler.... _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.