public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "H.Merijn Brand" <h.m.brand@hccnet.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/5917: [hpux 11.0 64bit] Building gcc-3.0.4 (bootstrap) using gcc-3.0.2/64 and binutils-2.12 fails
Date: Tue, 31 Dec 2002 05:36:00 -0000	[thread overview]
Message-ID: <20021231133601.23174.qmail@sources.redhat.com> (raw)

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

From: "H.Merijn Brand" <h.m.brand@hccnet.nl>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc: "John David Anglin" <dave@hiauly1.hia.nrc.ca>, law@redhat.com
Subject: Re: bootstrap/5917: [hpux 11.0 64bit] Building gcc-3.0.4 (bootstrap) using gcc-3.0.2/64 and binutils-2.12 fails
Date: Tue, 31 Dec 2002 14:34:43 +0100

 On Thu 21 Nov 2002 15:57, bangerth@dealii.org wrote:
 > Synopsis: [hpux 11.0 64bit] Building gcc-3.0.4 (bootstrap) using gcc-3.0.2/64 and binutils-2.12 fails
 > 
 > State-Changed-From-To: feedback->closed
 > State-Changed-By: bangerth
 > State-Changed-When: Thu Nov 21 06:57:18 2002
 > State-Changed-Why:
 >     Works now. 
 >     
 >     With regard to the warning: I don't know how important they
 >     are to the gcc developers, but if it does not take too
 >     long, why don't you send a summary to gcc@gcc.gnu.org
 >     and/or to the maintainers of your platform?
 >     
 >     W.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5917
 
 20021230 on 11.00 building with gcc-3.3 (20021216) & binutils-2.13.2 both
 32bit, I saw during the configure phase:
 
 
 checking linker read-only and read-write section mixing... conftest1.s: Assembler messages:
 conftest1.s:1: Warning: rest of line ignored; first ignored character is `"'
 conftest2.s: Assembler messages:
 conftest2.s:1: Warning: rest of line ignored; first ignored character is `"'
 conftest2.s:2: Warning: rest of line ignored; first ignored character is `1'
 conftest3.s: Assembler messages:
 conftest3.s:1: Warning: rest of line ignored; first ignored character is `"'
 conftest3.s:2: Warning: rest of line ignored; first ignored character is `0'
 /usr/ccs/bin/ld: (Warning) Can't hide symbol "ared"
 /usr/ccs/bin/ld: No $UNWIND_END$ subspace has been defined (probably missing /usr/ccs/lib/crt0.o)
 unknown
 checking linker PT_GNU_EH_FRAME support... no
 
 -- 
 H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
 using perl-5.6.1, 5.8.0 & 633 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
   WinNT 4, Win2K pro & WinCE 2.11.  Smoking perl CORE: smokers@perl.org
 http://archives.develooper.com/daily-build@perl.org/   perl-qa@perl.org
 send smoke reports to: smokers-reports@perl.org, QA: http://qa.perl.org
 
 


             reply	other threads:[~2002-12-31 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31  5:36 H.Merijn Brand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-31 16:06 John David Anglin
2002-11-30 18:16 H.Merijn Brand
2002-11-29  6:08 bangerth

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=20021231133601.23174.qmail@sources.redhat.com \
    --to=h.m.brand@hccnet.nl \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).