Skip site navigation (1)Skip section navigation (2)
Date:      28 Nov 2004 21:16:57 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        gabriel <normal1.lists@gmail.com>
Cc:        freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: Installing libgnome-2.8.0 (really trying galeon)
Message-ID:  <44fz2to0va.fsf@be-well.ilk.org>
In-Reply-To: <efb858204112709522b2f109c@mail.gmail.com>
References:  <efb858204112709522b2f109c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
gabriel <normal1.lists@gmail.com> writes:

> Hello guys!
> 
> I'm trying to install galeon (the lastes port version) for like the
> tenth time and as always I haven't been successfull at all. When I try
> to install galeon it goes through its motions of installing
> dependencies and such until it reaches libgnome-2.8.0 and well, thats
> where all hell breaks loose.
> 
> Here's a snip:
> ===>  Building for libgnome-2.8.0_1
> gmake  all-recursive
> gmake[1]: Entering directory `/usr/ports/x11/libgnome/work/libgnome-2.8.0'
> Making all in libgnome
> gmake[2]: Entering directory
> `/usr/ports/x11/libgnome/work/libgnome-2.8.0/libgnome'
> gmake  all-am
> gmake[3]: Entering directory
> `/usr/ports/x11/libgnome/work/libgnome-2.8.0/libgnome'
> /bin/sh /usr/local/bin/libtool15 --mode=link cc -O -pipe 
> -L/usr/local/lib -o gnome-open  gnome-open.o libgnome-2.la -lpopt
> cc -O -pipe -o .libs/gnome-open gnome-open.o  -L/usr/local/lib
> ./.libs/libgnome-2.so -L/usr/X11R6/lib -lgnomevfs-2 -lbonobo-2
> -lbonobo-activation -lgconf-2 -lORBit-2 -lgobject-2.0 -lgmodule-2.0
> -lgthread-2.0 -lglib-2.0 -liconv -lesd -laudiofile -lm -lpopt
> -Wl,--rpath -Wl,/usr/X11R6/lib
> gmake[3]: Leaving directory
> `/usr/ports/x11/libgnome/work/libgnome-2.8.0/libgnome'
> gmake[2]: Leaving directory
> `/usr/ports/x11/libgnome/work/libgnome-2.8.0/libgnome'
> gmake[1]: Leaving directory `/usr/ports/x11/libgnome/work/libgnome-2.8.0'
> *** Error code 2
> 
> Stop in /usr/ports/x11/libgnome.
> </snip>

I don't see any signs of the actual errors in there.  Don't use '-j'
when reporting problems, and make sure you do a "make clean" before
starting the build.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44fz2to0va.fsf>