On Wed, Feb 20, 2013 at 6:49 PM, Oliver Spornitz <[email protected]> wrote: > > Am 19.02.2013 um 17:42 schrieb Sedat Dilek: > >> NO, it seems MIPSEL is not built correctly. >> I switched to a 7390 target and do NOT get this build-error. >> >> $ egrep -i 'mips|^FREETZ_TYPE_FON_WLAN' .config* >> .config:FREETZ_TYPE_FON_WLAN_7390=y >> .config:FREETZ_TARGET_ARCH="mips" >> .config:FREETZ_TARGET_CROSS="mips-linux-uclibc-" >> .config:FREETZ_KERNEL_CROSS="mips-unknown-linux-gnu-" >> .config.old:FREETZ_TYPE_FON_WLAN_7170=y >> .config.old:FREETZ_TARGET_ARCH="mipsel" >> .config.old:FREETZ_TARGET_CROSS="mipsel-linux-uclibc-" >> .config.old:FREETZ_KERNEL_CROSS="mipsel-unknown-linux-gnu-" >> >> Oliver did you test for a MIPSEL target, too? > > Yes, I tested with mips and mipsel toolchain. After your report, > I repeated the test on both mips/mipsel with the current head of > master branch. I used scratchbox2, but I don't think this makes > a diffence. Last week I also tested normal cross compiling on > mips and mipsel against my generated patch set. >
mips is OK, but not mipsel. Did you had a look into the tarball and ltrace.mk I have sent. What HOST_CPU/HOST_OS do you see in the config* files? - Sedat - > Regards > OS > _______________________________________________ Ltrace-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ltrace-devel
