* Build status page:Succes and failures.
@ 2001-12-07 7:52 Gcc k6 testing account
2001-12-07 9:40 ` Joe Buck
0 siblings, 1 reply; 13+ messages in thread
From: Gcc k6 testing account @ 2001-12-07 7:52 UTC (permalink / raw)
To: gcc
Ave gcc people.
I'm following the build status page discussion and here are my 2 cents.
When 3.0.2 was released I reported a succesfull build on
k6-redhat-linux-gnu and submitted the testresults with
test_summary.(October 24). Following this discussion,I tried to build 3.0
and 3.0.1. Those bootstraps were NOT succesfull.
So here's the summary on the k6 side.
gcc-3.0 -->No bootstrap.
gcc-3.0.1 -->No bootstrap.
gcc-3.0.2 -->Succsesfull bootstrap.
gcc-3.0.x-cvs -->Succesfull bootstrap.
gcc-3.1-cvs -->Succesfull bootstrap.
All this with:
gcc : 2.96-97
binutils : 2.11.90.0.8
glibc : 2.2.4
So maybe there could be a warning note on the build status page that
k6-redhat-linux-gnu bootstraps succesfully from 3.0.2 on. Just like
s390-linux-gnu starts to bootstrap from 3.0.1 on.
Greetinx
Martijn Uffing
(please only reply to the list. This is a send only email-account)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-07 7:52 Build status page:Succes and failures Gcc k6 testing account
@ 2001-12-07 9:40 ` Joe Buck
2001-12-12 10:35 ` Janis Johnson
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
0 siblings, 2 replies; 13+ messages in thread
From: Joe Buck @ 2001-12-07 9:40 UTC (permalink / raw)
To: Gcc k6 testing account; +Cc: gcc
Martijn Uffing writes:
> I'm following the build status page discussion and here are my 2 cents.
>
> When 3.0.2 was released I reported a succesfull build on
> k6-redhat-linux-gnu and submitted the testresults with
> test_summary.(October 24). Following this discussion,I tried to build 3.0
> and 3.0.1. Those bootstraps were NOT succesfull.
>
> So here's the summary on the k6 side.
>
> gcc-3.0 -->No bootstrap.
> gcc-3.0.1 -->No bootstrap.
> gcc-3.0.2 -->Succsesfull bootstrap.
>
> gcc-3.0.x-cvs -->Succesfull bootstrap.
> gcc-3.1-cvs -->Succesfull bootstrap.
>
> All this with:
> gcc : 2.96-97
> binutils : 2.11.90.0.8
> glibc : 2.2.4
Janis, given this I repeat my request that the build status page be
specific about which releases were tested. I realize that you may not
have some of the details that came in before, but at least from here
on out the information should not be thrown away.
Also, the page should not assume no regressions (that is, we should not
assume that because 3.0.1 was tested, we know that 3.0.2 works, unless
we have a report confirming that it does).
Joe
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-07 9:40 ` Joe Buck
@ 2001-12-12 10:35 ` Janis Johnson
2001-12-13 12:29 ` Gerald Pfeifer
2001-12-15 10:43 ` John Marshall
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
1 sibling, 2 replies; 13+ messages in thread
From: Janis Johnson @ 2001-12-12 10:35 UTC (permalink / raw)
To: Joe Buck; +Cc: Gcc k6 testing account, gcc
On Fri, Dec 07, 2001 at 09:38:22AM -0800, Joe Buck wrote:
> Martijn Uffing writes:
>
> > I'm following the build status page discussion and here are my 2 cents.
> >
> > When 3.0.2 was released I reported a succesfull build on
> > k6-redhat-linux-gnu and submitted the testresults with
> > test_summary.(October 24). Following this discussion,I tried to build 3.0
> > and 3.0.1. Those bootstraps were NOT succesfull.
[snip]
> >
> Janis, given this I repeat my request that the build status page be
> specific about which releases were tested. I realize that you may not
> have some of the details that came in before, but at least from here
> on out the information should not be thrown away.
>
> Also, the page should not assume no regressions (that is, we should not
> assume that because 3.0.1 was tested, we know that 3.0.2 works, unless
> we have a report confirming that it does).
The build reports are all out there in the mail archives, except for the
first couple that were in Gerald's original version of the list, and
I've put together a new version of the list that includes links to those
reports. Some of the reports include useful additional information, and
keeping links to them will encourage future reports to include even more
relevant information.
Joe and Gerald, what do you think of the new format? I'll check in the
changes when I hear from both of you.
Janis
P.S. What's the tool that's supposed to be used now to check the
validity of html files?
Index: buildstat.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/buildstat.html,v
retrieving revision 1.54
diff -u -p -r1.54 buildstat.html
--- buildstat.html 2001/12/12 00:00:46 1.54
+++ buildstat.html 2001/12/12 18:14:47
@@ -7,292 +7,421 @@
<body>
<h1 align="center">Build status for GCC 3.0</h1>
-<p>This list covers GCC 3.0 and all 3.0.x releases.</p>
+<p>This list summarizes build reports for GCC 3.0*, with links to the
+archived mail messages that reported the builds.</p>
<table>
<tr>
<td>alpha-dec-osf4.0d</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
+</tr>
<tr>
<td>alpha-dec-osf4.0f</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00536.html">3.0.1</a></td>
</tr>
<tr>
<td>alpha-dec-osf5.1</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00421.html">3.0</a></td>
</tr>
<tr>
<td>alpha-pld-linux-gnu</td>
-<td>Successful (PLD devel 1.0, glibc 2.2.3, kernel 2.2.19)</td>
+<td>PLD devel 1.0, glibc 2.2.3, kernel 2.2.19</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00161.html">3.0.1</a></td>
</tr>
<tr>
<td>alphaev5-dec-osf4.0e</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-12/msg00224.html">3.0.2</a></td>
</tr>
<tr>
<td>alphaev5-dec-osf5.1</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg01289.html">3.0</a></td>
</tr>
<tr>
<td>alphaev56-dec-osf4.0b</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00481.html">3.0</a></td>
</tr>
<tr>
<td>alphaev56-unknown-linux-gnu</td>
-<td>Successful (Red Hat 6.2)</td>
+<td>Red Hat 6.2</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01020.html">3.0.1</a></td>
</tr>
<tr>
<td>alphaev67-dec-osf5.1</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00432.html">3.0</a></td>
</tr>
<tr>
<td>alphaev67-unknown-linux-gnu</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00230.html">3.0</a></td>
</tr>
<tr>
<td>hppa1.1-hp-hpux10.10</td>
-<td>Successful (except fastjar)</td>
+<td> </td>
+<td>Successful (except fastjar):
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00231.html">3.0.1</a></td>
</tr>
<tr>
<td>hppa1.1-hp-hpux10.20</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg00881.html">3.0</a></td>
</tr>
<tr>
<td>hppa1.1-hp-hpux11.00</td>
-<td>Successful (C and C++)</td>
+<td> </td>
+<td>Successful (C and C++):
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00877.html">3.0.1</a></td>
</tr>
<tr>
<td>hppa2.0-hp-hpux10.20</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00390.html">3.0</a></td>
</tr>
<tr>
<td>hppa2.0w-hp-hpux11.00</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg00193.html">3.0</a></td>
</tr>
<tr>
<td>hppa64-hp-hpux11.00</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00934.html">3.0.1</a>,
+<a href="http://gcc.gnu.org/ml/gcc/2001-11/msg01633.html">3.0.2</a></td>
</tr>
<tr>
<td>i386-pc-sco3.2v5.0.4</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful (C, C++, F77):
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00175.html">3.0</a></td>
</tr>
<tr>
<td>i386-pc-solaris2.6</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00734.html">3.0.1</a></td>
</tr>
<tr>
<td>i386-pc-solaris2.8</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00350.html">3.0</a></td>
</tr>
<tr>
<td>i386-pld-linux-gnu</td>
-<td>Successful (PLD devel 1.0, glibc 2.2.3, kernel 2.2.19)</td>
+<td>PLD devel 1.0, glibc 2.2.3, kernel 2.2.19</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00161.html">3.0.1</a></td>
</tr>
<tr>
<td>i386-redhat-linux-gnu</td>
-<td>Successful (WinLinux 2001)</td>
+<td>WinLinux 2001</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00742.html">3.0.1</a></td>
</tr>
<tr>
<td>i386-unknown-freebsd4.2</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-11/msg00949.html">3.0</a></td>
</tr>
<tr>
<td>i386-unknown-freebsd4.3</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful: 3.0</td>
</tr>
<tr>
<td>i586-pc-cygwin</td>
-<td>Successful</td>
+<td>Cygwin 1.3.2, Win98</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00026.html">3.0</a></td>
</tr>
<tr>
<td>i586-pc-linux-gnu</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00152.html">3.0</a></td>
</tr>
<tr>
<td>i586-pc-linux-gnu</td>
-<td>Successful (Caldera OpenLinux 2.2)</td>
+<td>Caldera OpenLinux 2.2</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00805.html">3.0.1</a></td>
</tr>
<tr>
<td>i586-pc-linux-gnu (k6)</td>
-<td>Successful (Red Hat 7.0, glibc 2.2.4)</td>
+<td>Red Hat 7.0, glibc 2.2.4</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-11/msg00214.html">3.0.2</a>;
+Unsuccessful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-12/msg00363.html">3.0 and 3.0.1</a></td>
</tr>
<tr>
<td>i586-pld-linux-gnu</td>
-<td>Successful (PLD devel 1.0, glibc 2.2.3, kernel 2.2.19)</td>
+<td>PLD devel 1.0, glibc 2.2.3, kernel 2.2.19</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00161.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-cygwin</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00314.html">3.0</a></td>
+</tr>
+
+<tr>
+<td>i686-pc-linux-gnu</td>
+<td>Caldera 2.4, glibc 2.1.2</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00863.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Caldera 2.4, glibc 2.1.2)</td>
+<td>Debian 2.2, glibc 2.1.3</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00206.html">3.0.1</a>,
+<a href="http://gcc.gnu.org/ml/gcc/2001-11/msg00206.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Debian 2.2, glibc 2.1.3)</td>
+<td>Mandrake 8.0, glibc 2.2.4</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00895.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Mandrake 8.0, glibc 2.2.4)</td>
+<td>Mandrake 8.1, glibc 2.2.4</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-11/msg00843.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Mandrake 8.1, glibc 2.2.4)</td>
+<td>Red Hat 6.2</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Red Hat 6.2)</td>
+<td>Red Hat 7.1</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Red Hat 7.1, glibc 2.2, kernel 2.4.10)</td>
+<td>Red Hat 7.1, glibc 2.2.2, kernel 2.4.9-12</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-12/msg00389.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Red Hat 7.1, glibc 2.2.2, kernel 2.4.9-12)</td>
+<td>Red Hat 7.1, glibc 2.2, kernel 2.4.10</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg01588.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Red Hat 7.2, glibc 2.2.4, kernel 2.4.13)</td>
+<td>Red Hat 7.2, glibc 2.2.4, kernel 2.4.13</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg01528.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (Slackware 8.0, glibc 2.2.3)</td>
+<td>Slackware 8.0, glibc 2.2.3</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg01189.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (SuSE 6.2, glibc 2.1.1, kernel 2.2.19)</td>
+<td>SuSE 6.2, glibc 2.1.1, kernel 2.2.19</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-11/msg00016.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (SuSE 7.0, glibc 2.1)</td>
+<td>SuSE 7.0, glibc 2.1, kernel 2.2.16</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00148.html">3.0.1</a></td>
</tr>
<tr>
<td>i686-pc-linux-gnu</td>
-<td>Successful (SuSE 7.2, glibc 2.2)</td>
+<td>SuSE 7.2, glibc 2.2</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg01481.html">3.0.2</a></td>
</tr>
<tr>
<td>i686-pld-linux-gnu</td>
-<td>Successful (PLD devel 1.0, glibc 2.2.3, kernel 2.2.19)</td>
+<td>PLD devel 1.0, glibc 2.2.3, kernel 2.2.19</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00161.html">3.0.1</a></td>
</tr>
<tr>
<td>ia64-unknown-linux</td>
-<td>Successful (Red Hat 7.1.94, glibc 2.2.4)</td>
+<td>Red Hat 7.1.94, glibc 2.2.4</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-09/msg00863.html">3.0.1</a></td>
</tr>
<tr>
<td>mips-sgi-irix6.2</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
</tr>
<tr>
<td>mips-sgi-irix6.5</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00973.html">3.0</a>,
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
</tr>
<tr>
<td>powerpc-ibm-aix4.2.1.0</td>
-<td>Successful (C and C++)</td>
+<td> </td>
+<td>Successful (C and C++):
+<a href="http://gcc.gnu.org/ml/gcc/2001-12/msg00127.html">3.0.2</a></td>
</tr>
<tr>
<td>powerpc-ibm-aix4.3.2.0</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg00193.html">3.0</a></td>
</tr>
<tr>
<td>powerpc-ibm-aix4.3.3.0</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00647.html">3.0.1</a></td>
</tr>
<tr>
<td>powerpc-unknown-linux-gnu</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-06/msg01914.html">3.0</a></td>
</tr>
<tr>
<td>s390-linux-gnu</td>
-<td>Successful (beginning with 3.0.1; not supported in 3.0)</td>
+<td>Supported beginning with 3.0.1</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01139.html">3.0.1</a></td>
</tr>
<tr>
<td>sparc-linux-gnu</td>
-<td>Successful (Debian)</td>
+<td>Debian</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01349.html">3.0</a></td>
</tr>
<tr>
<td>sparc-pld-linux-gnu</td>
-<td>Successful (PLD devel 1.0, glibc 2.2.3, kernel 2.2.19)</td>
+<td>PLD devel 1.0, glibc 2.2.3, kernel 2.2.19</td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-10/msg00161.html">3.0.1</a></td>
</tr>
<tr>
<td>sparc-sun-solaris2.5.1</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg00760.html">3.0</a></td>
</tr>
<tr>
<td>sparc-sun-solaris2.6</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg00842.html">3.0</a>,
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
</tr>
<tr>
<td>sparc-sun-solaris2.7</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg00973.html">3.0</a>,
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01024.html">3.0.1</a></td>
</tr>
<tr>
<td>sparc-sun-solaris2.8</td>
-<td>Successful</td>
+<td> </td>
+<td>Successful:
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg00941.html">3.0</a>,
+<a href="http://gcc.gnu.org/ml/gcc/2001-08/msg01021.html">3.0.1</a></td>
</tr>
<tr>
<td>sparc-sun-solaris2.* (64 bits)</td>
<td>Not supported</td>
+<td> </td>
</tr>
</table>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Problem with <cstdio> and AIX 4.3.3
2001-12-07 9:40 ` Joe Buck
2001-12-12 10:35 ` Janis Johnson
@ 2001-12-12 11:59 ` Chip Cuntz
2001-12-12 12:20 ` David Edelsohn
2001-12-12 14:48 ` David Edelsohn
1 sibling, 2 replies; 13+ messages in thread
From: Chip Cuntz @ 2001-12-12 11:59 UTC (permalink / raw)
To: gcc
Not sure this is the right place, but here goes. I am having a problem with
a file fixincludes created. The following are the lines in question from
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h and the
error excerpt from the complier.
Any ideas would be greatly appreciated...
...
262
263 #ifdef _DUMMY_VA_LIST
264 extern int vfprintf(FILE *, const char *, __gnuc_va_list);
265 extern int vprintf(const char *, __gnuc_va_list);
266 extern int vsprintf(char *, const char *, __gnuc_va_list);
267 #if (_XOPEN_SOURCE == 500)
268 extern int vsnprintf(char *, size_t, const char *, __gnuc_va_list);
269 #endif /* _XOPEN_SOURCE == 500 */
270 #else
271 #define _HIDDEN_DUMMY_VA_LIST /* define a type not in the
namespace */
272 #include <va_list.h>
273 extern int vfprintf(FILE *, const char *, __gnuc_va_list);
274 extern int vprintf(const char *, __gnuc_va_list);
275 extern int vsprintf(char *, const char *, __gnuc_va_list);
276 #if (_XOPEN_SOURCE == 500)
277 extern int vsnprintf(char *, size_t, const char *, __gnuc_va_list);
278 #endif /* _XOPEN_SOURCE == 500 */
279 #endif /* _DUMMY_VA_LIST */
...
The error message...
|| Compiling com_bmf.c
|| g++ -c -I/usr/include -I../include -D__AIX__ -D__UNIX__ com_bmf.c
|| In file included from /usr/local/include/g++-v3/bits/std_cstdio.h:41,
|| from /usr/local/include/g++-v3/cstdio:31,
|| from ../include/com_os.h:61,
|| from ../include/com_gen.h:29,
|| from ../include/com_ehs.h:38,
|| from ../include/com_bmf.h:32,
|| from com_bmf.c:25:
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|273| type
|| specifier omitted for parameter
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|274| type
|| specifier omitted for parameter
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|275| type
|| specifier omitted for parameter
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|277| type
|| specifier omitted for parameter
|| In file included from /usr/local/include/g++-v3/bits/std_cstdio.h:41,
|| from /usr/local/include/g++-v3/cstdio:31,
|| from ../include/com_os.h:61,
|| from ../include/com_gen.h:29,
|| from ../include/com_ehs.h:38,
|| from ../include/com_bmf.h:32,
|| from com_bmf.c:25:
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|465| type
|| specifier omitted for parameter
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|466| type
|| specifier omitted for parameter
/usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.0.1/include/stdio.h|467| type
|| specifier omitted for parameter
|| make: 1254-004 The error code from the last command is 1.
||
||
|| Stop.
Chip Cuntz
Worldcom
v622.1305/719.535.1305
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Problem with <cstdio> and AIX 4.3.3
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
@ 2001-12-12 12:20 ` David Edelsohn
2001-12-12 14:48 ` David Edelsohn
1 sibling, 0 replies; 13+ messages in thread
From: David Edelsohn @ 2001-12-12 12:20 UTC (permalink / raw)
To: Chip Cuntz; +Cc: gcc
Your message does not include enough information to investigate
the problem. Assuming the problem is the use of __gnuc_va_list, that
should have been defined in stdarg.h included at the top of the fixed
version of stdio.h.
David
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Problem with <cstdio> and AIX 4.3.3
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
2001-12-12 12:20 ` David Edelsohn
@ 2001-12-12 14:48 ` David Edelsohn
2001-12-12 15:51 ` Joe Buck
1 sibling, 1 reply; 13+ messages in thread
From: David Edelsohn @ 2001-12-12 14:48 UTC (permalink / raw)
To: Chip Cuntz; +Cc: gcc
>>>>> "Chip Cuntz" writes:
Chip> g++ -c -I/usr/include -I../include -D__AIX__ -D__UNIX__ com_bmf.c
I just noticed something suspicious about your commandline: why
are you explicitly adding -I/usr/include? The compiler implicitly
searches that directory already. Your adding it to the commandline is
altering the search order, probably causing GCC to find a different
version of some header file than its own, internal version.
David
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Problem with <cstdio> and AIX 4.3.3
2001-12-12 14:48 ` David Edelsohn
@ 2001-12-12 15:51 ` Joe Buck
0 siblings, 0 replies; 13+ messages in thread
From: Joe Buck @ 2001-12-12 15:51 UTC (permalink / raw)
To: David Edelsohn; +Cc: Chip Cuntz, gcc
> >>>>> "Chip Cuntz" writes:
>
> Chip> g++ -c -I/usr/include -I../include -D__AIX__ -D__UNIX__ com_bmf.c
David Edelsohn writes:
> I just noticed something suspicious about your commandline: why
> are you explicitly adding -I/usr/include? The compiler implicitly
> searches that directory already. Your adding it to the commandline is
> altering the search order, probably causing GCC to find a different
> version of some header file than its own, internal version.
David's objection is not strong enough. For C++, any attempt to put
-I/usr/include on the command line, and then to include standard headers,
is likely to fail, unless your OS populates /usr/include only with ISO C++
compliant headers designed to work with g++. This pretty much means that
if you do this on any proprietary operating system, as well as most free
ones, it will fail.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-12 10:35 ` Janis Johnson
@ 2001-12-13 12:29 ` Gerald Pfeifer
2001-12-13 13:15 ` Janis Johnson
2001-12-13 16:54 ` Joe Buck
2001-12-15 10:43 ` John Marshall
1 sibling, 2 replies; 13+ messages in thread
From: Gerald Pfeifer @ 2001-12-13 12:29 UTC (permalink / raw)
To: Janis Johnson; +Cc: Joe Buck, Gcc k6 testing account, gcc, Zack Weinberg
On Wed, 12 Dec 2001, Janis Johnson wrote:
> Joe and Gerald, what do you think of the new format? I'll check in the
> changes when I hear from both of you.
I had a look, and it really seems fine -- thanks for the (large) amount of
work that you have put into this!
> P.S. What's the tool that's supposed to be used now to check the
> validity of html files?
Personally, I mostly use validator.w3.org. IIRC Zack had a nice
description on how to perform such a test which was part of a larger
patch which required some splitting and I believe he didn't have the
time to commit this part yet...
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-13 12:29 ` Gerald Pfeifer
@ 2001-12-13 13:15 ` Janis Johnson
2001-12-13 16:54 ` Joe Buck
1 sibling, 0 replies; 13+ messages in thread
From: Janis Johnson @ 2001-12-13 13:15 UTC (permalink / raw)
To: Gerald Pfeifer
Cc: Janis Johnson, Joe Buck, Gcc k6 testing account, gcc, Zack Weinberg
On Thu, Dec 13, 2001 at 09:26:34PM +0100, Gerald Pfeifer wrote:
>
> > P.S. What's the tool that's supposed to be used now to check the
> > validity of html files?
>
> Personally, I mostly use validator.w3.org. IIRC Zack had a nice
> description on how to perform such a test which was part of a larger
> patch which required some splitting and I believe he didn't have the
> time to commit this part yet...
OK, I found Zack's description in the gcc-patches archives. The file is
clean, although Zack's patch contains an extraneous semicolon in the
html command to use:
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
^ here
Janis
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-13 12:29 ` Gerald Pfeifer
2001-12-13 13:15 ` Janis Johnson
@ 2001-12-13 16:54 ` Joe Buck
2001-12-13 17:38 ` Janis Johnson
1 sibling, 1 reply; 13+ messages in thread
From: Joe Buck @ 2001-12-13 16:54 UTC (permalink / raw)
To: Gerald Pfeifer
Cc: Janis Johnson, Joe Buck, Gcc k6 testing account, gcc, Zack Weinberg
On Wed, 12 Dec 2001, Janis Johnson wrote:
> > Joe and Gerald, what do you think of the new format? I'll check in the
> > changes when I hear from both of you.
Gerald wrote:
> I had a look, and it really seems fine -- thanks for the (large) amount of
> work that you have put into this!
OK with me too, and thanks for taking care of this.
Joe
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-13 16:54 ` Joe Buck
@ 2001-12-13 17:38 ` Janis Johnson
0 siblings, 0 replies; 13+ messages in thread
From: Janis Johnson @ 2001-12-13 17:38 UTC (permalink / raw)
To: Joe Buck
Cc: Gerald Pfeifer, Janis Johnson, Gcc k6 testing account, gcc,
Zack Weinberg
On Thu, Dec 13, 2001 at 04:26:36PM -0800, Joe Buck wrote:
>
> On Wed, 12 Dec 2001, Janis Johnson wrote:
> > > Joe and Gerald, what do you think of the new format? I'll check in the
> > > changes when I hear from both of you.
>
> Gerald wrote:
> > I had a look, and it really seems fine -- thanks for the (large) amount of
> > work that you have put into this!
>
> OK with me too, and thanks for taking care of this.
OK, it's in, ready for the flood of new reports for 3.0.3 in a few days.
Janis
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-12 10:35 ` Janis Johnson
2001-12-13 12:29 ` Gerald Pfeifer
@ 2001-12-15 10:43 ` John Marshall
2001-12-17 9:08 ` Janis Johnson
1 sibling, 1 reply; 13+ messages in thread
From: John Marshall @ 2001-12-15 10:43 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc
This is pretty trivial, but might save some people some time.
On Wed, Dec 12, 2001 at 10:34:25AM -0800, Janis Johnson wrote:
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/buildstat.html,v
[...]
> +<p>This list summarizes build reports for GCC 3.0*, with links to the
> +archived mail messages that reported the builds.</p>
"3.0*" looks like a footnote reference, and I spent some time hunting
at the bottom of the page for a footnote. Maybe it would be better
written as "3.0.x", which is how the same thing is written on, e.g.,
http://gcc.gnu.org/gcc-3.0/ .
John
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Build status page:Succes and failures.
2001-12-15 10:43 ` John Marshall
@ 2001-12-17 9:08 ` Janis Johnson
0 siblings, 0 replies; 13+ messages in thread
From: Janis Johnson @ 2001-12-17 9:08 UTC (permalink / raw)
To: John Marshall; +Cc: Janis Johnson, gcc
On Sat, Dec 15, 2001 at 05:16:55PM +0100, John Marshall wrote:
> This is pretty trivial, but might save some people some time.
>
> On Wed, Dec 12, 2001 at 10:34:25AM -0800, Janis Johnson wrote:
> > RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/buildstat.html,v
> [...]
> > +<p>This list summarizes build reports for GCC 3.0*, with links to the
> > +archived mail messages that reported the builds.</p>
>
> "3.0*" looks like a footnote reference, and I spent some time hunting
> at the bottom of the page for a footnote. Maybe it would be better
> written as "3.0.x", which is how the same thing is written on, e.g.,
> http://gcc.gnu.org/gcc-3.0/ .
Thanks for the suggestion; it was trivial to fix and I'm all for saving
people's time.
Janis
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2001-12-17 16:35 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-07 7:52 Build status page:Succes and failures Gcc k6 testing account
2001-12-07 9:40 ` Joe Buck
2001-12-12 10:35 ` Janis Johnson
2001-12-13 12:29 ` Gerald Pfeifer
2001-12-13 13:15 ` Janis Johnson
2001-12-13 16:54 ` Joe Buck
2001-12-13 17:38 ` Janis Johnson
2001-12-15 10:43 ` John Marshall
2001-12-17 9:08 ` Janis Johnson
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
2001-12-12 12:20 ` David Edelsohn
2001-12-12 14:48 ` David Edelsohn
2001-12-12 15:51 ` Joe Buck
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).