public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
@ 2003-05-09 23:06 Dara Hazeghi
0 siblings, 0 replies; 5+ messages in thread
From: Dara Hazeghi @ 2003-05-09 23:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9989; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, struppi@acm.org
Cc:
Subject: Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
Date: Fri, 9 May 2003 16:03:54 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=9989
Hello,
can the submitter please confirm whether this bug is still present
building recent gcc 3.3 sources? Thanks,
Dara
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
@ 2003-03-10 15:46 John David Anglin
0 siblings, 0 replies; 5+ messages in thread
From: John David Anglin @ 2003-03-10 15:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9989; it has been noted by GNATS.
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: stefan.rupp@inform-ac.com (Stefan Rupp)
Cc: danglin@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
struppi@acm.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
Date: Mon, 10 Mar 2003 10:41:39 -0500 (EST)
> Is there any patch ID you can provide? I am unfamiliar with HPUX.
I have PHCO_26111 installed. You can get patches via anonymous ftp at
ftp.itrc.hp.com. The ftp site has a catalog in each patch directory
which is useful for locating relevant patches. Web access is at
<http://us-support3.external.hp.com/common/bin/doc.pl/distrib_redir=2+1047309820|*>.
You will need to create an account but you don't need a service
contract to download individual patches. When you get patches via the
web, dependent patches will automatically be included in your download
and a script is included to build a depot containing all the downloaded
patches.
Read the hpux section in the installation documentation. You probably
also need the latest sed, make and linker patches. I always use GNU
make for my builds.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
@ 2003-03-10 9:56 Stefan Rupp
0 siblings, 0 replies; 5+ messages in thread
From: Stefan Rupp @ 2003-03-10 9:56 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9989; it has been noted by GNATS.
From: Stefan Rupp <stefan.rupp@inform-ac.com>
To: danglin@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
struppi@acm.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
Date: Mon, 10 Mar 2003 10:52:25 +0100
Shalom!
danglin@gcc.gnu.org wrote:
> Synopsis: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
[...]
> I suspect that you haven't applied the latest header patch,
> or possibly stdio.h has been edited.
[...]
> If there is a problem, more details are needed.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9989
Is there any patch ID you can provide? I am unfamiliar with HPUX.
Thanks alot!
Regards,
Stefan
--
Stefan Rupp Phone: +49 (0) 2408 9456-44
Inform GmbH Fax: +49 (0) 2408 9456-45
Pascalstr. 23, 52076 Aachen, Germany E-Mail: stefan.rupp@inform-ac.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
@ 2003-03-08 1:51 danglin
0 siblings, 0 replies; 5+ messages in thread
From: danglin @ 2003-03-08 1:51 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, struppi
Synopsis: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
State-Changed-From-To: open->feedback
State-Changed-By: danglin
State-Changed-When: Sat Mar 8 01:51:21 2003
State-Changed-Why:
I don't see #include <varargs.h> in /usr/include/stdio.h
in the headers that I have for HP-UX 10.20, 11.00 or 11.11.
I suspect that you haven't applied the latest header patch,
or possibly stdio.h has been edited.
Normally, you should see
#ifndef FIXINC_WRAP_STDIO_H_STDIO_STDARG_H
#define FIXINC_WRAP_STDIO_H_STDIO_STDARG_H 1
#define __need___va_list
#include <stdarg.h>
near the beginning of the fixed header. There is no
replacement of "#include <varargs.h>", only a wrap.
If there is a problem, more details are needed.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9989
^ permalink raw reply [flat|nested] 5+ messages in thread
* bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
@ 2003-03-07 14:36 struppi
0 siblings, 0 replies; 5+ messages in thread
From: struppi @ 2003-03-07 14:36 UTC (permalink / raw)
To: gcc-gnats
>Number: 9989
>Category: bootstrap
>Synopsis: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 07 14:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: struppi@acm.org
>Release: unknown-1.0
>Organization:
>Environment:
HPUX 11.00 gcc 3.3 (snapshot 03.03.03)
>Description:
While bootstraping fixinclude fixes stdio.h wrong - it doesn't replaces #include <varargs.h> by #include <stdarg.h>. Same applies for all older 3.x releases.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-05-09 23:06 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-09 23:06 bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails Dara Hazeghi
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 15:46 John David Anglin
2003-03-10 9:56 Stefan Rupp
2003-03-08 1:51 danglin
2003-03-07 14:36 struppi
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).