From: Jeffrey A Law <law@cygnus.com>
To: mulbrich@statistik.tu-muenchen.de (Michael Ulbrich)
Cc: egcs@cygnus.com
Subject: Re: egcs-1.0 successfully built on sparc-sun-solaris2.6
Date: Mon, 15 Dec 1997 10:26:00 -0000 [thread overview]
Message-ID: <903.882210535@hurl.cygnus.com> (raw)
In-Reply-To: <199712121449.PAA23058@sparc1.iams>
In message < 199712121449.PAA23058@sparc1.iams >you write:
> Hi,
>
> I have built a native egcs-1.0 for the host sparc-sun-solaris2.6.
Good. Thanks for letting us know.
> Three patches were necessary:
>
> 1. I had to use gmake, since /usr/ccs/bin/make did not work.
Right. Of course we recommend using gmake in the installation
instructions.
> 2. /usr/bin/which does not work on my system. I replaced
> the corresponding line 795 in srcdir/configure.in
Why exactly did it not work? It seemed to work just fine for other folks.
> 3. I had to use bash instead of /bin/sh in srcdir/configure.
> See the diff-file.
Again, why?
Thanks!
jeff
prev parent reply other threads:[~1997-12-15 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-12 10:18 Michael Ulbrich
1997-12-15 10:26 ` Jeffrey A Law [this message]
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=903.882210535@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mulbrich@statistik.tu-muenchen.de \
/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).