Matthew Lye wrote:
> I'm just getting things running under Leopard.

I'm envy you albeit I'd prefer a Leo II.

> The first thing I've noticed is a odd glitch in the Configure script  
> when it tests for usable versions of Glib and Gtk.  The conditional  
> expressions in the script at lines 7026 & 7101, for instance:
> 
> > if [ "$gtkversion" = 1 ] && [ gtk-config --cflags >/dev/null 2>&1 ];  
> > then
> 
> Always fail, as the second term always evaluates as false.  (The  
> result, "sh: [: gtk-config: unary operator expected" is hidden).

Duh! What a shice. If you remove the '2>&1' the message becomes visible
and my shell complains about the 'unsupported' --cflags. I wonder whether
test (the other name of '[') shouldn't ignore long options but it's not
just your shell, so I've removed the bogus use of test.

> Changing the test to something like this:
> 
> > if [ "$gtkversion" = 1 ]; then
> > if gtk-config --cflags >/dev/null 2>&1 ; then
> 
> works just fine (with extra 'fi', of course).  There's probably a much  
> tidier way to do it.

Yes, just remove the brackets. These brackets are not precedence operators
but the shell utility "test" in disguise, so such misuse isn't obvious (to me)
on first sight.

> I also noticed a fair number of messages such as:
> 
> > Checking to see if your C compiler knows about "volatile"...
> > rm: try.dSYM: is a directory

> which go away if all the 'rm -f' expressions are changed to 'rm -Rf'.

That looks odd. Do you have an idea how the "dSYM" gets in there? You could
add the line below before an affected occurence of rm?

        echo "rm='$rm'"

> Finally, gettext, glib & gtk1-1.2.10 appear to rely heavily on  
> convenience environmental variables such as '$SED' and '$EGREP' being  
> set to the corresponding binary.  I never encountered this as a  
> problem in Tiger  (OS X 10.4).  Are these assumed to be defined on  
> one's system, or am I missing an element of the ltconfig and/or (gnu)  
> libtool rigamarole?

Those are certainly not standard environment variables and I've never seen
them before or set them. Are you talking about their configure scripts? I'd
think they couldn't find a variant of 'sed' or 'grep' that they can handle
on your system respectively in your path. So it's probably just some broken
check but you shouldn't have to set them manually.

Christian
-- 
1000 byte   = 1 kB = 1 kilobyte; 1024 byte   = 1 KiB = 1 kibibyte
1000^2 byte = 1 MB = 1 megabyte; 1024^2 byte = 1 MiB = 1 mebibyte
1000^3 byte = 1 GB = 1 gigabyte; 1024^3 byte = 1 GiB = 1 gibibyte

-------------------------------------------------------------------------
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
gtk-gnutella-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel

Reply via email to