From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Joe Buck <jbuck@synopsys.com>
Cc: gcc@gcc.gnu.org
Subject: Re: non-portable construct in gcc configure script
Date: Sat, 24 May 2003 21:37:00 -0000 [thread overview]
Message-ID: <200305242220.12082.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <20030515180723.A1418@synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
> In the test labeled
>
> AC_MSG_CHECKING(linker read-only and read-write section mixing)
>
> gcc/configure.in in 3.3 uses "grep -A1". This feature is not in Solaris's
> grep. It's not in the HP-UX grep either.
>
> The result is that the configure output looks like
>
>
> checking linker read-only and read-write section mixing... grep: illegal
> option -- A grep: illegal option -- 1
> Usage: grep -hblcnsviw pattern file . . .
>
> on Solaris 2.8. The failure appears harmless, but I'm not sure.
Does the attached patch cure it? The construct works on the 5 Solaris
versions I have access to, but I can't directly test the configure check
because it dies earlier with the native Sun tools.
--
Eric Botcazou
[-- Attachment #2: pr10663-1.diff --]
[-- Type: text/x-diff, Size: 732 bytes --]
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/configure.in,v
retrieving revision 1.627.2.8
diff -u -r1.627.2.8 configure.in
--- configure.in 12 May 2003 18:49:18 -0000 1.627.2.8
+++ configure.in 24 May 2003 20:04:38 -0000
@@ -2319,7 +2319,10 @@
&& $gcc_cv_ld -shared -o conftest1.so conftest1.o \
conftest2.o conftest3.o; then
gcc_cv_ld_ro_rw_mix=`$gcc_cv_objdump -h conftest1.so \
- | grep -A1 myfoosect`
+ | sed -n '/.*myfoosect.*/{
+ N
+ p
+ }'`
if echo "$gcc_cv_ld_ro_rw_mix" | grep CONTENTS > /dev/null; then
if echo "$gcc_cv_ld_ro_rw_mix" | grep READONLY > /dev/null; then
gcc_cv_ld_ro_rw_mix=read-only
next prev parent reply other threads:[~2003-05-24 20:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 1:07 Joe Buck
2003-05-16 9:41 ` Eric Botcazou
2003-05-16 20:35 ` target/10663 (was Re: non-portable construct in gcc configure script) Kelley Cook
2003-05-24 21:37 ` Eric Botcazou [this message]
2003-06-01 17:49 ` non-portable construct in gcc configure script Zack Weinberg
2003-06-01 19:13 ` Eric Botcazou
2003-06-01 19:51 ` Zack Weinberg
2003-06-02 10:23 ` Eric Botcazou
2003-06-02 16:19 ` Zack Weinberg
2003-06-04 8:51 Bonzini
2003-06-04 10:01 ` Eric Botcazou
2003-06-04 16:05 ` Zack Weinberg
2003-06-05 8:55 ` Eric Botcazou
2003-06-05 16:49 ` Zack Weinberg
2003-06-05 20:48 ` Eric Botcazou
2003-06-05 20:49 ` Zack Weinberg
2003-06-05 21:02 ` Eric Botcazou
2003-06-05 21:49 ` Zack Weinberg
2003-06-07 7:46 ` Eric Botcazou
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=200305242220.12082.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.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).