Well, I "knew" it would be a simple answer. I guess the use of "automated everything" has passed this newbie by good ol' ways of getting the stuff you need. Thanks, sorry the email was long in relation to the question. If you didn't respond, it's probably because you're still reading my posting, so no problem.
Thanks again,
Gustaf B.
P.S. Fabian, here is what we're looking for to get those headers passed. Hope this works for you.
At 01:27 PM 6/13/2001 +0200, you wrote:
Hi Gustaf,
Gustaf Barkstrom <gusb8@xxxxxxxx> writes:
> (therein lies probably the crux of my problem, "I don't know how to > pass headers to the configure script")
You need to tell cpp and ld where to find the headers and libs by defining environment variables:
export CPPFLAGS='-I /path/to/blah/include' export LDFLAGS='-L /path/to/blah/lib'
before running ./configure
Note that this is only neccessary for legacy libs which do not provide M4 macros or *-config scripts.
ciao, --mitch
