public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib}
@ 2023-11-22 13:45 ro at gcc dot gnu.org
2023-11-22 14:57 ` [Bug other/112671] " arsen at gcc dot gnu.org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: ro at gcc dot gnu.org @ 2023-11-22 13:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112671
Bug ID: 112671
Summary: libiconv support lacks separate
--with-libiconv-{include,lib}
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
When trying to build trunk on Solaris with GNU libiconv 1.17, I noticed that
the libiconv configure support is limited compared to e.g. gmp etc. On
multilibbed targets like Solaris, you usually install both 32 and 64-bit
versions of a library into <libiconv-prefix>/include (common between 32 and
64-bit) and <libiconv-prefix>/lib (32-bit lib) resp.
<libiconv-prefix>/lib/{amd64,sparcv9}.
The current (simple-minded) support via --with-libiconv-prefix cannot handle
this,
requiring to use two different installations into different prefixes. It's
also inconsistent with the rest of gcc which does support configurations like
this.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug other/112671] libiconv support lacks separate --with-libiconv-{include,lib}
2023-11-22 13:45 [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib} ro at gcc dot gnu.org
@ 2023-11-22 14:57 ` arsen at gcc dot gnu.org
2023-11-22 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: arsen at gcc dot gnu.org @ 2023-11-22 14:57 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112671
--- Comment #1 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
yes, this also came up from the binutils side. see
https://inbox.sourceware.org/binutils/874jhg2x6p.fsf@adacore.com/
I will restore the modifications in the shared tree with the few other patches
I mentioned on the GCC ML recently soon (I've ran a little low on testing
bandwidth this week..)
apologies for the inconvenience
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug other/112671] libiconv support lacks separate --with-libiconv-{include,lib}
2023-11-22 13:45 [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib} ro at gcc dot gnu.org
2023-11-22 14:57 ` [Bug other/112671] " arsen at gcc dot gnu.org
@ 2023-11-22 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-22 15:00 ` arsen at gcc dot gnu.org
2023-11-22 15:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
3 siblings, 0 replies; 5+ messages in thread
From: ro at CeBiTec dot Uni-Bielefeld.DE @ 2023-11-22 14:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112671
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
[...]
> I will restore the modifications in the shared tree with the few other patches
> I mentioned on the GCC ML recently soon (I've ran a little low on testing
> bandwidth this week..)
>
> apologies for the inconvenience
No worries, this is the first time ever I tried this on Solaris and can
easily live with 32-bit-only testing for now.
Thanks for taking care of this.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug other/112671] libiconv support lacks separate --with-libiconv-{include,lib}
2023-11-22 13:45 [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib} ro at gcc dot gnu.org
2023-11-22 14:57 ` [Bug other/112671] " arsen at gcc dot gnu.org
2023-11-22 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
@ 2023-11-22 15:00 ` arsen at gcc dot gnu.org
2023-11-22 15:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
3 siblings, 0 replies; 5+ messages in thread
From: arsen at gcc dot gnu.org @ 2023-11-22 15:00 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112671
--- Comment #3 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
hm, actually, I think I confused reports - sorry.
do you know if this worked a short while ago? and if so, how did such a
configuration look?
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug other/112671] libiconv support lacks separate --with-libiconv-{include,lib}
2023-11-22 13:45 [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib} ro at gcc dot gnu.org
` (2 preceding siblings ...)
2023-11-22 15:00 ` arsen at gcc dot gnu.org
@ 2023-11-22 15:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
3 siblings, 0 replies; 5+ messages in thread
From: ro at CeBiTec dot Uni-Bielefeld.DE @ 2023-11-22 15:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112671
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #3 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
> hm, actually, I think I confused reports - sorry.
>
> do you know if this worked a short while ago? and if so, how did such a
> configuration look?
I have no idea: at least AFAICS back to the gcc-11 branch (didn't look
further) there was only --with-libiconv-prefix.
Still it's inconsistent with how many (all?) other support libs are
handled.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-11-22 15:04 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-22 13:45 [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib} ro at gcc dot gnu.org
2023-11-22 14:57 ` [Bug other/112671] " arsen at gcc dot gnu.org
2023-11-22 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-22 15:00 ` arsen at gcc dot gnu.org
2023-11-22 15:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).