Hi,
It looks like:
- the plist change for libgcrypt is missing in the patch
- INSTALL_TARGET=install-strip should be preferred over ${STRIP} conditionned on DOCS option
- USE_GCC=4.7 should be replaced by USE_GCC=yes, version 4.7 is retired upstream and we plan to move to 4.8 soon

Fixes for the additional ports see
devel/ccrtp, PR 192162
editors/abiword, PR 192163
security/shishi, PR 192164
security/p5-Crypt-GCrypt, PR 192166
Do you want to wait for those to be committed for another exp-run ?

Created attachment 145057[details]
patch to fix devel/ccrtp build, to apply to libgcrypt/files/
Thanks, I missed the test on 9.1, only did it on 10.0 8-(
The attached patch for libgcrypt fixes this. This file needs to be placed in
security/libgcrypt/files/
as patch-gcrypt.h.in

PASS: bench-slope
SKIP: hashtest-256g
======================================
10 of 24 tests failed
(1 test was not run)
Please report to http://bugs.gnupg.org
======================================
Same without CPUTYPE setting. Looks like something is about AMD, amd64 and clang.
Yes I think using GCC for all archs would be fine.

(In reply to arcade from comment #25)
> And here am I :)
>
> I am a user of security/vpnc and after last update vpnc crashes after start:
Can you build security/vpnc in poudriere on 10.0p7-amd64-REL ? And
try whether the binary crashes as well ?
Antoine suggested that you put your two WRKDIRs as .tgz somewhere and
we compare it to our builds ?

(In reply to Kurt Jaeger from comment #33)
> (In reply to Carlos Jacobo Puga Medina from comment #31)
> > I updated and rebuilt all ports installed which depend on libgcrypt. Only I
> > can say that it went pretty well.
>
> Can you test if vpnc starts ?
I missing one that I'm just building...chromium and it goes well.

I archived both WRKDIR's at http://limbo.xim.bz/libgcrypt/
Whether it's relevant or not I'm using WRKDIRPREFIX:=/tmp/ports
No, I have no gdb experience... but I can get on IRC :)
Now I'll try building libgcrypt at some 10-RELEASE machine, right?

Well, I tried to test this on a number of machines. Everything works on the machines with Intel processors whether it's 10-RELEASE or 10-STABLE.
Everything brakes when it's AMD running on 10-STABLE. I did a clean build, I don't use ccache for world and it still doesn't work.
I'll try to install 10-RELEASE somewhere into the jail to test how 10-RELEASE works with AMD processors.

So, on a problematic AMD box could you:
- install devel/gdb
- build security/libgcrypt with clang
- go to /tmp/ports/usr/ports/security/libgcrypt/work/libgcrypt-1.6.1/tests
- verify that some programs there like ./basic do crash due to Illegal instruction
- run /usr/local/bin/gdb ./basic
In the gdb prompt, type run, type bt, type disass and enter until you reach the end of the function
And copy all the output somewhere; that way we will see what is the illegal instruction

Installing devel/gdb. Meanwhile I already copied /usr/obj and /usr/src from one of the working machines and created a jail with 10-RELEASE. And the tests do fail:
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd10.0
Thread model: posix

(In reply to arcade from comment #41)
> http://limbo.xim.bz/libgcrypt/libgcrypt.gdb.out
>
> Now it looks obvious: RdRand is an Intel instruction and doesn't exist in
> AMD chips.
Thanks, very cool that you found the cause. I have an AMD system to test this. Probably --disable-drng-support will help.

(In reply to Gerard Seibert from comment #43)
> I have a system using an AMD chip:
[...]
> Should I assume that I cannot build libgcrypt ohn this system?
You can build it, but programs using it will probably not work.
Please test and confirm.
If you add
CONFIGURE_ARGS+= --disable-drng-support
to the ports makefile, and build it, do programms work ?

(In reply to Kurt Jaeger from comment #44)
> (In reply to Gerard Seibert from comment #43)
> > I have a system using an AMD chip:
> [...]
> > Should I assume that I cannot build libgcrypt ohn this system?
>
> You can build it, but programs using it will probably not work.
> Please test and confirm.
>
> If you add
>
> CONFIGURE_ARGS+= --disable-drng-support
>
> to the ports makefile, and build it, do programms work ?
I placed it here:
.elif ${ARCH} == "amd64"
.if (${OSVERSION} < 900000)
USE_GCC= yes
CONFIGURE_ARGS+= --disable-drng-support
.endif
Is that correct?