public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/112671] New: libiconv support lacks separate --with-libiconv-{include,lib}
Date: Wed, 22 Nov 2023 13:45:40 +0000	[thread overview]
Message-ID: <bug-112671-4@http.gcc.gnu.org/bugzilla/> (raw)

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.

             reply	other threads:[~2023-11-22 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 13:45 ro at gcc dot gnu.org [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-112671-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).