From: Steinar Bang <sb@metis.no>
To: egcs@cygnus.com
Subject: Re: problem building linux specific 1.1.1
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <whww2btvwb.fsf@viffer.oslo.metis.no> (raw)
Message-ID: <19990131235800.o7wm49va42qXI_Uam0024yXa1KHIaXQeIiWpW-AemQ8@z> (raw)
In-Reply-To: <vyzr9sj7gdk.fsf@issan.cs.uni-dortmund.de>
>>>>> 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))
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-21 0:36 multiple definitions of 'xxx keyed to...' in egcs-1.1.1 Steinar Bang
1999-01-21 2:44 ` Steinar Bang
1999-01-21 23:48 ` Steinar Bang
1999-01-22 0:37 ` H.J. Lu
1999-01-22 0:42 ` Steinar Bang
1999-01-22 0:48 ` H.J. Lu
1999-01-22 1:21 ` Steinar Bang
1999-01-22 2:01 ` problem building linux specific 1.1.1 Steinar Bang
1999-01-22 8:22 ` H.J. Lu
1999-01-25 2:20 ` Steinar Bang
1999-01-25 2:27 ` Steinar Bang
1999-01-25 2:49 ` Steinar Bang
1999-01-25 3:15 ` Andreas Schwab
1999-01-25 3:49 ` Steinar Bang [this message]
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Andreas Schwab
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` H.J. Lu
1999-01-31 23:58 ` Steinar Bang
1999-01-22 8:27 ` multiple definitions of 'xxx keyed to...' in egcs-1.1.1 H.J. Lu
1999-01-25 1:44 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` H.J. Lu
1999-01-26 10:11 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` H.J. Lu
1999-01-31 23:58 ` Steinar Bang
1999-01-22 7:05 ` Andris Pavenis
1999-01-27 9:04 ` Joe Buck
1999-01-28 0:55 ` Andris Pavenis
1999-01-28 1:16 ` Steinar Bang
1999-01-29 3:54 ` Steinar Bang
1999-01-29 17:30 ` H.J. Lu
1999-01-29 17:30 ` H.J. Lu
1999-01-29 17:58 ` Joe Buck
1999-01-29 18:30 ` Jeffrey A Law
1999-01-30 2:50 ` Andris Pavenis
1999-01-30 17:37 ` Joe Buck
1999-01-31 23:58 ` Joe Buck
1999-01-30 1:50 ` Andris Pavenis
1999-02-01 2:19 ` Steinar Bang
1999-02-28 22:53 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Andris Pavenis
1999-01-29 17:30 ` H.J. Lu
1999-01-30 15:50 ` craig
1999-01-31 12:21 ` H.J. Lu
1999-02-01 4:48 ` craig
1999-02-28 22:53 ` craig
1999-01-31 23:58 ` craig
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Andris Pavenis
1999-01-31 23:58 ` H.J. Lu
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-31 23:58 ` Steinar Bang
1999-01-25 5:41 problem building linux specific 1.1.1 N8TM
1999-01-31 23:58 ` N8TM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=whww2btvwb.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).