On Thu, 06 Aug 2009 01:35:32 -0500, khsing <khsing...@gmail.com> wrote:
I have found the reason. because libtool15 have been mv to libtool22.
It is documented in /usr/ports/UPDATING.
so upgrade libtool from 15 to 22 will resolve this problem.
portmaster -Btuw libtool
On Thu, Aug 6, 2009 at 12:36 PM, 葉佳威 Jiawei Ye<leafy7...@gmail.com>
wrote:
On Thu, Aug 6, 2009 at 12:10 PM, khsing <khsing...@gmail.com> wrote:
When I deinstall devel/glib20 ports. I got this message
===> Deinstalling for devel/glib20
===> Deinstalling glib-2.20.4
pkg_delete: file '/usr/local/lib/libgio-2.0.so.0' doesn't exist
pkg_delete: file '/usr/local/lib/libglib-2.0.so.0' doesn't exist
pkg_delete: file '/usr/local/lib/libgmodule-2.0.so.0' doesn't exist
pkg_delete: file '/usr/local/lib/libgobject-2.0.so.0' doesn't exist
pkg_delete: file '/usr/local/lib/libgthread-2.0.so.0' doesn't exist
pkg_delete: couldn't entirely delete package (perhaps the packing list
is
incorrectly specified?)
On Thu, Aug 6, 2009 at 12:07 PM, khsing<khsing...@gmail.com> wrote:
> When I install graphics/p5-Image-Magick-Iterator, I have got some
> message below.
>
> I think the devel/glib install is not correct, so made this error.
>
> gmake[4]: Leaving directory
> `/usr/ports/devel/glib20/work/glib-2.20.4/docs'
> gmake[3]: Leaving directory
> `/usr/ports/devel/glib20/work/glib-2.20.4/docs'
> gmake[2]: Leaving directory
> `/usr/ports/devel/glib20/work/glib-2.20.4/docs'
> gmake[1]: Leaving directory
`/usr/ports/devel/glib20/work/glib-2.20.4'
> ===> Running ldconfig
> /sbin/ldconfig -m /usr/local/lib
> ===> Registering installation for glib-2.20.4
> ===> Returning to build of liblqr-1-0.4.1
> Error: shared library "glib-2.0.0" does not exist
> *** Error code 1
>
> Stop in /usr/ports/graphics/liblqr-1.
> *** Error code 1
>
> Stop in /usr/ports/graphics/ImageMagick.
> *** Error code 1
>
> Stop in /usr/ports/graphics/ImageMagick.
> *** Error code 1
>
> Stop in /usr/ports/graphics/p5-Image-Magick-Iterator.
>
>
> --
> A man live in jail and want to break.
> http://blog.khsing.net
>
I had the same issue with my new 4-core AMD64 -current system too. I
suspect
it's the new libtool and MAKE_JOBS_NUMBER>1.
If I use MAKE_JOBS_NUMBERS>1 + libtool 2.2, both glib and atk are built
with
very strange lib version.
glib is 2.0.200, atk is 1.2.6092 (or something like that, I don't have
the
exact error message anymore). To work around, set MAKE_JOB_NUMBERS=1 in
make.conf and rebuild glib. that should make the problem go away for the
moment.
Cheers,
Jiawei
--
"If it looks like a duck, walks like a duck, and quacks like a duck,
then to
the end user it's a duck, and end users have made it pretty clear they
want
a duck; whether the duck drinks hot chocolate or coffee is irrelevant."
--
me...@cox.net - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
