Build failure (first installation)

Build failure (first installation)

[Marc Girod]

Hello!

I just started to follow th egcs development.
I downloaded to my Linux host egcs 1.1.1, egcs-19981220 and the diffs
to 19981226.
I installed all this into a brand new CVS tree.
I ran ./configure and make, got the error about the needed autoconf
2.12.1. I was not able to find such a beast (I cannot connect directly
to Cygnus through cvs). I read the FAQ and ran the touch commands.
Reran configure and make.

This went much farther, but failed in gcc/collects.o (transcript
below).
In demangle.h:26:
#define PARAMS(ARGS) PROTO(ARGS)
In gansidecl.h:33 (priorily included):
#define PROTO(ARGS) PARAMS(ARGS)

Did I do an error somewhere?
Do I really need autoconf 2.12.1 and where is it available from?

Thanks!
Best Regards!
Marc

-transcript---------------------
[...]
gcc  -DIN_GCC     -g -O2  -DHAVE_CONFIG_H    -I. -I. -I./config -I./../include  \
-DTARGET_MACHINE=\"i586-pc-linux-gnu\"  \
-c `echo ./collect2.c | sed 's,^\./,,'`
In file included from collect2.c:48:
demangle.h:25: warning: `PARAMS' redefined
../include/ansidecl.h:113: warning: this is the location of the previous definition
In file included from collect2.c:48:
demangle.h:77: parse error before `PARAMS'
demangle.h:80: parse error before `PARAMS'
demangle.h:83: parse error before `PARAMS'
demangle.h:88: parse error before `PARAMS'
demangle.h:91: parse error before `PARAMS'
demangle.h:94: parse error before `PARAMS'
demangle.h:97: parse error before `PARAMS'
demangle.h:100: parse error before `PARAMS'
demangle.h:103: parse error before `PARAMS'
demangle.h:106: parse error before `PARAMS'
collect2.c:58: parse error before `PROTO'
collect2.c:265: parse error before `PARAMS'
collect2.c:266: parse error before `PARAMS'
collect2.c:268: parse error before `PARAMS'
collect2.c:270: parse error before `PROTO'
collect2.c:271: parse error before `PROTO'
collect2.c:272: parse error before `PROTO'
collect2.c:273: parse error before `PROTO'
collect2.c:274: parse error before `PROTO'
collect2.c:275: parse error before `PROTO'
collect2.c:276: parse error before `PROTO'
collect2.c:277: parse error before `PROTO'
collect2.c:278: parse error before `PROTO'
collect2.c:279: parse error before `PROTO'
collect2.c:280: parse error before `PROTO'
collect2.c:281: parse error before `PROTO'
collect2.c:282: parse error before `PROTO'
collect2.c:283: parse error before `PROTO'
collect2.c:284: parse error before `PROTO'
collect2.c:291: parse error before `PROTO'
collect2.c:292: parse error before `PROTO'
collect2.c:293: parse error before `PROTO'
collect2.c: In function `dump_file':
collect2.c:627: warning: assignment makes pointer from integer without a cast
collect2.c: At top level:
collect2.c:903: warning: type mismatch with previous implicit declaration
collect2.c:898: warning: previous implicit declaration of `prefix_from_string'
collect2.c:903: warning: `prefix_from_string' was previously implicitly declared to return `int'
collect2.c:903: warning: `prefix_from_string' was declared implicitly `extern' and later `static'
collect2.c: In function `main':
collect2.c:1188: warning: assignment makes pointer from integer without a cast
collect2.c:1189: warning: assignment makes pointer from integer without a cast
collect2.c:1194: warning: assignment makes pointer from integer without a cast
collect2.c: At top level:
collect2.c:1731: warning: type mismatch with previous implicit declaration
collect2.c:1601: warning: previous implicit declaration of `fork_execute'
collect2.c:1731: warning: `fork_execute' was previously implicitly declared to return `int'
collect2.c:1731: warning: `fork_execute' was declared implicitly `extern' and later `static'
collect2.c:1742: warning: type mismatch with previous implicit declaration
collect2.c:1550: warning: previous implicit declaration of `maybe_unlink'
collect2.c:1742: warning: `maybe_unlink' was previously implicitly declared to return `int'
collect2.c:1742: warning: `maybe_unlink' was declared implicitly `extern' and later `static'
collect2.c:1810: warning: type mismatch with previous implicit declaration
collect2.c:1547: warning: previous implicit declaration of `sort_ids'
collect2.c:1810: warning: `sort_ids' was previously implicitly declared to return `int'
collect2.c:1810: warning: `sort_ids' was declared implicitly `extern' and later `static'
collect2.c:2129: warning: type mismatch with previous implicit declaration
collect2.c:1555: warning: previous implicit declaration of `write_c_file'
collect2.c:2129: warning: `write_c_file' was previously implicitly declared to return `int'
collect2.c:2129: warning: `write_c_file' was declared implicitly `extern' and later `static'
collect2.c:2176: warning: type mismatch with previous implicit declaration
collect2.c:1500: warning: previous implicit declaration of `scan_prog_file'
collect2.c:2176: warning: `scan_prog_file' was previously implicitly declared to return `int'
collect2.c:2176: warning: `scan_prog_file' was declared implicitly `extern' and later `static'
make[1]: *** [collect2.o] Error 1
make[1]: Leaving directory `/home/marc/egcs/gcc'
make: *** [all-gcc] Error 2


-- 
Marc Girod                Hiomo 5/1          Voice:  +358-9-511 23746
Nokia Telecommunications  P.O. Box 320       Mobile: +358-40-569 7954
NWS/NMS/NMS for Data      00045 NOKIA Group  Fax:    +358-9-511 23580
                          Finland            marc.girod@ntc.nokia.com

Re: Build failure (first installation)

[Jeffrey A Law]

  In message < 199812271554.RAA18920@sinkku.ntc.nokia.com >you write:
  > This went much farther, but failed in gcc/collects.o (transcript
  > below).
  > In demangle.h:26:
  > #define PARAMS(ARGS) PROTO(ARGS)
  > In gansidecl.h:33 (priorily included):
  > #define PROTO(ARGS) PARAMS(ARGS)
Make sure there is no demangle.h file in the gcc directory.  The gcc/demangle.h
file was deleted a week or two ago.


  > Do I really need autoconf 2.12.1 and where is it available from?
Yes.  http://sourceware.cygnus.com 

jeff

Re: Build failure (first installation)

[Marc Girod]

>>>>> "JL" == Jeffrey A Law <law@upchuck.cygnus.com> writes:

JL> Make sure there is no demangle.h file in the gcc directory. The
JL> gcc/demangle.h file was deleted a week or two ago.

Thanks. I am still not familiar with cvs...

>> Do I really need autoconf 2.12.1 and where is it available from?
JL> Yes.  http://sourceware.cygnus.com 

I am sitting behind a firewall --or is it that I have a strange IP
address on my linux box, probably illegal out of our corporate
network-- and I cannot use cvs remote (I connect, but it times out).

Now, I am mailing from my HP host, the IP address of which is fine,
but which has no cvs installed...

Wouldn't it make sense that autoconf too was available in tar format,
as snapshots are?

By the way, now again, I could build the 19990103 snapshot with 2.12,
just using the touch instructions from the FAQ.

Best Regards!
Marc

-- 
Marc Girod                Hiomo 5/1          Voice:  +358-9-511 23746
Nokia Telecommunications  P.O. Box 320       Mobile: +358-40-569 7954
NWS/NMS/NMS for Data      00045 NOKIA Group  Fax:    +358-9-511 23580
                          Finland            marc.girod@ntc.nokia.com

Re: Build failure (first installation)

[Joe Buck]

> I am sitting behind a firewall --or is it that I have a strange IP
> address on my linux box, probably illegal out of our corporate
> network-- and I cannot use cvs remote (I connect, but it times out).

Yes, this is generally a problem with remote CVS: most people can't
get to it at work, as the leading firewalls tend to block all ports
except those corresponding to well-known services.  I can only use remote
CVS at home.

> Wouldn't it make sense that autoconf too was available in tar format,
> as snapshots are?

Yes.  It would make even more sense to do a new autoconf release.

Re: Build failure (first installation)

[Alfred Perlstein]

On Mon, 4 Jan 1999, Joe Buck wrote:

> 
> > I am sitting behind a firewall --or is it that I have a strange IP
> > address on my linux box, probably illegal out of our corporate
> > network-- and I cannot use cvs remote (I connect, but it times out).
> 
> Yes, this is generally a problem with remote CVS: most people can't
> get to it at work, as the leading firewalls tend to block all ports
> except those corresponding to well-known services.  I can only use remote
> CVS at home.
> 
> > Wouldn't it make sense that autoconf too was available in tar format,
> > as snapshots are?
> 
> Yes.  It would make even more sense to do a new autoconf release.

When i cvs the FreeBSD tree i set the enviorment variable:
CVS_RSH=ssh

cvs will try to rsh using ssh, if both sides support ssh this really
helps.  a lot of places block rsh services as a matter of policy.

-Alfred

Re: Build failure (first installation)

[Jeffrey A Law]

  In message < 199901042039.MAA05714@atrus.synopsys.com >you write:
  > > Wouldn't it make sense that autoconf too was available in tar format,
  > > as snapshots are?
  > 
  > Yes.  It would make even more sense to do a new autoconf release.
I believe they're in the process of getting a release put together.  There's
a branch in the autoconf CVS repo for the 2.13 release.  Hopefully it won't
be too much longer.

jeff

Re: Build failure (first installation)

[Marc Girod]

>>>>> "N8TM" == N8TM@aol.com writes:

N8TM> << Do I really need autoconf 2.12.1 and where is it available from?
>>
N8TM> That doesn't appear to be your problem, ...

Indeed. It seems that I had messed up with cvs, and checked out files
from different versions: there is no gcc/demangle.h any more in the
latest patches.

N8TM> ... but it is preferable.
N8TM> Either install the one from the egcs or sourceware mirror sites
N8TM> (works for me on linux) or modify autoconf-2.12 to report itself
N8TM> as 2.12.1 and to use "int main()" consistently when testing
N8TM> whether gcc works.

Could one post the diffs (or better place them in /pub/autoconf on the
ftp site, which looks empty from my place).

Anyway, now my build passed with plain autoconf-2.12, so is it really
necessary? I'll start checking the results tomorrow...

Best Regards!
Marc

-- 
Marc Girod                Hiomo 5/1          Voice:  +358-9-511 23746
Nokia Telecommunications  P.O. Box 320       Mobile: +358-40-569 7954
NWS/NMS/NMS for Data      00045 NOKIA Group  Fax:    +358-9-511 23580
                          Finland            marc.girod@ntc.nokia.com

Re: Build failure (first installation)

[N8TM]

In a message dated 12/27/98 7:57:47 AM Pacific Standard Time,
girod@stybba.ntc.nokia.com writes:

<< Do I really need autoconf 2.12.1 and where is it available from?
  >>
That doesn't appear to be your problem, but it is preferable.  Either install
the one from the egcs or sourceware mirror sites (works for me on linux) or
modify autoconf-2.12 to report itself as 2.12.1 and to use "int main()"
consistently when testing whether gcc works.