Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Jan 2009 10:40:11 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        Da Rock <rock_on_the_web@comcen.com.au>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: x11/libXrandr, x11-toolkits/libXmu, graphics/jasper fails to  build
Message-ID:  <44zlhbo2w4.fsf@lowell-desk.lan>
In-Reply-To: <1233094843.1202.30.camel@laptop2.herveybayaustralia.com.au> (Da Rock's message of "Wed\, 28 Jan 2009 08\:20\:43 %2B1000")
References:  <1233019367.41990.88.camel@laptop1.herveybayaustralia.com.au> <1233025480.1751.13.camel@wombat.2hip.net> <1233028584.1110.6.camel@laptop2.herveybayaustralia.com.au> <f84c38580901270627r5eb40916g12f1e7adedf19298@mail.gmail.com> <1233067663.18867.13.camel@lenzix.cwb.casa> <1233094843.1202.30.camel@laptop2.herveybayaustralia.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Da Rock <rock_on_the_web@comcen.com.au> writes:

> On Tue, 2009-01-27 at 12:47 -0200, Sergio de Almeida Lenzi wrote:
>> Em Ter, 2009-01-27 =E0s 09:27 -0500, Tsu-Fan Cheng escreveu:
>>=20
>> > Hi,
>> >     have you solved the problem yet? I also have libXmu failed to
>> > upgrade due to libxcb-xlib.la. Thanks!!
>>=20
>> I removed every instance of libxb-xlib.la from /usr/local/lib/*.la
>> than it all works again
>>=20
>> a shell script like:
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
>> #!/bin/sh
>>=20
>> lista=3D`find /usr/local/lib  -type f -name "*.la"`
>>=20
>> if [ -n "$lista" ]
>> then
>> 	for i in $lista
>> 	do
>> 		if grep $1 $i > /dev/null
>> 		then
>> 			sed -i "" "s|/usr/local/lib/$1||" $lista
>> 		fi
>> 	done
>> fi
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>> supose you name this shell ->  XX
>> than.....
>> sh XX libxcb-xlib.la=20
>> will do the trick....
>>=20
>> after that, you will be able to build things again.
>
> I've been talking to the porters and that would not be the recommended
> way of fixing this. Running portupgrade -a -rf libxcb resolves the
> issue.

That probably isn't the exactly recommended form either.=20
"-a" and "-r" don't make sense together; the "-r" will be ignored, and
you will end up rebuilding *everything*.

--=20
Lowell Gilbert, embedded/networking software engineer, Boston area
		http://be-well.ilk.org/~lowell/



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