bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build issues with gettext 0.20.2 and 0.21 on Solaris 10 i386 with 64


From: Dagobert Michelsen
Subject: Re: Build issues with gettext 0.20.2 and 0.21 on Solaris 10 i386 with 64 bit
Date: Tue, 1 Dec 2020 21:14:58 +0100

Hi Bruno,

Am 01.12.2020 um 20:46 schrieb Bruno Haible <bruno@clisp.org>:
> But the $host_cpu value from the canonical triplet $host allows to do so.

This is the triplet I get for my 64 bit build:

checking build system type... i386-pc-solaris2.10
checking host system type... i386-pc-solaris2.10

These are the flags I set which are also inherited in the gettext-runtime
subinvocation:

'CC=/opt/csw/bin/gcc-5.5' 'CFLAGS=-O2 -pipe -fno-omit-frame-pointer -m64 
-march=opteron' 'LDFLAGS=-m64 -march=opteron -L/opt/csw/lib/64' 
'CPPFLAGS=-I/opt/csw/include' 'CXX=/opt/csw/bin/g++-5.5' 'CXXFLAGS=-O2 -pipe 
-fno-omit-frame-pointer -m64 -march=opteron'

> And this code works fine. I verified this:
>  - on a Solaris 10 machine:
>      CC="cc -O", CC="gcc -O2"                       -> HOST_CPU="i386"
>      CC="cc -xarch=generic64 -O", CC="gcc -m64 -O2" -> HOST_CPU="x86_64"
>  - on a Solaris 11.4 machine:
>      CC="gcc -m32 -O2" -> HOST_CPU="i386"
>      CC="gcc -O2"      -> HOST_CPU="x86_64"
> 
> You must be specifying a --host triplet incorrectly in your build. Possibly
> through a --host option when you run configure. Possibly through a 
> --cache-file
> that points to a file with a wrong setting.

Nope, neither —host nor —cache-file, but what differs is that I pass -m64 in 
CFLAGS
and not as part of CC.


Best regards

  — Dago


-- 
"You don't become great by trying to be great, you become great by wanting to 
do something,
and then doing it so hard that you become great in the process." - xkcd #896




reply via email to

[Prev in Thread] Current Thread [Next in Thread]