--s2lX4GznBIrto1wi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 23, 2003 at 03:37:53PM +0200, Michal 'hramrach' Suchanek
wrote:
>
> I cannot imagine how the package would link with iconv instead of
> libiconv since it insists on linking with the nonexistent library.
> Unless there is a bug either in the packages or in the buildlink
> script which prevents the correct linking.  Since I had to rebuild
> everything from glib up to satisfy the dependencies I doubt there was
> an obsolete package which specified the -liconv in its config script.

make sure your pkgsrc tree is up to date.

the older packages are built against libiconv, since there was no
iconv() in libc at that time.  they are still bringing their dependency
to the build and insist on using libiconv.

it's not a bug, it's called evolution.  this is -current after all.


regards,

--=20
-- Lubomir Sedlacik <salo@Xtrmntr.org>                   --
--                  <salo@silcnet.org>                   --

--s2lX4GznBIrto1wi
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/l9yyiwjDDlS8cmMRAvmqAJ9wcWKGjPHvryAq2b23IioR6HlkdACeOjAV
LLvuC/fQFXcbon6FcHdWriQ=
=jnMY
-----END PGP SIGNATURE-----

--s2lX4GznBIrto1wi--