Solaris vtv port breaks x32 build
Rainer Orth
ro@CeBiTec.Uni-Bielefeld.DE
Wed Dec 2 12:29:00 GMT 2015
Sorry for replying so late: I'd been away from my mail for an extended
weekend.
Jeff Law <law@redhat.com> writes:
> On 12/01/2015 07:17 AM, Ulrich Drepper wrote:
>> On Tue, Dec 1, 2015 at 2:39 AM, Matthias Klose <doko@ubuntu.com> wrote:
>>> that might be another instance of
>>> https://gcc.gnu.org/ml/gcc-patches/2015-01/msg02064.html
>>> Does something like this help?
>>
>> No, same problem as before. This macro doesn't actually generate any
>> code in configure.
> From looking at your configure line, I see that
> --build = x86_64-redhat-linux
> --host = x86_64-redhat-linux
>
> and no --target
>
> That to me looks like a native setup and thus I would expect
> $cross_compiling to be "no". Hence the behaviour you're seeing.
Exactly: it would be good if Ulrich could post the canonical build,
host, and target values determined by configure, so we can be sure.
> Essentially you've got a native toolchain, but with one or more multilibs
> that can't actually be executed.
Right: I saw exactly the same behaviour in the distant past when
bootstrapping on an IRIX host that couldn't execute 64-bit binaries or
on Solaris/SPARC with a non-SPARCv9 capable cpu. At that time, the only
workaround was to configure with --disable-multilib.
> Which in turn suggests looking more closely at Matthias's suggestion.
Exactly: moving AM_ENABLE_MULTILIB up as Matthias suggested sets
cross_compiling=maybe for non-default multilibs early, which should
achieve the desired behaviour. All other libraries that invoke both
macros already do so in this order.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
More information about the Gcc
mailing list