On 14-05-19 15:25, Rene Rebe wrote:
package/scientific/gmp/zzz.m68k.patch
is similarly likely only necessary if our gcc wrapper does not have it’s
variables exported.
We better 1) fix that and 2) remove -m68* generally off the compiler
invocation, then we
do not need to patch all packages like this. All the generic options are
currently removed
The problem with this package was that, during cross compilation, the CPU gets
misdetected, causing the GMP to fall back to 68000, which does not work
because. I found this was the only way to force it to select the codepath for
68020+ (and actually compile without error.
You could check if it just works now again, that the gcc wrapper is fixed with
“current” bash versions. If not please resend ;-)
I did. I dove in a little deeper and it appears the cpu is derived from
the name of the target:
m68k-t2-linux-gnu will be detected as m68k, of course.
The documentation states:
"'m68k' is taken to mean 68000."
I can cheat it without patches by symlinking m68k-t2-linux-gnu-gcc to,
for example, m68020-t2-linux-gnu-gcc
On a side note:
wpa_supplicant depends on dbus, but dbus does not appear to be compiled
in the same stage, therefore wpa_supplicant fails to build.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
li...@t2-project.org with a subject of: unsubscribe t2
