[argyllcms] Re: Building Argyll 1.5.0 on Ubuntu Quantal fails

  • From: Pascal de Bruijn <pmjdebruijn@xxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Sat, 2 Mar 2013 16:34:43 +0100

On Fri, Mar 1, 2013 at 11:53 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
> Pascal de Bruijn wrote:
>> Apparently the order in which the link flags are passed matters, so
>> moving them to the end seems to fix my build issue.
>
> Hi,
>         interesting that I didn't notice this on any of the
> gcc's I've compiled V1.5.0 on.
>
> Do you known what version of gcc this is ?

On Ubuntu Quantal (12.10):

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.7.2-2ubuntu1'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--enable-gnu-unique-object --enable-plugin --enable-objc-gc
--disable-werror --with-arch-32=i686 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)

and

$ ld -v
GNU ld (GNU Binutils for Ubuntu) 2.22.90.20120924

> Were you using the Jambase that comes with V1.5.0 ?

Yep, I was using completely unpatched sources.

Well, except for the patch I posted of course :)

>> On my 64bit machine I had to explicitly pass HOSTTYPE
>>
>> $ HOSTTYPE=x86_64-linux-gnu make
>
> For some reason lots of systems don't export things like
> HOSTTYPE by default. Typically I fix it in my .profile etc.
>
>> Maybe it's an idea to try uname -m to autodetect?
>
> I'll look into it, but such utilities are rather system type
> dependent, thereby resulting in a logical loop :-)

It's not ideal either, I agree.

Regards,
Pascal de Bruijn

Other related posts: