Your welcome.

I regret to have distracted your attention. All the above applies to a terminal window (KDE's konsole) in my GUI KDE. On the bare FreeBSD console, everything is fine. So this is a bug in some KDE library or konsole. I'm sorry I did not have the idea to test that on the bare console right away. I'll close this bug here.

Hello Mr. Niibe,

It seems that nl_langinfo(CODESET) returns US-ASCII on your system.

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

`-m'
`--machine'

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

`-p'
`--processor'

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
kernels.

Resolved according to freebsd tracker.

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

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

2011-08-20 Ben Elliston <bje@gnu.org>

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

2006-04-26 Bruno Haible <bruno@clisp.org>

	    Ben Elliston  <bje@gnu.org>

• config.guess (amd64:FreeBSD:*:*) Detect as x86_64.
• testsuite/config-guess.data: 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
changed.

Feel free to continue by private mail.

No, FreeBSD has amd64 as uname -m value.

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

config.guess has this code:

*:FreeBSD:*:*)

UNAME_PROCESSOR=/usr/bin/uname -p
case ${UNAME_PROCESSOR} in

	    amd64)
		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").

D201: 439_patch-configure.diff

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

See attached.

Just fixed in SVN.