I am familiar with -d. Been running it all day.
I have tried to find a way to influance the configure script without
patching but I gave up and patched it.
# port configure // fails
# cd work/libzdb-2.3/ && ./configure --prefix=/opt/local // works
As far as I know --prefix typically influences the install dir and not
the finding of libs or includes.
But I'm not a strong unix admin.
Just try the scripts I attached. Takes about a minute or two to add
them to a local repo.
I have the scripts dumbed down on purpose. Running ./configure with no
args (or with prefix=/opt/local if you prefer) from ${worksrcdir} or
what ever that var is named works.
Running "port configure" does not work.
//brad
On Feb 9, 2009, at 2:18 PM, Toby Peterson wrote:
On Mon, Feb 9, 2009 at 2:02 PM, Bradley Giesbrecht
<[email protected]> wrote:
The file I'm patching is named "configure" hence patch-configure.
My patches are in ./files.
The patch is being applied, and after I let macports apply the
patch if I cd
into the worksrcdir and do ./configure it works.
But not with macports.
"port configure" does not simply run ./configure... it sets some
environment variables, and uses --prefix (possibly other args too).
port -d configure should show you what it's doing.
- Toby
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
