This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

problem with choice of --prefix dir


I have a MIPSEL system with a native toolchain I downloaded. I need to
add a compiler that would link with uClibc. This is done by picking

       	         *
       --prefix=/usr/local --target=mipsel-linux \
       --program-transform-name=s/^mipsel-linux-/mipsel-uclibc-/ \
       	         *

I want to put the new compiler in /usr/local. As soon as the build script
copied libraries files into /usr/local and did

	ln -s  /usr/local/lib/ld-uClibc-0.9.12.so ld-uClibc.so.0

The native gcc stopped working. I got the error

    gcc -o test test.c
    /lib/crt1.o: In function `__start':
    /lib/crt1.o(.text+0x4c): undefined reference to `__libc_start_main'
    collect2: ld returned 1 exit status

If I do gcc --print-search-dirs /usr/local doesn't show up. When I do
gcc -v test.c it pulls the crt*.o files from the correct place. If I do

    mv /usr/local/lib /usr/local/LIB

then the native gcc works fine. How can I keep my native gcc working and
put the new compiler in /usr/local? What is causing my problem? I only
need the native gcc to work until the new one finishes building but if
I can keep them both would like to preserve that option.

Thanks.


-- 
Joel Coltoff

Just think of the tragedy of teaching children not to doubt.
    -- Clarence Darrow


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]