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]

Re: MIPS(el) Toolchain


I've tried to follow the patch trail, but I've still got issues with
building a cross compiler for mips.  I am shooting for:
binutils-2.16
gcc-3.4.3
glibc-2.3.5 

Incidentally, the http://sources.redhat.com/bugzilla/show_bug.cgi?id=758 
patch failed.  It looks like it is meant for glibc-2.3.4.  I don't think 
this patch is necessary for glibc to compile.  Is this true? 

It almost looks like a problem with gmake.  I see a lot of lines like:
   make -C <****> subdir_lib
Where <****> is csu, iconv, iconvdata, locale, localedata, assert, ctype, 
etc..   Everything is going great until this line:
make  -C /data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/
gcc-3.4.3-glibc-2.3.5/glibc-2.3.5/Makerules subdir_lib
This seems all wrong to me.  Makerules is a file, while in all of the other 
cases, <****> is a directory. 

Here is the tail end of my log.  I have also attached a more complete 
version. 

.././scripts/mkinstalldirs 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug
echo 'debug/backtrace.os debug/backtracesyms.os debug/backtracesymsfd.os 
debug/noophooks.os debug/memcpy_chk.os debug/memmove_chk.os 
debug/mempcpy_chk.os debug/memset_chk.os debug/stpcpy_chk.os 
debug/strcat_chk.os debug/strcpy_chk.os debug/strncat_chk.os 
debug/strncpy_chk.os debug/sprintf_chk.os debug/vsprintf_chk.os 
debug/snprintf_chk.os debug/vsnprintf_chk.os debug/printf_chk.os 
debug/fprintf_chk.os debug/vprintf_chk.os debug/vfprintf_chk.os 
debug/gets_chk.os debug/chk_fail.os debug/readonly-area.os' > 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug/stamp.osT
mv -f 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug/stamp.osT 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug/stamp.os
.././scripts/mkinstalldirs 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug
echo '' > 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug/stamp.oSTT
mv -f 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug/stamp.oSTT 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/build-glibc/debug/stamp.oST
make[2]: Leaving directory 
`/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gl

ibc-2.3.5/glibc-2.3.5/debug'
make  -C 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/glibc-2.3.5/Makerules subdir_lib
make: *** 
/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gli

bc-2.3.5/glibc-2.3.5/Makerules: Not a directory.  Stop.
make: Entering an unknown directorymake: Leaving an unknown 
directorymake[1]: *** 
[/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gl

ibc-2.3.5/glibc-2.3.5/Makerules/subdir_lib] Error 2
make[1]: Leaving directory 
`/data/mips/compile/crosstool-0.35/build/mips-unknown-linux-gnu/gcc-3.4.3-gl

ibc-2.3.5/glibc-2.3.5'
make: *** [lib] Error 2 

 

I think I'm really close.  Hopefully this is obvious to someone.  I am using

crosstool-0.35 on a FC3 PC. Thank you. 

Bryan 

 

>>> I followed TheNop's suggestions and I was able to build
>>> gcc-3.3.5 and glibc-2.3.5 with kernel 2.4.26 for mips and 
>>> mipsel. However those patches do not appear in official crosstool. 
>>> 
>>> Do you plan to use the patches?
>>> This way maybe the build matrix can be updated, now it just
>>> red and yellow. :-(
>> 
>> I just added the patch from
>> http://sources.redhat.com/bugzilla/show_bug.cgi?id=758
>> to patchs/glibc-2.3.[45].   Hopefully that's enough.
>> If not, let me know.
>
>No it is not :-( 
>
>You have to apply one more patch to the glibc and one patch
>to crosstool.sh. Although they are included in the mail
>I have tested them with the glibc-2.3.5, modified a little and
>attached them to this mail for your convenience.

Attachment: log_piece.txt
Description: Text document

------
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]