Matthew Lye wrote:
> Okay, I tried build.sh again, and the previous problem was that
> Configure.sh couldn't find /usr/bin/make when being run from the
> build.sh script.
>
> > [21:32:48|~/prj/gtk-gnutella>./build.sh
> > Would you like to see the instructions? [n]
> > Locating common programs...
> > I don't know where 'make' is, and my life depends on it.
> > Go find a free implementation or fix your PATH setting!
> >
> > ERROR: Configure failed.
> This time, I actually took a look at the build.sh script. "$MAKE"
> does not have a default value on my system; one would be required to
> define it at the script's execution.
I think you tried at moment the script was broken. MAKE is set to
gmake or make by default.
> It looks like I'll definitely have trouble with the library suffix
> ('dylib' rather than 'so', although they're actually technically two
> different things.)
> I tried adding the following:
> > --so=*) so="${1#--*=}";;
> just mimicking the other definitions. I don't know yet if it works.
> The next problem is currently stopping things.
You probably didn't add the code which actually passes it to Configure. It's
certainly possible to add such an option but I'd like to avoid it if not
necessary. I've added -U usenm to the Configure options now. Does it still need
to know the suffix?
> It appears that "--cflag=" is unable to take a list of flags from the
> command line? They're all passed to Configure as if they should be
> it's own flags, rather than used to define CFLAGS as an environmental
> variable. I'm having trouble figuring out why.
I think this is again due to brokenness when you tried. The option parsing
of Configure had been broken for the last 14 years. Not sure whether it's
100% correct now but it seems to work. So, for example, this should propagate
the compiler flags properly:
./build.sh --cflags='-W -Wall -O3'
If you don't pass this option and $CFLAGS is set, it will be automagically
passed in the same manner. You only need single- or double-quotes if you
pass multiple flags of course.
> I would like it if build.sh moved or renamed config.sh rather than
> deleting it. Currently, if it fails, one needs to enter all one's
> local peculiarities into Configure.sh by hand again.
Once build.sh works perfectly for you, it should be a non-issue, but this can
be added to the script:
mv config.sh config.sh.bak >/dev/null 2>&1 || : ignore
What flags are you usually passing to Configure? And what's the output of
uname -s
on your machine?
--
Christian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
gtk-gnutella-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
