Re: Problems with precompiled packages

[Richard Frith-Macdonald]

On 26 Jun 2010, at 06:33, German Arias wrote:

> Before refer my problems, some things:
> 
> 1) Relative paths in GNUstep.conf, always are taken in reference to 
> /etc/GNUstep/GNUstep.conf. Even if you configure --with-config-file=another 
> path. In fact gnustep-base ignore the specified file with this option.

This is certainly not true on my systems ... what version of gnustep are you 
using.  As far as I know there have been no releases where the configure script 
accepts '--with-config-file=' and the value it sets is not honored.
You should check whether the configured file exists and what paths are 
specified inside it.   If the file doesn't exist, you should check the output 
from 'configure'  (config.log) to see what default information you defined for 
when the config file doesn't exist.

Here's a section from my config.log when I configured base to be relocatable:

configure:2120: checking for GNUstep configuration file to use at runtime
configure:2160: result: ./
configure:2175: checking whether the GNUstep.conf file path can be set in the 
environment
configure:2190: result: yes
configure:2232: checking if we should import an existing configuration file now
configure:2245: result: yes
configure:2252: checking for default GNUstep configuration file to use
configure:2280: result: relocatable.conf
configure:2308: result: trying to import "relocatable.conf"
configure:2310: If this fails, please run configure again with the 
--disable-importing-config-file option or specifying an alternative file using 
the --with-default-config= option
configure:2380: checking for GNUstep-base installation domain
--installation-domain-for=xxx: prints the value of the default installation 
domain
                personalized using an installation-domains.conf file.
configure:2420: result: LOCAL
configure:2529: checking if we are hardcoding any relative paths in gnustep-base
configure:2531: result: yes
configure:2540: We store the following filesystem layout into gnustep-base, to 
be used when no config file is found
configure:2542: checking for Makefiles directory
configure:2544: result: ../../System/Library/Makefiles
configure:2546: checking for user defaults directory
configure:2548: result: GNUstep/Defaults
configure:2550: checking for user config file
configure:2552: result: .GNUstep.conf
configure:2555: checking for System Applications directory
configure:2557: result: ../../System/Applications
configure:2559: checking for System Admin Applications directory
configure:2561: result: ../../System/Applications/Admin


> 2) If you target to a GNUstep.conf file relative to "Base" location, for 
> example --with config-file=./GNUstep.conf. As before, gnustep-base ignore 
> this file.

You should check that you created/installed the GNUstep.conf file in the same 
directory as the base library (if it's not there, it can't be read) and that it 
contained relative paths ... unless, as I did in the example above, you built 
relative paths in as the defaults when you configured the library.

> But well, after that. I decide make a precompiled package with the standard 
> location (/etc/GNUstep/GNUstep.conf and /usr/GNUstep) as described in 
> README.packaging on gnustep-make source. All seems to be OK. but when I try 
> that package in another machine (also i686), I get a segmentation fault at 
> launch of gdomap, gdnc, gpbs. With openapp TestApp, fixpath return many 
> errors. Nothing specific, something like
> 
> segmentation fault = "\\\ /// ...
> 
> Maybe a problem with a library (objc. objc2, ffi,..)? I have installed those 
> libraries at /usr/GNUstep/Local/Library/Libraries/ on my package.

Quite likely a problem linking in the wrong library version ... having your own 
version won't stop the operating system from using other versions of libraries 
... you need to adjust your environment (eg LD_LIBRARY_PATH) to make sure that 
the operating system uses the libraries you want.