From: David Edelsohn <dje.gcc@gmail.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Bruno Haible <bruno@clisp.org>
Subject: Re: [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext
Date: Wed, 15 Nov 2023 14:58:52 -0500 [thread overview]
Message-ID: <CAGWvnynXnV6g=uXMqXdXzSJkVjQzwZ_H8ru8g+H8ZR5mZRYW8Q@mail.gmail.com> (raw)
In-Reply-To: <8634x7hza7.fsf@aarsen.me>
[-- Attachment #1: Type: text/plain, Size: 4976 bytes --]
On Wed, Nov 15, 2023 at 9:22 AM Arsen Arsenović <arsen@aarsen.me> wrote:
>
> David Edelsohn <dje.gcc@gmail.com> writes:
>
> > GCC had been working on AIX with NLS, using "--with-included-gettext".
> > --disable-nls gets past the breakage, but GCC does not build for me on
> AIX
> > with NLS enabled.
>
> That should still work with gettext 0.22+ extracted in-tree (it should
> be fetched by download_prerequisites).
>
> > A change in dependencies for GCC should have been announced and more
> widely
> > socialized in the GCC development mailing list, not just GCC patches
> > mailing list.
> >
> > I have tried both the AIX Open Source libiconv and libgettext package,
> and
> > the ones that I previously built. Both fail because GCC configure
> decides
> > to disable NLS, despite being requested, while libcpp is satisfied, so
> > tools in the gcc subdirectory don't link against libiconv and the build
> > fails. With the included gettext, I was able to rely on a
> self-consistent
> > solution.
>
> That is interesting. They should be using the same checks. I've
> checked trunk and regenerated files on it, and saw no significant diff
> (some whitespace changes only). Could you post the config.log of both?
>
GCC configured with --with-libintl-prefix and --with-libiconv-prefix
libcpp/config.log:
configure:7610: checking for GNU gettext in libc
configure:7639: /nasfarm/edelsohn/install/GCC12/bin/gcc -std=gnu99 -o
conftest -g -static-libstdc++ -static-libgcc -Wl,-bbigtoc conftest.c >&5
conftest.c:71:10: fatal error: libintl.h: No such file or directory
71 | #include <libintl.h>
| ^~~~~~~~~~~
configure:8318: checking for GNU gettext in libintl
configure:8355: /nasfarm/edelsohn/install/GCC12/bin/gcc -std=gnu99 -o
conftest -g -I/nasfarm/edelsohn/install/include -static-libstdc++
-static-libgcc -Wl,-bbigtoc conftest.c /nasfarm/edelsohn/install/lib/
libintl.a >&5
ld: 0711-317 ERROR: Undefined symbol: .libiconv_open
ld: 0711-317 ERROR: Undefined symbol: .libiconv_set_relocation_prefix
ld: 0711-317 ERROR: Undefined symbol: .libiconv_close
ld: 0711-317 ERROR: Undefined symbol: .libiconv
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
collect2: error: ld returned 8 exit status
configure:8355: $? = 1
configure:8392: /nasfarm/edelsohn/install/GCC12/bin/gcc -std=gnu99 -o
conftest -g -I/nasfarm/edelsohn/install/include -static-libstdc++
-static-libgcc -Wl,-bbigtoc conftest.c /nasfarm/edelsohn/install/lib/
libintl.a /nasfarm/edelsohn/install/lib/libiconv.a >&5
configure:8392: $? = 0
configure:8405: result: yes
configure:8440: checking whether to use NLS
configure:8442: result: yes
configure:8445: checking where the gettext function comes from
configure:8456: result: external libintl
configure:8464: checking how to link with libintl
configure:8466: result: /nasfarm/edelsohn/install/lib/libintl.a
/nasfarm/edelsohn/install/lib/libiconv.a
configure:8525: checking whether NLS is requested
configure:8531: result: yes
gcc/config.log:
configure:14002: checking for GNU gettext in libc
configure:14031: /nasfarm/edelsohn/install/GCC12/bin/g++ -std=c++11 -o
conftest
-g -static-libstdc++ -static-libgcc -Wl,-bbigtoc conftest.cpp >&5
conftest.cpp:196:10: fatal error: libintl.h: No such file or directory
196 | #include <libintl.h>
| ^~~~~~~~~~~
configure:14710: checking for GNU gettext in libintl
configure:14747: /nasfarm/edelsohn/install/GCC12/bin/g++ -std=c++11 -o
conftest -g -I/nasfarm/edelsohn/install/include -static-libstdc++
-static-libgcc -Wl,-bbigtoc conftest.cpp /nasfarm/edelsohn/install/lib/
libintl.a >&5
ld: 0711-317 ERROR: Undefined symbol: .libiconv_open
ld: 0711-317 ERROR: Undefined symbol: .libiconv_set_relocation_prefix
ld: 0711-317 ERROR: Undefined symbol: .libiconv_close
ld: 0711-317 ERROR: Undefined symbol: .libiconv
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
collect2: error: ld returned 8 exit status
configure:14747: $? = 1
configure:14797: result: no
configure:14832: checking whether to use NLS
configure:14834: result: no
configure:14917: checking whether NLS is requested
configure:14920: result: no
> I've never used AIX. Can I reproduce this on one of the cfarm machines
> to poke around? I've tried cfarm119, but that one lacked git, and I
> haven't poked around much further due to time constraints.
>
> TIA, sorry about the inconvenience. Have a lovely day.
>
> > The current gettext-0.22.3 fails to build for me on AIX.
> >
> > libcpp configure believes that NLS functions on AIX, but gcc configure
> > fails in its tests of gettext functionality, which leads to an
> inconsistent
> > configuration and build breakage.
> >
> > Thanks, David
>
>
> --
> Arsen Arsenović
>
next prev parent reply other threads:[~2023-11-15 19:59 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 20:37 David Edelsohn
2023-11-14 23:06 ` Arsen Arsenović
2023-11-15 1:49 ` David Edelsohn
2023-11-15 12:29 ` building GNU gettext on AIX Bruno Haible
2023-11-15 19:26 ` David Edelsohn
2023-11-15 21:22 ` Bruno Haible
2023-11-15 21:31 ` David Edelsohn
2023-11-15 22:39 ` Bruno Haible
2023-11-16 16:00 ` David Edelsohn
2023-11-16 16:35 ` David Edelsohn
2023-11-16 18:01 ` David Edelsohn
2023-11-16 18:17 ` David Edelsohn
2023-11-16 18:52 ` Bruno Haible
2023-11-16 22:18 ` David Edelsohn
2023-11-16 22:46 ` Bruno Haible
2023-11-16 23:10 ` Arsen Arsenović
2023-11-17 8:33 ` Richard Biener
2023-11-17 8:49 ` Arsen Arsenović
2023-11-17 12:24 ` Bruno Haible
2023-11-17 13:06 ` Arsen Arsenović
2023-11-16 23:38 ` David Edelsohn
2023-11-17 0:07 ` Bruno Haible
2023-11-17 0:15 ` David Edelsohn
[not found] ` <84B39BF1-33D5-488E-8CF5-D08B09417568@gmail.com>
2023-11-16 17:44 ` David Edelsohn
2023-11-16 18:47 ` Bruno Haible
2023-11-16 18:50 ` Arsen Arsenović
2023-11-16 18:59 ` Bruno Haible
2023-11-16 19:14 ` Arsen Arsenović
2023-11-19 19:49 ` Bruno Haible
2023-11-15 14:14 ` [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-11-15 15:51 ` Xi Ruoyao
2023-11-16 18:48 ` Arsen Arsenović
2023-11-15 17:19 ` David Edelsohn
2023-11-16 18:33 ` Arsen Arsenović
2023-11-16 21:11 ` Arsen Arsenović
2023-11-16 21:40 ` David Edelsohn
2023-11-16 22:19 ` Arsen Arsenović
2023-11-16 22:30 ` David Edelsohn
2023-11-16 22:32 ` Arsen Arsenović
2023-11-16 23:59 ` David Edelsohn
2023-11-17 8:34 ` Arsen Arsenović
2023-11-17 8:50 ` Richard Biener
2023-11-17 8:56 ` Arsen Arsenović
2023-11-17 14:41 ` David Edelsohn
2023-11-17 15:16 ` Arsen Arsenović
2023-11-17 16:07 ` David Edelsohn
2023-11-18 18:10 ` Arsen Arsenović
2023-11-19 21:55 ` Bruno Haible
2023-11-19 23:00 ` Bruno Haible
2023-11-19 23:06 ` Andrew Pinski
2023-11-20 1:17 ` David Edelsohn
2023-11-20 21:18 ` Arsen Arsenović
2023-11-20 21:38 ` David Edelsohn
2023-11-21 0:44 ` Arsen Arsenović
2023-11-20 23:00 ` Bruno Haible
2023-11-21 0:45 ` Arsen Arsenović
2023-11-21 13:13 ` Arsen Arsenović
2023-11-21 16:28 ` David Edelsohn
2023-11-21 20:58 ` Eric Gallager
2023-11-15 19:58 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 8:27 Arsen Arsenović
2023-11-10 10:37 ` Richard Biener
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='CAGWvnynXnV6g=uXMqXdXzSJkVjQzwZ_H8ru8g+H8ZR5mZRYW8Q@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=arsen@aarsen.me \
--cc=bruno@clisp.org \
--cc=gcc-patches@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).