Re: problem building linux specific 1.1.1

Re: problem building linux specific 1.1.1

[N8TM]

In a message dated 1/25/99 3:53:51 AM Pacific Standard Time, sb@metis.no
writes:

<< Hm... I have patch 2.1 it seems.  At least that's what "patch -v"
 reports.  >>
patch-2.1 was working for me when I installed egcs-1.1.1 on linux-gnulibc1 and
Irix6.4, but it failed on recent snapshots, so I've switched to patch-2.5.

Re: problem building linux specific 1.1.1

[N8TM]

In a message dated 1/25/99 3:53:51 AM Pacific Standard Time, sb@metis.no
writes:

<< Hm... I have patch 2.1 it seems.  At least that's what "patch -v"
 reports.  >>
patch-2.1 was working for me when I installed egcs-1.1.1 on linux-gnulibc1 and
Irix6.4, but it failed on recent snapshots, so I've switched to patch-2.5.

problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Steinar Bang <sb@metis.no>:

>>>>> hjl@lucon.org (H.J. Lu):
>> Get it and read the release note as well as ChangeLogs.

> I got the patches at 
> 	ftp://ftp.yggdrasil.com/private/hjl/egcs/1.1.1/egcs-1.1.1-19990115-linux.diff.gz
> and applied them to a freshly unpacked egcs-1.1.1, but they didn't
> change the ChangeLog as far as I could tell.

I've problems configuring the patched egcs-1.1.1:
	/home/sb/src/install/egcs-1.1.1 > ./configure --prefix=/home/sb/apps
	Configuring for a i686-pc-linux-gnulibc1 host.
	./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Steinar Bang <sb@metis.no>:

> If I moved up one level to apply the patch, I got asked about some
> presumably reversed patches and if they should be applied (to which I
> said no to everything) and got a log slightly larger than the first
> time I did this.

> Hm... I could try some -p magic, but the diffs in this patch seems to
> have different directory levels... I'll live with the two applications 
> of the patch for now, I think... at least it configured this time.

> I'm starting to get pretty tired of unpacking and patching by now.

It configured, but didn't build.  "make bootstrap" ended up here:
...
make[3]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo/makeinfo'
make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
Bootstrapping the compiler
make[1]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
make CC="gcc" libdir=/home/sb/apps/lib LANGUAGES="c "
make[2]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
cd . && autoheader
/bin/sh: autoheader: command not found
make[2]: *** [cstamp-h.in] Error 127
make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
make: *** [bootstrap] Error 2

Does anybody have an idea of what "autoheader" is?

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>:

>>> However I'm still getting the problem of the missing "autoheader"
>>> program (on S.u.S.E. 5.3).  Hm... do I need "autoconf" and "GNU m4"
>>> installed on the system...?  Some Deja News messages seems to
>>> indicate this.

> You only need them if you upgrade via a patch, otherwise the
> timestamps will be correct.  Btw, if you use the latest version of
> patch (2.5) you can use `patch -p1 -T', which causes patch to set
> the timestamp from the diff headers.

Hm... I have patch 2.1 it seems.  At least that's what "patch -v"
reports. 

In any case, I installed the autoconf package from the S.u.S.E. 5.3
distribution, available from eg.
	http://rufus.w3.org/linux/RPM/suse/5.3/d1/autoconf-2.12-13.i386.html
or on the CD.

Now "make boostrap" seems to run OK.

Thanx!

(then it only remains to see if it fixes my shared lib linking problem 
without the binutils alpha which I din't know where to find (or even
*with* it, for that matter)) 

Re: problem building linux specific 1.1.1

[H.J. Lu]

> 
> >>>>> Steinar Bang <sb@metis.no>:
> 
> >>>>> hjl@lucon.org (H.J. Lu):
> >> Get it and read the release note as well as ChangeLogs.
> 
> > I got the patches at 
> > 	ftp://ftp.yggdrasil.com/private/hjl/egcs/1.1.1/egcs-1.1.1-19990115-linux.diff.gz
> > and applied them to a freshly unpacked egcs-1.1.1, but they didn't
> > change the ChangeLog as far as I could tell.

Please check ChangeLog.linux.

> 
> I've problems configuring the patched egcs-1.1.1:
> 	/home/sb/src/install/egcs-1.1.1 > ./configure --prefix=/home/sb/apps
> 	Configuring for a i686-pc-linux-gnulibc1 host.
> 	./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory
> 

You didn't apply the patch right. config.if should be there. I see it
in my patch. Please tell me exactly how you unpack egcs 1.1.1 and apply
my patch.

-- 
H.J. Lu (hjl@gnu.org)

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Steinar Bang <sb@metis.no>:

>>>>> Steinar Bang <sb@metis.no>:
>> If I moved up one level to apply the patch, I got asked about some
>> presumably reversed patches and if they should be applied (to which I
>> said no to everything) and got a log slightly larger than the first
>> time I did this.

>> Hm... I could try some -p magic, but the diffs in this patch seems to
>> have different directory levels... I'll live with the two applications 
>> of the patch for now, I think... at least it configured this time.

Thanx to Martin Kahlert <martin.kahlert@mchp.siemens.de> who told me
to use the "-p1 -E" arguments to patch.  That took care of the
directory problems.

However I'm still getting the problem of the missing "autoheader"
program (on S.u.S.E. 5.3).  Hm... do I need "autoconf" and "GNU m4"
installed on the system...?  Some Deja News messages seems to
indicate this.

Hm... should ./configure have searched for autoheader and compensated
for a missing autoheader?

> It configured, but didn't build.  "make bootstrap" ended up here:
> ...
> make[3]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo/makeinfo'
> make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
> make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
> Bootstrapping the compiler
> make[1]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
> make CC="gcc" libdir=/home/sb/apps/lib LANGUAGES="c "
> make[2]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
> cd . && autoheader
> /bin/sh: autoheader: command not found
> make[2]: *** [cstamp-h.in] Error 127
> make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
> make[1]: *** [bootstrap] Error 2
> make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
> make: *** [bootstrap] Error 2

> Does anybody have an idea of what "autoheader" is?

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> hjl@lucon.org (H.J. Lu):

>> > I got the patches at 
>> > 	ftp://ftp.yggdrasil.com/private/hjl/egcs/1.1.1/egcs-1.1.1-19990115-linux.diff.gz
>> > and applied them to a freshly unpacked egcs-1.1.1, but they didn't
>> > change the ChangeLog as far as I could tell.

> Please check ChangeLog.linux.

There isn't one.

>> 
>> I've problems configuring the patched egcs-1.1.1:
>> /home/sb/src/install/egcs-1.1.1 > ./configure --prefix=/home/sb/apps
>> Configuring for a i686-pc-linux-gnulibc1 host.
>> ./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory
>> 

> You didn't apply the patch right. config.if should be there. I see it
> in my patch. Please tell me exactly how you unpack egcs 1.1.1 and apply
> my patch.

/home/sb/src/install% zcat ~/src/distrib/egcs-1.1.1.tar.gz | tar xf -
/home/sb/src/install% zcat ~/src/distrib/egcs-1.1.1-19990115-linux.diff.gz | patch 
[lots of hunk# succeeded snipped]

/home/sb/src/install% cd egcs-1.1.1/
/home/sb/src/install/egcs-1.1.1% ./configure --prefix=/home/sb/apps
Configuring for a i686-pc-linux-gnulibc1 host.
./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory

Since I'm missing some files, there's probably a command line argument 
to patch that will tell it to create files, lesse... (M-x man patch RET)
no there wasn't... arrrrgh!  Lots of files are created on the
directory above the egcs-1.1.1 directory... @$&@!!  When I saw
"succeed" in the patch messages flickering over the screen I assumed
that the directory information in the patch was correct.

Hmph... moving down into the egcs-1.1.1 directory to apply the patch
applied the missing patches (the ones containing the missing files?),
but seems to croak on something else:
Patching file Makefile.in using Plan A...
Hunk #1 failed at 344.
Hunk #2 failed at 801.
Hunk #3 failed at 823.
Hunk #4 failed at 2189.
Hunk #5 failed at 2338.
Hunk #6 failed at 2819.
Hunk #7 failed at 2844.
Hunk #8 failed at 2869.
Hunk #9 failed at 2894.
Hunk #10 succeeded at 2978 with fuzz 2 (offset -1 lines).
patch: **** misordered hunks! output would be garbled

If I moved up one level to apply the patch, I got asked about some
presumably reversed patches and if they should be applied (to which I
said no to everything) and got a log slightly larger than the first
time I did this.

Hm... I could try some -p magic, but the diffs in this patch seems to
have different directory levels... I'll live with the two applications 
of the patch for now, I think... at least it configured this time.

I'm starting to get pretty tired of unpacking and patching by now.

Re: problem building linux specific 1.1.1

[Andreas Schwab]

Steinar Bang <sb@metis.no> writes:

|> >>>>> Steinar Bang <sb@metis.no>:
|> 
|> >>>>> Steinar Bang <sb@metis.no>:
|> >> If I moved up one level to apply the patch, I got asked about some
|> >> presumably reversed patches and if they should be applied (to which I
|> >> said no to everything) and got a log slightly larger than the first
|> >> time I did this.
|> 
|> >> Hm... I could try some -p magic, but the diffs in this patch seems to
|> >> have different directory levels... I'll live with the two applications 
|> >> of the patch for now, I think... at least it configured this time.
|> 
|> Thanx to Martin Kahlert <martin.kahlert@mchp.siemens.de> who told me
|> to use the "-p1 -E" arguments to patch.  That took care of the
|> directory problems.
|> 
|> However I'm still getting the problem of the missing "autoheader"
|> program (on S.u.S.E. 5.3).  Hm... do I need "autoconf" and "GNU m4"
|> installed on the system...?  Some Deja News messages seems to
|> indicate this.

You only need them if you upgrade via a patch, otherwise the timestamps
will be correct.  Btw, if you use the latest version of patch (2.5) you
can use `patch -p1 -T', which causes patch to set the timestamp from the
diff headers.

-- 
Andreas Schwab                                      "And now for something
schwab@issan.cs.uni-dortmund.de                      completely different"
schwab@gnu.org

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>:

>>> However I'm still getting the problem of the missing "autoheader"
>>> program (on S.u.S.E. 5.3).  Hm... do I need "autoconf" and "GNU m4"
>>> installed on the system...?  Some Deja News messages seems to
>>> indicate this.

> You only need them if you upgrade via a patch, otherwise the
> timestamps will be correct.  Btw, if you use the latest version of
> patch (2.5) you can use `patch -p1 -T', which causes patch to set
> the timestamp from the diff headers.

Hm... I have patch 2.1 it seems.  At least that's what "patch -v"
reports. 

In any case, I installed the autoconf package from the S.u.S.E. 5.3
distribution, available from eg.
	http://rufus.w3.org/linux/RPM/suse/5.3/d1/autoconf-2.12-13.i386.html
or on the CD.

Now "make boostrap" seems to run OK.

Thanx!

(then it only remains to see if it fixes my shared lib linking problem 
without the binutils alpha which I din't know where to find (or even
*with* it, for that matter)) 

Re: problem building linux specific 1.1.1

[Andreas Schwab]

Steinar Bang <sb@metis.no> writes:

|> >>>>> Steinar Bang <sb@metis.no>:
|> 
|> >>>>> Steinar Bang <sb@metis.no>:
|> >> If I moved up one level to apply the patch, I got asked about some
|> >> presumably reversed patches and if they should be applied (to which I
|> >> said no to everything) and got a log slightly larger than the first
|> >> time I did this.
|> 
|> >> Hm... I could try some -p magic, but the diffs in this patch seems to
|> >> have different directory levels... I'll live with the two applications 
|> >> of the patch for now, I think... at least it configured this time.
|> 
|> Thanx to Martin Kahlert <martin.kahlert@mchp.siemens.de> who told me
|> to use the "-p1 -E" arguments to patch.  That took care of the
|> directory problems.
|> 
|> However I'm still getting the problem of the missing "autoheader"
|> program (on S.u.S.E. 5.3).  Hm... do I need "autoconf" and "GNU m4"
|> installed on the system...?  Some Deja News messages seems to
|> indicate this.

You only need them if you upgrade via a patch, otherwise the timestamps
will be correct.  Btw, if you use the latest version of patch (2.5) you
can use `patch -p1 -T', which causes patch to set the timestamp from the
diff headers.

-- 
Andreas Schwab                                      "And now for something
schwab@issan.cs.uni-dortmund.de                      completely different"
schwab@gnu.org

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Steinar Bang <sb@metis.no>:

>>>>> Steinar Bang <sb@metis.no>:
>> If I moved up one level to apply the patch, I got asked about some
>> presumably reversed patches and if they should be applied (to which I
>> said no to everything) and got a log slightly larger than the first
>> time I did this.

>> Hm... I could try some -p magic, but the diffs in this patch seems to
>> have different directory levels... I'll live with the two applications 
>> of the patch for now, I think... at least it configured this time.

Thanx to Martin Kahlert <martin.kahlert@mchp.siemens.de> who told me
to use the "-p1 -E" arguments to patch.  That took care of the
directory problems.

However I'm still getting the problem of the missing "autoheader"
program (on S.u.S.E. 5.3).  Hm... do I need "autoconf" and "GNU m4"
installed on the system...?  Some Deja News messages seems to
indicate this.

Hm... should ./configure have searched for autoheader and compensated
for a missing autoheader?

> It configured, but didn't build.  "make bootstrap" ended up here:
> ...
> make[3]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo/makeinfo'
> make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
> make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
> Bootstrapping the compiler
> make[1]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
> make CC="gcc" libdir=/home/sb/apps/lib LANGUAGES="c "
> make[2]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
> cd . && autoheader
> /bin/sh: autoheader: command not found
> make[2]: *** [cstamp-h.in] Error 127
> make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
> make[1]: *** [bootstrap] Error 2
> make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
> make: *** [bootstrap] Error 2

> Does anybody have an idea of what "autoheader" is?

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Steinar Bang <sb@metis.no>:

> If I moved up one level to apply the patch, I got asked about some
> presumably reversed patches and if they should be applied (to which I
> said no to everything) and got a log slightly larger than the first
> time I did this.

> Hm... I could try some -p magic, but the diffs in this patch seems to
> have different directory levels... I'll live with the two applications 
> of the patch for now, I think... at least it configured this time.

> I'm starting to get pretty tired of unpacking and patching by now.

It configured, but didn't build.  "make bootstrap" ended up here:
...
make[3]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo/makeinfo'
make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/texinfo'
Bootstrapping the compiler
make[1]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
make CC="gcc" libdir=/home/sb/apps/lib LANGUAGES="c "
make[2]: Entering directory `/home/sb/src/install/egcs-1.1.1/gcc'
cd . && autoheader
/bin/sh: autoheader: command not found
make[2]: *** [cstamp-h.in] Error 127
make[2]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/home/sb/src/install/egcs-1.1.1/gcc'
make: *** [bootstrap] Error 2

Does anybody have an idea of what "autoheader" is?

Re: problem building linux specific 1.1.1

[Steinar Bang]

>>>>> hjl@lucon.org (H.J. Lu):

>> > I got the patches at 
>> > 	ftp://ftp.yggdrasil.com/private/hjl/egcs/1.1.1/egcs-1.1.1-19990115-linux.diff.gz
>> > and applied them to a freshly unpacked egcs-1.1.1, but they didn't
>> > change the ChangeLog as far as I could tell.

> Please check ChangeLog.linux.

There isn't one.

>> 
>> I've problems configuring the patched egcs-1.1.1:
>> /home/sb/src/install/egcs-1.1.1 > ./configure --prefix=/home/sb/apps
>> Configuring for a i686-pc-linux-gnulibc1 host.
>> ./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory
>> 

> You didn't apply the patch right. config.if should be there. I see it
> in my patch. Please tell me exactly how you unpack egcs 1.1.1 and apply
> my patch.

/home/sb/src/install% zcat ~/src/distrib/egcs-1.1.1.tar.gz | tar xf -
/home/sb/src/install% zcat ~/src/distrib/egcs-1.1.1-19990115-linux.diff.gz | patch 
[lots of hunk# succeeded snipped]

/home/sb/src/install% cd egcs-1.1.1/
/home/sb/src/install/egcs-1.1.1% ./configure --prefix=/home/sb/apps
Configuring for a i686-pc-linux-gnulibc1 host.
./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory

Since I'm missing some files, there's probably a command line argument 
to patch that will tell it to create files, lesse... (M-x man patch RET)
no there wasn't... arrrrgh!  Lots of files are created on the
directory above the egcs-1.1.1 directory... @$&@!!  When I saw
"succeed" in the patch messages flickering over the screen I assumed
that the directory information in the patch was correct.

Hmph... moving down into the egcs-1.1.1 directory to apply the patch
applied the missing patches (the ones containing the missing files?),
but seems to croak on something else:
Patching file Makefile.in using Plan A...
Hunk #1 failed at 344.
Hunk #2 failed at 801.
Hunk #3 failed at 823.
Hunk #4 failed at 2189.
Hunk #5 failed at 2338.
Hunk #6 failed at 2819.
Hunk #7 failed at 2844.
Hunk #8 failed at 2869.
Hunk #9 failed at 2894.
Hunk #10 succeeded at 2978 with fuzz 2 (offset -1 lines).
patch: **** misordered hunks! output would be garbled

If I moved up one level to apply the patch, I got asked about some
presumably reversed patches and if they should be applied (to which I
said no to everything) and got a log slightly larger than the first
time I did this.

Hm... I could try some -p magic, but the diffs in this patch seems to
have different directory levels... I'll live with the two applications 
of the patch for now, I think... at least it configured this time.

I'm starting to get pretty tired of unpacking and patching by now.

Re: problem building linux specific 1.1.1

[H.J. Lu]

> 
> >>>>> Steinar Bang <sb@metis.no>:
> 
> >>>>> hjl@lucon.org (H.J. Lu):
> >> Get it and read the release note as well as ChangeLogs.
> 
> > I got the patches at 
> > 	ftp://ftp.yggdrasil.com/private/hjl/egcs/1.1.1/egcs-1.1.1-19990115-linux.diff.gz
> > and applied them to a freshly unpacked egcs-1.1.1, but they didn't
> > change the ChangeLog as far as I could tell.

Please check ChangeLog.linux.

> 
> I've problems configuring the patched egcs-1.1.1:
> 	/home/sb/src/install/egcs-1.1.1 > ./configure --prefix=/home/sb/apps
> 	Configuring for a i686-pc-linux-gnulibc1 host.
> 	./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory
> 

You didn't apply the patch right. config.if should be there. I see it
in my patch. Please tell me exactly how you unpack egcs 1.1.1 and apply
my patch.

-- 
H.J. Lu (hjl@gnu.org)

problem building linux specific 1.1.1

[Steinar Bang]

>>>>> Steinar Bang <sb@metis.no>:

>>>>> hjl@lucon.org (H.J. Lu):
>> Get it and read the release note as well as ChangeLogs.

> I got the patches at 
> 	ftp://ftp.yggdrasil.com/private/hjl/egcs/1.1.1/egcs-1.1.1-19990115-linux.diff.gz
> and applied them to a freshly unpacked egcs-1.1.1, but they didn't
> change the ChangeLog as far as I could tell.

I've problems configuring the patched egcs-1.1.1:
	/home/sb/src/install/egcs-1.1.1 > ./configure --prefix=/home/sb/apps
	Configuring for a i686-pc-linux-gnulibc1 host.
	./configure: /home/sb/src/install/egcs-1.1.1/config.if: No such file or directory