public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: 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 13:16:48 +0200	[thread overview]
Message-ID: <87k0bpth0f.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPf2Or57z=+EJvW3VuiNtCdfXbMdTOq9tDwq1Bzw-aabtC9wBA@mail.gmail.com> (Manolo Padron Martinez via Libc-help's message of "Fri, 15 Apr 2022 23:42:15 +0100")

* 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


  reply	other threads:[~2022-04-16 11:16 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 [this message]
2022-04-16 13:15   ` Manolo Padron Martinez
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=87k0bpth0f.fsf@oldenburg.str.redhat.com \
    --to=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).