This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [Make failure with GCC-3.3.X and GCC-3.4.0 on Solaris 8 ] : gmake: *** [all-libiberty] Error 2


Thanks Eric for your reply.

Nothing has changed on the machine and nobody can log on the machine except me.

My boostrap compiler is gcc-2.95.3 and is fully functional !

I re-checked the PATHS and everything is fine but the build always fails.

I tried to make a build on another solaris 8 system and I've got the same error... Solaris 8 patches missing or gcc build bugs ?

Whats' about the parse error ?

In file included from ../../libiberty/fdmatch.c:47:
/usr/include/sys/stat.h:258: error: parse error before "blksize_t"
/usr/include/sys/stat.h:262: error: parse error before '}' token
/usr/include/sys/stat.h:318: error: parse error before "blksize_t"
/usr/include/sys/stat.h:319: error: conflicting types for `st_blocks'
/usr/include/sys/stat.h:259: error: previous declaration of `st_blocks'
/usr/include/sys/stat.h:322: error: parse error before '}' token


Thanks


Any ideas ?

Rgds,

-----Original Message-----
From: Eric Botcazou [mailto:ebotcazou@libertysurf.fr]
Sent: jeudi 27 mai 2004 14:37
To: Suares, Dominique [CTF:CM41:EXCH]
Cc: gcc@gcc.gnu.org
Subject: Re: [Make failure with GCC-3.3.X and GCC-3.4.0 on Solaris 8 ] : gmake: *** [all-libiberty] Error 2



> Since one week, I'm getting a make failure with the following versions > of gcc : 3.3.2, 3.3.3, 3.4.0 on Solaris 8. ( On solaris 2.6 and redhat > 8.0, all these builds are OK )

I think it would be interesting to know what has changed between a week ago
and now on your machine.  Did you check the integrity of the sources?

> My way to proceed :
>
> % > ../configure --prefix=/opt/swe/tools/ext/gnu/gcc-3.3.2
> --exec-prefix=/opt/swe/tools/ext/gnu/gcc-3.3.2/sparc-solaris2.8
> --disable-shared --enable-threads=posix --enable-languages=c,c++,java
>
> The configure seems OK instead that :
>
> checking for iconv declaration...
>           extern size_t iconv (iconv_t cd, const char * *inbuf, size_t
> *inbytesleft, char * *outbuf, size_t *outbytesleft);
> checking whether getenv is declared... no
> checking whether atol is declared... no
> checking whether sbrk is declared... no
> checking whether abort is declared... no
> checking whether atof is declared... no
> checking whether getcwd is declared... no
> checking whether getwd is declared... no
> checking whether strsignal is declared... no
> checking whether putc_unlocked is declared... no
> checking whether fputs_unlocked is declared... no
> checking whether fwrite_unlocked is declared... no
> checking whether fprintf_unlocked is declared... no
> checking whether strstr is declared... no
> checking whether errno is declared... no
> checking whether vasprintf is declared... no
> checking whether malloc is declared... no
> checking whether realloc is declared... no
> checking whether calloc is declared... no
> checking whether free is declared... no
> checking whether basename is declared... no
> checking whether getopt is declared... no
> checking whether clock is declared... no
> checking whether getrlimit is declared... no
> checking whether setrlimit is declared... no
> checking whether getrusage is declared... no
> checking whether times is declared... no
> checking for struct tms... no
> checking for clock_t... no
>
>
> On Solaris 2.6 and on linux, all this checkings are 'yes'
> Any ideas ?

Is your bootstrap compiler fully functional?

--
Eric Botcazou


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]