public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Fix configure check for source locations
Date: Tue, 10 Aug 2004 22:53:00 -0000	[thread overview]
Message-ID: <jeu0vasj03.fsf@sykes.suse.de> (raw)

On ia64 the nop instruction is spelled "nop 0".  Also fixes a missing pair
of parens.

Andreas.

2004-08-11  Andreas Schwab  <schwab@suse.de>

	* configure.in: Fix libc_cv_cpp_asm_debuginfo test for ia64 and
	add missing parens.

--- configure.in	09 Aug 2004 11:13:44 +0200	1.419
+++ configure.in	11 Aug 2004 00:46:18 +0200	
@@ -1669,16 +1669,19 @@ foo:
 	/* Unfortunately this test only works for a real instruction,
 	   not for any of the machine-independent pseudo-ops.
 	   So we just have to assume everybody has a "nop".  */
+#ifdef __ia64__
+#define nop nop 0
+#endif
 	nop
 	/* comment */
 	nop
 	/* comment */
 	nop
 EOF
-if AC_TRY_COMMAND([${CC-cc} $CPPFLAGS $ASFLAGS -g -c conftest.S 1>&AS_MESSAGE_LOG_FD]) &&
+if AC_TRY_COMMAND([${CC-cc} $CPPFLAGS $ASFLAGS -g -c conftest.S 1>&AS_MESSAGE_LOG_FD]) && {
    ac_pattern='conftest\.S'
    AC_TRY_COMMAND([readelf --debug-dump=line conftest.o |
-		   grep $ac_pattern 1>&AS_MESSAGE_LOG_FD]); then
+		   grep $ac_pattern 1>&AS_MESSAGE_LOG_FD]); }; then
   libc_cv_cpp_asm_debuginfo=yes
 else
   libc_cv_cpp_asm_debuginfo=no

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

             reply	other threads:[~2004-08-10 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 22:53 Andreas Schwab [this message]
2004-08-12  6:14 ` Roland McGrath
2004-08-12 16:46   ` Andreas Schwab

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=jeu0vasj03.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=libc-hacker@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).