Page MenuHome GnuPG

libgcrypt build on freebsd 10.0-amd64 fails, cast5-amd64.S not linked to build
Closed, ResolvedPublic


See for details and
build error at

Question: How to connect cipher/cast5-amd.S to the build ?

Related Objects

Event Timeline

pi set External Link to 6 2014, 12:15 PM
pi set Version to 1.6.1..
pi added projects: libgcrypt, Bug Report, FreeBSD.
pi added a subscriber: pi.

By patching configure it's possible to connect the cipher/*-amd64.S to the build.

See attached.

That should not be required. Did you explicitly specify host with

config.guess has this code:


UNAME_PROCESSOR=/usr/bin/uname -p

		echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;

to map "amd64" to "x86_64" and config.sub called with "amd64" also
returns the canonical "x86_64". Thus everything should be fine.

(I think "amd64" would have been the better and easier to type name,
but the GCC developers settled for "x86_64").

No, FreeBSD has amd64 as uname -m value.

WTF happened to config.guess? Upstream's ChangeLog has these entries:

2011-08-20 Ben Elliston <>

  • config.guess (*:FreeBSD:*:*): Switch on ${UNAME_PROCESSOR}.
  • testsuite/ Remove hard to test FreeBSD cases.

2006-04-26 Bruno Haible <>

	    Ben Elliston  <>
  • config.guess (amd64:FreeBSD:*:*) Detect as x86_64.
  • testsuite/ Add test case.

Thus in 2006 support form and64 was added and in 2011 the faulty
"uname -p" was implemented and test cases removed. I assume that
everyone patched similar to what you suggested. However, the correct
thing is to fix config.guess.

Unfortunately I do not have access to any FreeBSD box right now (the
FreeBSD in the gcc compile farm is offline). Can you do some tests on
several FreeBSD boxes or give me access to a test box?

What are the patches to configure I see in the build log? And why are
the M4 files are patched - they are not used after configure has been
created? I would also like to see the config.rpath to see how it has been

Feel free to continue by private mail.

Well, on FreeBSD 10 "uname -p" works the same as "uname -m". It is not POSIX

Resolved according to freebsd tracker.

werner claimed this task.

FWIW, I checked my POSIX 2001 standard and it does not define -p. The
GNU manual for uname however has to say:


     Print the machine hardware name (sometimes called the hardware
     class or hardware type).


Print the processor type (sometimes called the instruction set
architecture or ISA).  Print `unknown' if the kernel does not make
this information easily available, as is the case with Linux