Re: A new libg++ for egcs

[Torbjorn Lindgren <tl at funcom dot no>]

On Fri, 24 Oct 1997, H.J. Lu wrote:
> I have made a libg++ for egcs just in case someone wants it. It
> is very close to the one in libg++ 2.8.0b6.
[...]
> This libg++ and librx are tested with egcs 971023 on linux/x86/libc 5,
> linux/x86/glibc 2.1 and linux/alpha/glibc 2.0.5c. Just put libg++ and
> librx under the egcs source directory, i.e.,

It doesn't work with at least linux/x86/glibc 2.05c (RedHat 4.9.1) on my
machine, which AFAIK is the latest released version.


The relevant part from the build log is:

Configuring in libraries/libg++
[ ... Informations about links being created ... ]
checking for ranlib
Appending ./config/linux.mt to target-mkfrag
Created "Makefile" in /usr/src/egcs-971023/libraries/libg++ using "target-mkfrag"
*** /usr/src/egcs-971023/configure: cannot create a link "rx.h",
*** since the file ".//usr/include/regex.h" does not exist.
Configure in /usr/src/egcs-971023/libraries/libg++/src failed, exiting.
make[1]: *** [configure-target-libg++] Error 1


I looked at libg++/src/configure.in and with some testing I verified that
it should have set "files" to /usr/include/regex.h and "links" to rx.h

Later, "configure" (from egcs-971023) tries to link with 
${srcdir}/${file}, which of course won't work when ${file) is an absolute
path...


There are at least two relevant questions here:

1. Is libg++ supposed to find and try to use /usr/include/regex.h on
Linux? It looks like it's hardcoded to use "../../librx/rx.h" on all other
platforms.

2. Is the main configure script supposed to support absolute paths?


I made some minor modifications to configure so that it also supports
absolute paths, but I'm not sure if that's the right way to do it.

-- 
Torbjörn Lindgren
E-mail: tl@funcom.com
If Santa ever DID deliver presents on Christmas Eve, he's dead now.