Re: Problem building garnome 0.24.2 on Solaris 9 - HELP needed

[Eric Damphousse <ericdamphousse darwingroup net>]

Again, another error....

It seems to me that the bunzip2 thing aint working right. This error looks
strangely like the other I previously mentionned. In this case, the pkgconfig-0.15.0
directory was empty, and therefore, could not run the .configure. I manually
bunzip and untar and the .configure ran. 

make[6]: Entering directory `/home/ericd/Projects/garnome-0.24.2/bootstrap/pkgconfig'
--15:41:34--  http://ftp.gnome.org/pub/GNOME/sources/pkgconfig/0.15/pkgconfig-0.15.0.tar.bz2
           => `download/partial/pkgconfig-0.15.0.tar.bz2'
Resolving ftp.gnome.org... done.
Connecting to ftp.gnome.org[130.239.18.173]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 490,351 [application/x-tar]

100%[====================================================>] 490,351     
151.87K/s    ETA 00:00

15:41:37 (151.87 KB/s) - `download/partial/pkgconfig-0.15.0.tar.bz2' saved
[490351/490351]

make[6]: Leaving directory `/home/ericd/Projects/garnome-0.24.2/bootstrap/pkgconfig'
    [fetch] complete for pkgconfig.
 ==> Running checksum on pkgconfig-0.15.0.tar.bz2
8e3f44717a76069fcc8fdae9c252369b  download/pkgconfig-0.15.0.tar.bz2
/bin/sh: md5sum: not found
file pkgconfig-0.15.0.tar.bz2 passes checksum test!
    [checksum] complete for pkgconfig.
install -d work/main.d
 ==> Extracting download/pkgconfig-0.15.0.tar.bz2
    [extract] complete for pkgconfig.
install -d work/main.d/pkgconfig-0.15.0
    [patch] complete for pkgconfig.
 ==> Running configure in work/main.d/pkgconfig-0.15.0
/bin/sh: ./configure: not found

I now have a another problem... ie:

configure: error: I can't find the libraries for the thread implementation
 posix. Please choose another thread implementation or
 provide information on your thread implementation.
 You can also run 'configure --disable-threads' 
 to compile without thread support.
 
But my guess, its another set of problems, unrelated to the first one.

Eric Damphousse wrote:

Found out a few interesting things:

If I manually gunzip2 | tar xvf the gtk+-2.2.1 file then rerun the make... I still get the previously noted msg, but this time, if I specified the full path of the file it wants to diff, ie: gtk+-2.2.1/gtk/gtkstyle.c, then it works, but complains about the next file its trying to diff.

So, I could potentially make this work, but I doubt very much that this is the way it has been planned.

Any ideas?

Eric

Eric Damphousse wrote:

Ok,

You have assumed right, garnome uses recent GAR. I have tried both methods you have specified, and the problem now is as such:

 ==> Applying patch download/insensitive-iain.diff
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --speed-large-files --minimal -Nru gtk+-2.2.1/gtk/gtkstyle.c gtk+-2.2.1/gtk/gtkstyle.c
|--- gtk+-2.2.1/gtk/gtkstyle.c    2003-01-31 15:42:34.000000000 +1100
|+++ gtk+-2.2.1/gtk/gtkstyle.c    2003-02-08 08:11:30.000000000 +1100
--------------------------
File to patch: "it expects something from me,"

Any clues,,,

I will do my googleing to see if anyone else had those issues....


Eric Damphousse wrote:

Will do!... and thanks

Nick Moffitt wrote:

begin  Eric Damphousse  quotation:
  

 You either have to fix gar.conf.mk to use gpatch,
 >or symlink /usr/bin/gpatch to "some path/patch" such
 >that "some path" is in front of /usr/bin, which is
 >where the patch binary you're getting output from
 >is.  I assume you're trying to build on Solaris.
    

	Yeah, that's a likely culprit.  

First of all, make sure you install GNU patch.

Second, I'm assuming garnome 0.24.2 (242 sighting!) uses recent GAR,
which has the following at about line 204 of gar.lib.mk:

PATCHDIR ?= $(WORKDIR)
PATCHDIRLEVEL ?= 1
PATCHDIRFUZZ ?= 2
GARPATCH = patch -d$(PATCHDIR) -p$(PATCHDIRLEVEL) -F$(PATCHDIRFUZZ)

	if this is so, then you can do:

make GARPATCH='/usr/bin/gpatch -d$(PATCHDIR) -p$(PATCHDIRLEVEL) -F$(PATCHDIRFUZZ)' install

and the patch rules will use the new patch utility.  Barring that,
just edit gar.lib.mk and swap in the location for GNU patch wherever
you have the system calling the raw "patch" executable.