From: Manolo Padron Martinez <manolopm@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Manolo Padron Martinez via Libc-help <libc-help@sourceware.org>
Subject: Re: Help compiling glibc 2.31 wih System V abi for powerpc
Date: Sat, 16 Apr 2022 14:15:07 +0100 [thread overview]
Message-ID: <CAPf2Or7xbVtDQY4suOV2jtC2iZUK0LFmFcKVZShZ+jVXLbFJVw@mail.gmail.com> (raw)
In-Reply-To: <87k0bpth0f.fsf@oldenburg.str.redhat.com>
First, Thanks for the answer Florian!
I still have the same problem. libc_pic.a keeps telling me that
gettimeofday and time its using GNU ABI, and when it links libc.so it
becomes GNU ABI.
The reason that I need it in System V its I have an old powerpc with and
old linux distro, when I try to cross compile something for this machine I
get problems because it has an on libc, so I need libc and If I try to use
it with GNU ABI the program said "wrong ABI format" .
On Sat, Apr 16, 2022 at 12:16 PM Florian Weimer <fweimer@redhat.com> wrote:
> * Manolo Padron Martinez via Libc-help:
>
> > I'm trying to compile glibc for a device with a powerpc processor that
> have
> > an old distro.
> > I'm using debian and crosscompiling it.
> > It seems to compile but when I use readelf to check the abi of libc.so I
> > get UNIX - GNU.
> > I take a look to all .a files and I have seen that everything is compiled
> > with UNIX - System V except the entries related to gettimeofday and time
> in
> > libc_pic.a.
> >
> > I think I've tried everything but still get that part with UNIX - GNU.
> > The configure options I'm trying are this:
> >
> > --host=powerpc-linux-gnu --enable-oldest-abi --prefix=/tmp/binglibc
> > --disable-werror CFLAGS='-D_GLIBCXX_USE_CXX11_ABI=0 -mcall-sysv-noeabi
> -O2
> > -U HAVE_ELFV2_ABI
>
> I'm not sure if -mcall-sysv-noeabi is safe. -U HAVE_ELFV2_ABI won't
> have any effect for powerpc (32-bit).
>
> > Any idea what I could try?
>
> The GNU ABI probably comes from IFUNC usage, so you could try
> configuring with --disable-multi-arch. But it would have to be a
> strange configuration where the ABI field would matter because your
> cross-toolchain is apparently compatible with it, and glibc is as well.
>
> Thanks,
> Florian
>
>
next prev parent reply other threads:[~2022-04-16 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 22:42 Manolo Padron Martinez
2022-04-16 11:16 ` Florian Weimer
2022-04-16 13:15 ` Manolo Padron Martinez [this message]
2022-04-16 13:41 ` Florian Weimer
2022-04-16 21:51 ` Manolo Padron Martinez
2022-04-19 10:04 ` Florian Weimer
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=CAPf2Or7xbVtDQY4suOV2jtC2iZUK0LFmFcKVZShZ+jVXLbFJVw@mail.gmail.com \
--to=manolopm@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.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).