Re: garnome-list Digest, Vol 35, Issue 11

["B.S.J.W. Stephenson" <es018r6256 blueyonder co uk>]

garnome-list-request gnome org wrote:
> Send garnome-list mailing list submissions to
> 	garnome-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mail.gnome.org/mailman/listinfo/garnome-list
> or, via email, send a message with subject or body 'help' to
> 	garnome-list-request gnome org
>
> You can reach the person managing the list at
> 	garnome-list-owner gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of garnome-list digest..."
>
>
> Today's Topics:
>
>    1. Re: clean building the download files 2.18.0 (guenther)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Mar 2007 00:15:03 +0100
> From: guenther <guenther rudersport de>
> Subject: Re: clean building the download files 2.18.0
> To: garnome-list gnome org
> Message-ID: <1174259703 9626 104 camel monkey loc>
> Content-Type: text/plain
>
> On Sun, 2007-03-18 at 15:59 +0000, B.S.J.W. Stephenson wrote:
>   
> > To whoever
> >     I have just made clean in desktop !!
> > Nothing will now link up , or build properly linked !
> > How should I proceed , to make a complete re-build ?
> >     
>
> Hmm, I'm not sure if I understand you. Is this what you did?
>
> $ cd garnome-2.18.0/
> $ cd desktop/
> $ make clean
>
> Also, what do you mean exactly by that description? How does it not
> build properly? What about the linking?
>
> FWIW, if the above really is, what you did, then it will result in the
> entire desktop/ directory being cleaned and re-set to the state exactly
> like it has been when extracting the GARNOME tarball.
>
> However, this is not a good idea, if you want to build additional
> applications after that. GARNOME is a build environment, and the
> dependencies are provided by this environment. When building any
> application from GARNOME, it will make sure that all dependencies are
> built as well -- which means the "build root" directory, the extracted
> GARNOME tarball. It does not check if the dependencies are installed
> somewhere in the currently set $PATH.
>
> If you are low on disk space, and your goal was to not keep all the
> extracted source directories around, you actually want to have a look at
> the BUILD_CLEAN switch in gar.conf.mk. Running 'make clean' is not the
> solution.
>
>   guenther
>
>
>   
First three commands correct .
The reason for the make clean , was to attempt to rebuild the complete 
repository against corrected libraries , opennss* and kerberos , some of 
which did not have the correct dependencies some miss-configured , other 
faults were due to a lack of Dbus ( I am running a BlueWhite64 linux 11) 
(Dbus faults) which I could not find in my log files during python and 
glib construction , are those visible anywhere ? (I was building in a vi 
terminal , with 'make install' in 'desktop' )have not got round to 
correcting yet (Dbus).
  I can tell it's a "build environment" , how do I reset the build 
environment  to  square one , as if I had just downloaded the  tarball  ?
Is there some simpler arrangement to attain this end ?
If my questions are to prosaic please feel free to say so and I 'll
just listen to other peoples problems .
B.S.J.W. Stephenson