Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I've been seeing the odd problem when building on my DNS-323, so I thought I would try and build a later gcc ...
Turns out to be harder than I first thought! I've been trying gcc 4.4.3 (with the openwrt patches applied) but I get various build failures. I'll try 4.4.2 next ..
But has anyone else tried to build a later gcc ?
Thanks,
Pete
Offline
I hit a couple of issues which I couldn't find a solution for.
When trying to build a c program with gcc I see :-
/ffp/lib/libgcc_s.so: undefined reference to `__eqdf2'
/ffp/lib/libgcc_s.so: undefined reference to `__divsf3'
/ffp/lib/libgcc_s.so: undefined reference to `__ltdf2'
/ffp/lib/libgcc_s.so: undefined reference to `__fixunsdfsi'
/ffp/lib/libgcc_s.so: undefined reference to `__nesf2'
/ffp/lib/libgcc_s.so: undefined reference to `__eqsf2'
/ffp/lib/libgcc_s.so: undefined reference to `__divdf3'
/ffp/lib/libgcc_s.so: undefined reference to `__muldf3'
/ffp/lib/libgcc_s.so: undefined reference to `__ltsf2'
/ffp/lib/libgcc_s.so: undefined reference to `__mulsf3'
/ffp/lib/libgcc_s.so: undefined reference to `__nedf2'
Secondly, configure fails on libstdc++-v3 ... but unfortunately I don't have the error message to hand any more :-(
Offline
Oh, also the main issue I'm seeing with 4.1.3 is an occasional "internal compiler error"., especially with building larger (more complex?) programs.
For example, I need to improve the performance of my spamassasin - I thought I would try compiling the spam rules, this calls gcc and usually fails.
Offline
a different compiler version wont help you
the undefined symbols are due to incompatible compiler config (ffp uses soft-floats)
the internal compiler errors are most likely a kernel problem. in my experience, more recent compiler fail more often than 4.1. the only reliable solution is to compile in qemu,
ps: if you really want to try a new gcc, you may want to try these packages: http://www.inreto.de/testing/ffp/0.6/ar … kages/All/
note that they are not compatible with ffp 0.5
Offline
fonz wrote:
a different compiler version wont help you
the undefined symbols are due to incompatible compiler config (ffp uses soft-floats)
I've been building with --with-float=soft configure option and CFLAGS_FOR_TARGET including -msoft-float on the make line ... I thought that would be okay, but obviously not.
the internal compiler errors are most likely a kernel problem. in my experience, more recent compiler fail more often than 4.1. the only reliable solution is to compile in qemu,
Hmmm, okay.
ps: if you really want to try a new gcc, you may want to try these packages: http://www.inreto.de/testing/ffp/0.6/ar … kages/All/
note that they are not compatible with ffp 0.5
Great, thanks.
Offline
plord wrote:
Secondly, configure fails on libstdc++-v3 ... but unfortunately I don't have the error message to hand any more :-(
Trying to build gcc 4.4.2 I see :-
checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
which is the same error I saw with 4.4.3
Maybe I need to go down a different path here.
Offline