public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Kelley Cook <kcook34@ford.com>
To: jakub@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: target/10663 (was Re: non-portable construct in gcc configure script)
Date: Fri, 16 May 2003 20:26:00 -0000	[thread overview]
Message-ID: <20030516202600.14006.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/10663; it has been noted by GNATS.

From: Kelley Cook <kcook34@ford.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: gcc@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: target/10663 (was Re: non-portable construct in gcc configure script)
Date: Fri, 16 May 2003 16:15:44 -0400

 Joe Buck wrote:
 > 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.
 
 There is another non-portable feature in that exact same test.
 
 I sent a patch for it a few weeks ago, if someone would like to review that
 at the same time.
 
 http://gcc.gnu.org/ml/gcc-patches/2003-04/msg02262.html
 
 --- forward ----
 Cygwin is not completing the "linker read-only and
 read-write section mixing" configure test. It aborts with:
 
 conftest1.s: Assembler messages:
 conftest1.s:1: Warning: rest of line ignored; first ignored
 character is `"'
 
 It seems that Cygwin's "as" doesn't like double-quotes
 surrounding it's section names.  This in itself may or may
 not be a bug, but it that is not what this particular
 conftest is testing.  Regardless, from what I can gather
 from the gas docs not having the quotes should be OK on all
 targets.
 ---- end ----
 
 Kelley Cook
 
 


                 reply	other threads:[~2003-05-16 20:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030516202600.14006.qmail@sources.redhat.com \
    --to=kcook34@ford.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jakub@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).