public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alon Bar-Lev (alonbl)" <alonbl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-crypt/p11-kit/files: p11-kit-0.19.3-build.patch
Date: Sat, 27 Jul 2013 20:24:41 +0000 (UTC)	[thread overview]
Message-ID: <20130727202441.8DEF62171D@flycatcher.gentoo.org> (raw)

alonbl      13/07/27 20:24:41

  Added:                p11-kit-0.19.3-build.patch
  Log:
  Version bump, fixes bug#471956, bug#477486
  
  (Portage version: 2.2.0_alpha190/cvs/Linux x86_64, signed Manifest commit with key BF20DC51)

Revision  Changes    Path
1.1                  app-crypt/p11-kit/files/p11-kit-0.19.3-build.patch

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-crypt/p11-kit/files/p11-kit-0.19.3-build.patch?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-crypt/p11-kit/files/p11-kit-0.19.3-build.patch?rev=1.1&content-type=text/plain

Index: p11-kit-0.19.3-build.patch
===================================================================
[PATCH] do not assume dead code existence in autoconf checks

when compiler optimize source, it removes dead code so a linkage error
in these cases are not visisble.

Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>

--- p11-kit-0.19.3/configure.ac	2013-07-24 11:13:03.000000000 +0300
+++ p11-kit-0.19.3.new/configure.ac	2013-07-27 23:05:53.470534878 +0300
@@ -100,9 +100,9 @@ if test "$os_unix" = "yes"; then
 	                AC_MSG_RESULT([yes])],
 	               [AC_MSG_RESULT([no])])
 	AC_CHECK_DECLS([__progname])
-	AC_LINK_IFELSE([AC_LANG_SOURCE([extern char *__progname; void main() { }])],
+	AC_LINK_IFELSE([AC_LANG_PROGRAM([[extern char *__progname;]], [[__progname=(char*)0;]])],
 		[AC_DEFINE(HAVE___PROGNAME, [1], [Whether __progname available])])
-	AC_LINK_IFELSE([AC_LANG_SOURCE([extern int __libc_enable_secure; void main() { }])],
+	AC_LINK_IFELSE([AC_LANG_PROGRAM([[extern int __libc_enable_secure;]], [[__libc_enable_secure = 0;]])],
 		[AC_DEFINE(HAVE___LIBC_ENABLE_SECURE, [1], [Whether __libc_enable_secure available])])
 fi
 





             reply	other threads:[~2013-07-27 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 20:24 Alon Bar-Lev (alonbl) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-15  6:29 [gentoo-commits] gentoo-x86 commit in app-crypt/p11-kit/files: p11-kit-0.19.3-build.patch Tim Harder (radhermit)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130727202441.8DEF62171D@flycatcher.gentoo.org \
    --to=alonbl@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox