glib2 compilation troubles

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

glib2 compilation troubles

Vijay Ramesh
I haven't been able to compile glib-2.12.11. Did I miss a crucial announcement or is everyone having this problem?

/usr/bin/ld: warning: libglib-2.0.so.1000.3, needed by /usr/local/lib/libgobject-2.0.so.1000.3, may conflict with libglib-2.0.so.1200.11
/usr/local/lib/libglib-2.0.so.1000.3: warning: g_sprintf() is often misused, please use g_snprintf()
/usr/local/lib/libglib-2.0.so.1000.3: warning: g_vsprintf() is often misused, please use g_vsnprintf()
closures.o(.text+0x5a): In function `g_test_get_type':
: undefined reference to `g_type_register_static_simple'
collect2: ld returned 1 exit status
gmake[3]: *** [closures] Error 1
gmake[3]: Leaving directory `/usr/ports/devel/glib2/w-glib-2.12.11/glib-2.12.11/tests/refcount'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/usr/ports/devel/glib2/w-glib-2.12.11/glib-2.12.11/tests'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/devel/glib2/w-glib-2.12.11/glib-2.12.11'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/devel/glib2 (line 2069 of /usr/ports/infrastructure/mk/bsd.port.mk).


Vijay Ramesh
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: glib2 compilation troubles

Marc Espie-2
On Thu, May 10, 2007 at 02:25:15AM -0500, Vijay Ramesh wrote:
> I haven't been able to compile glib-2.12.11. Did I miss a crucial announcement or is everyone having this problem?

In some cases, especially with gnu shit, you have to uninstall the previous
version before compiling the new one.

Since those nitwits who develop libtool do not really understand linking,
that's hardly surprising.

Reply | Threaded
Open this post in threaded view
|

Re: glib2 compilation troubles

Hannah Schroeter
Hi!

On Thu, May 10, 2007 at 10:36:58AM +0200, Marc Espie wrote:
>On Thu, May 10, 2007 at 02:25:15AM -0500, Vijay Ramesh wrote:
>> I haven't been able to compile glib-2.12.11. Did I miss a crucial announcement or is everyone having this problem?

>In some cases, especially with gnu shit, you have to uninstall the previous
>version before compiling the new one.

>Since those nitwits who develop libtool do not really understand linking,
>that's hardly surprising.

Frankly, I encountered the same problem, then tried to uninstall the old
stuff (not really, just moved it away, includes and libs), but still
kept getting the same error message.

*Uninstalling* doesn't work because of those many dependencies. (I
wanted to "make update" in among others glib2, after glib2 was still out
of date after upgrading using the latest snapshot packages.)

Kind regards,

Hannah.

PS: I thought we have a tweaked libtool in our tree/ports?