Jeffrey Walton <[email protected]> writes: > I have a Solaris 11.3 box, but it does not have Sun Studio on it. Two > other testing machines have Sun Studio 12.1 through 12.6, but both are > dead at the moment. I need to order some parts. > > Maybe the OpenCSW folks have something that can test Sun Studio. They > provide free accounts to developers.
I don't have any time to spend on testing with these systems or compilers. Do you think it makes sense to change from -G to -shared unconditionally for Solaris? It makes no sense to try to do something more clever based on compiler used, without any contributor able to test it. > Braindead Autotools. Please, no derogatory comments about autoconf on this list. And as I think I've said before, the term "autotools" is even more irrelevant here. > But Autotools detects the system as i386: > > $ /usr/share/automake-1.11/config.guess > i386-pc-solaris2.11 Can you check if latest config.guess (https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess) has this bug? If not, I can simply upgrade to the latest version. If it's still giving the wrong result, it might make your life easier to submit a patch to fix this problem upstream. One subtlety is that it might cause problems to say x86_64 if the compiler produces 32-bit i386 binaries by default. You might also want to test if CC_FOR_BUILD='gcc -m64' ./config.status makes any difference. > So I have to tell Autotools to build for a 64-bit system via > --host=amd64-sun-solaris If you get into any subtle problems from configure thinking you're crosscompiling, you might want to add --build=amd64-sun-solaris instead or in addition to setting --host. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
