Bug 166388
| Summary: | security/libgcrypt is broken | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | glevand <geoffrey.levand> | ||||
| Component: | Individual Port(s) | Assignee: | Mark Linimon <linimon> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
glevand
2012-03-25 11:50:11 UTC
Maintainer of security/libgcrypt,
Please note that PR ports/166388 has just been submitted.
If it contains a patch for an upgrade, an enhancement or a bug fix
you agree on, reply to this email stating that you approve the patch
and a committer will take care of it.
The full text of the PR can be found at:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/166388
--
Edwin Groothuis via the GNATS Auto Assign Tool
edwin@FreeBSD.org
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool) Hi, At Sun, 25 Mar 2012 12:17:14 UT, Edwin Groothuis wrote: > > Maintainer of security/libgcrypt, > > Please note that PR ports/166388 has just been submitted. It looks like a ppc (or ppc64) specific problem. I don't have PowerPC environment to reproduce the problem at this moment. Could you please tell me (if it's possible) that building security/libgcrypt with 9.0-RELEASE, too? Regards, -- Hirohisa Yamaguchi umq@ueo.co.jp Hirohisa: did you want this marked 'BROKEN in ppc' for now?? wait for an upstream fix? secondary architectures are problematic (and we have just discussed this in ports@ in fact). We don't have enough resources, and there are no tinderbox's even for ports committers to try this. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell Responsible Changed From-To: freebsd-ports-bugs->scheidell I'll take it. Hirohisa: I propose the attached patched, and this for commit log: - Mark Broken for ppc - Remove check for obsolete, unsupported OS version - pet portlint (space/vs tab, like 41, 44 of Makefile) -- Michael Scheidell, CTO SECNAP Network Security Corporation http://people.freebsd.org/~scheidell ______________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ ______________________________________________________________________ ping? ok to commit? -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell Author: scheidell Date: Tue Jul 24 15:51:26 2012 New Revision: 301475 URL: http://svn.freebsd.org/changeset/ports/301475 Log: - Mark Broken for ppc - Remove check for obsolete, unsupported OS version - pet portlint (space/vs tab, like 41, 44 of Makefile) PR: ports/166388 Submitted by: scheidell@ (me) Reported by: glevand <geoffrey.levand@mail.ru> Approved by: maintainer (timeout, 21 days) Modified: head/security/libgcrypt/Makefile (contents, props changed) Modified: head/security/libgcrypt/Makefile ============================================================================== --- head/security/libgcrypt/Makefile Tue Jul 24 15:50:12 2012 (r301474) +++ head/security/libgcrypt/Makefile Tue Jul 24 15:51:26 2012 (r301475) @@ -35,16 +35,14 @@ INFO= gcrypt .if ${ARCH} == "powerpc" CONFIGURE_ARGS+= --disable-asm +BROKEN= will not compile. See pr ports/166388 .elif ${ARCH} == "i386" .if (${OSVERSION} < 900033) -CONFIGURE_ARGS+= --disable-aesni-support +CONFIGURE_ARGS+= --disable-aesni-support #workaround for FreeBSD 10.0 .elif (${OSVERSION} >= 1000000) -CONFIGURE_ARGS+= --disable-asm -.endif +CONFIGURE_ARGS+= --disable-asm .endif -.if (${OSVERSION} < 700000) -CONFIGURE_ARGS+= --disable-padlock-support .endif post-patch: _______________________________________________ svn-ports-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-ports-all To unsubscribe, send any mail to "svn-ports-all-unsubscribe@freebsd.org" State Changed From-To: feedback->closed Committed. This fix also worked for me on Mac Mini G4, FreeBSD 9.1-PRERELEASE = FreeBSD 9.1-PRERELEASE #0: Regards Pasi FYI, the port builds fine on FreeBSD-9.1-RELENG_9-20120830-JPSNAP-powerpc-powerpc-release. I simply commented out the BROKEN line, and it built and installed without incident on an iBook G4. Maybe BROKEN should be restricted to FreeBSD 10? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jason W. Bacon jwbacon@tds.net http://personalpages.tds.net/~jwbacon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I can confirm that libgcrypt builds fine on FreeBSD/powerpc and = FreeBSD/powerpc64 (9.0-RELEASE and 9.1RC1). Regards. -- Mathias State Changed From-To: closed->open re-open and take. Responsible Changed From-To: scheidell->linimon State Changed From-To: open->feedback I have unmarked the port as broken on 7/8/9. Can anyone confirm whether or not it builds for them on 10? The cluster is not yet set up to try powerpc-10 builds. State Changed From-To: feedback->closed Feedback timeout. Responsible Changed From-To: linimon->linimon libgcrypt does build on ppc -CURRENT, it has built fine for both powerpc and powerpc64 for a while now. This PR recently came to my attention when I encountered the same problem. The issue seems to affect Clang (now used by default in 10-CURRENT) and newer versions of GCC (4.6+). Clang complains about several more unavailable reloc types than newer GCC versions, though. By using system-included GCC, I was able to get this port to compile successfully on PPC32 and 64. I'm in favor of treating this as a communication problem between these new(er) compilers and the system linker, since the compilers seem to be creating binaries that /usr/bin/ld thinks are invalid. Using the linkers from each newer GCC version did not correct the problem. In the mean time, we could simply set a conditional in /usr/ports/security/libgcrypt/Makefile that forces usage of the bundled GCC if ARCH is powerpc[64]. Sincerely, Guy M. Broome At Fri, 06 Apr 2012 04:48:46 +0900 Hirohisa Yamaguchi wrote: > Hi, > > At Sun, 25 Mar 2012 12:17:14 UT, > Edwin Groothuis wrote: > > > > Maintainer of security/libgcrypt, > > > > Please note that PR ports/166388 has just been submitted. > > It looks like a ppc (or ppc64) specific problem. > > I don't have PowerPC environment to reproduce the problem at this > moment. > Could you please tell me (if it's possible) that building > security/libgcrypt with 9.0-RELEASE, too? > > > Regards, > -- > > Hirohisa Yamaguchi > umq at ueo.co.jp <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs> |
