public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/38383] fails to build cross gcc for target hppa64-hp-hpux11.00
Date: Sat, 13 Dec 2008 00:16:00 -0000 [thread overview]
Message-ID: <20081213001539.30726.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38383-11564@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from danglin at gcc dot gnu dot org 2008-12-13 00:15 -------
Subject: Bug 38383
Author: danglin
Date: Sat Dec 13 00:14:15 2008
New Revision: 142729
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142729
Log:
PR bootstrap/38383
* pa64-hpux.h (LINK_GCC_C_SEQUENCE_SPEC): Don't hardcode search path
for the milli.a library.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/pa/pa64-hpux.h
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38383
next prev parent reply other threads:[~2008-12-13 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 16:06 [Bug bootstrap/38383] New: " r dot emrich at de dot tecosim dot com
2008-12-03 16:10 ` [Bug bootstrap/38383] " r dot emrich at de dot tecosim dot com
2008-12-13 0:16 ` danglin at gcc dot gnu dot org [this message]
2008-12-13 0:20 ` danglin at gcc dot gnu dot org
2008-12-13 0:25 ` danglin at gcc dot gnu dot org
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=20081213001539.30726.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).