Re: new glibc, egcs, etc.
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 23 Mar 1999, Hartmut Koptein wrote:
>I think it sym-links ../linux -> /usr/src/linux, this may also a link ...
>This with -I../../port/linux/include -I../../include and you are in trouble.
>... and an #include <net/route.h> is so easy :-)
check this. It's the most absurd and stupid way I've seen to create a source
pwd = /public/ftp/pub/debian/dists/potato/source/net/bind-8.1.2/
target/port/linux/include/net/route.h -> SRC/route.h
target/port/linux/include/net/SRC -> ../SRC/net/
target/port/linux/include/SRC -> ../SRC/include/
target/port/linux/SRC -> ../SRC/linux/
target/port/SRC -> ../SRC/port/
target/SRC -> /public/ftp/pub/debian/dists/potato/source/net/bind-8.1.2/
So, I see three ways to overcome this problem
a) hack this up so that it includes the necessary file without the links.
This is easy, but it will have to be done probably every time a new bind
release is made.
b) Fix egcs compiler to be able to follow a greater number of symlinks (I don't
even know if that can be done in the first place). If it can be done, it will
probably be just a definition in a config file but it will require a new
recompiling (slow and tedious process), not to mention I would have to download
a few MBs again.
c) Tell the guys the produce the upstream release to change their way of
configuring/compiling bind, maybe even use a configure script (ah, that would
be the day). That seems to be the hardest way.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----