From: hjl@lucon.org (H.J. Lu)
To: sb@metis.no (Steinar Bang)
Cc: 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: <m103jLs-00038dC@ocean.lucon.org> (raw)
Message-ID: <19990131235800.ubPZ2AeUUxMU5MsoTgsdVSvOjOMeGDqmGHhPH7bkTUI@z> (raw)
In-Reply-To: <wh90ev62yf.fsf_-_@viffer.oslo.metis.no>
>
> >>>>> 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)
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 [this message]
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
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=m103jLs-00038dC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=sb@metis.no \
/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).