From: hjl@lucon.org (H.J. Lu)
To: g.thomas@opengroup.org (Gary Thomas)
Cc: egcs@cygnus.com
Subject: Re: libg++-2.8.1-980306
Date: Tue, 10 Mar 1998 10:28:00 -0000 [thread overview]
Message-ID: <m0yCQbn-00058gC@ocean.lucon.org> (raw)
In-Reply-To: <XFMail.980310081747.g.thomas@opengroup.org>
>
> When I merged this in with EGCS, I get the following "configure" errors:
>
> Created "Makefile" in /usr/src/redhat/BUILD/egcs/libraries/nof/libg++ using
> "target-mkfrag"
> *** /usr/src/redhat/BUILD/egcs/configure: cannot create a link "rx.h",
> *** since the file ".//usr/include/regex.h" does not exist.
> Configure in /usr/src/redhat/BUILD/egcs/libraries/nof/libg++/src failed,
> exiting.
> make: *** [configure-target-libg++] Error 1
> Bad exit status
>
> Any ideas?
>
Please read README.libg++ in the tar ball.
Jeff, could you please install my patch to egcs configure? It fixes
a real bug so that people don't have to apply my patch to compile
libg++.
Thanks.
H.J.
parent reply other threads:[~1998-03-10 10:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <XFMail.980310081747.g.thomas@opengroup.org>]
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=m0yCQbn-00058gC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=g.thomas@opengroup.org \
/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).