Re: [gnome-core] Build failure for gnome-vfs2-unified: undefined macro

[Stephen M. <ern...@gm...>]

Alexander Hansen wrote:
> Stephen Malton wrote:
>>
>> Martin Costabel wrote:
>>> Stephen Malton wrote:
>>>> []
>>>>>> fink dumpinfo gnome-vfs2-unified | grep "^ PATH"
>>>>>> PATH=/sw/var/lib/fink/path-prefix-g++-4.0:/sw/bootstrap/bin:/sw/bootstrap/sbin:/bin:/usr/bin:/sbin:/usr/sbin:/sw/bin:/sw/sbin:/usr/X11R6/bin 
>>>>>>
>>>>>
>>>
>>> The only way i can imagine you get this is that you have two unusual 
>>> things:
>>>
>>> 1) A directory /sw/bootstrap
>>> 2) A modified script /sw/bin/init.sh
>>>
>>> Point 1) triggers a feature of fink that adds 
>>> /sw/bootstrap/bin:/sw/bootstrap/sbin to PATH if such a directory 
>>> exists. This is completely harmless.
>>>
>>> Point 2): you must have modified the line in /sw/bin/init.sh where 
>>> it says
>>>
>>>   prepend_path PATH /sw/bin:/sw/sbin
>>>
>>> to do something else, probably "append_path" instead of "prepend_path".
>>>
>>
>> Interestingly, the PATH variable that fink reports in 'dumpinfo' 
>> differs from the one that is set in the environment:
>> echo $PATH
>> /usr/local/bin:/sw/bin:/sw/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin 
>>
>
> fink doesn't use the user's environment setting when building, so it's 
> pretty normal for the PATH it uses when building and the user's PATH 
> to be different.  Maybe it doesn't just source the startup script 
> though, since on comparing a user path and what fink uses in builds 
> the order of common elements differs (e.g. /sbin:/usr/sbin vs. 
> /usr/sbin:/sbin -- which holds on my system, too)
>
Ok. Well, I've bitten the bullet and gone for the nuclear option - fresh 
install of fink. The path now looks right; hopefully once the 70 odd 
remaining dependencies are done I'll know whether this will build. 
Thanks all for you time.