Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Dec 2023 22:58:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        desktop@FreeBSD.org
Subject:   [Bug 275969] converters/libiconv: Unable to build without including /usr/local/include/iconv.h
Message-ID:  <bug-275969-39348-OKygp4mast@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-275969-39348@https.bugs.freebsd.org/bugzilla/>
References:  <bug-275969-39348@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275969

--- Comment #5 from Rodrigo <rodarima@gmail.com> ---
> Do you have a buildlog somewhere?

I attached the build log.

> I think you have mixed up two different ports. One is converters/iconv an=
d other is converters/libiconv which are different in terms of functionalit=
ies.

Sorry, I didn't realize they were split :-)

> The gotcha here is that you need to also pass -DLIBICONV_PLUG when includ=
ing iconv from localbase.

I tested that and it links properly.

However, the problem remains: I'm including /usr/local/include/iconv.h and
linking with -lc which also provides an iconv implementation. With the
LIBICONV_PLUG the libiconv functions don't get the "lib" prefix.

I'm guessing libiconv and libc try to provide compatible headers, but it se=
ems
a bit fragile to depend on that. So I was looking for a way to avoid includ=
ing
the /usr/local/include/iconv.h file and just include the one provided by the
libc.

And in case there is none, I can instead link with -liconv, which at least
would make more sense than depending on the headers to remain compatible am=
ong
both implementations.

Best,
Rodrigo.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275969-39348-OKygp4mast>