public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bero at lindev dot ch" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/26360] New: glibc 2.32 fails to crosscompile to ppc64le-linux-gnu using gcc 10.2.0
Date: Mon, 10 Aug 2020 03:45:14 +0000	[thread overview]
Message-ID: <bug-26360-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26360

            Bug ID: 26360
           Summary: glibc 2.32 fails to crosscompile to ppc64le-linux-gnu
                    using gcc 10.2.0
           Product: glibc
           Version: 2.32
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: bero at lindev dot ch
                CC: carlos at redhat dot com
  Target Milestone: ---

Trying to crosscompile glibc 2.32 with a ppc64le-linux-gnu-gcc 10.2.0
crosscompiler on an x86_64-linux-gnu fails.

If -Werror is enabled, it errors out on:

In file included from ../argp/argp.h:23,
                 from ../include/argp.h:2,
                 from ../sysdeps/ieee754/ldbl-opt/nldbl-compat.c:25:
../include/stdio.h:186:1: error: ‘asm’ declaration ignored due to conflict with
previous rename [-Werror=pragmas]
  186 | libc_hidden_ldbl_proto (__asprintf)
      | ^~~~~~~~~~~~~~~~~~~~~~
../include/stdio.h:211:1: error: ‘asm’ declaration ignored due to conflict with
previous rename [-Werror=pragmas]
  211 | libc_hidden_ldbl_proto (dprintf)
      | ^~~~~~~~~~~~~~~~~~~~~~
../include/stdio.h:212:1: error: ‘asm’ declaration ignored due to conflict with
previous rename [-Werror=pragmas]
  212 | libc_hidden_ldbl_proto (fprintf)
      | ^~~~~~~~~~~~~~~~~~~~~~
../include/stdio.h:213:1: error: ‘asm’ declaration ignored due to conflict with
previous rename [-Werror=pragmas]
  213 | libc_hidden_ldbl_proto (vfprintf)
      | ^~~~~~~~~~~~~~~~~~~~~~
../include/stdio.h:214:1: error: ‘asm’ declaration ignored due to conflict with
previous rename [-Werror=pragmas]
  214 | libc_hidden_ldbl_proto (sprintf)
      | ^~~~~~~~~~~~~~~~~~~~~~


Without -Werror, it gets past that point, but later on errors out saying

In file included from <command-line>:
../sysdeps/ieee754/ldbl-opt/nldbl-sscanf.c:22:23: error: ‘_IO_sscanf’ aliased
to undefined symbol ‘sscanf’
   22 | strong_alias (sscanf, _IO_sscanf)
      |                       ^~~~~~~~~~
./../include/libc-symbols.h:140:26: note: in definition of macro
‘_strong_alias’
  140 |   extern __typeof (name) aliasname __attribute__ ((alias (#name))) \
      |                          ^~~~~~~~~
../sysdeps/ieee754/ldbl-opt/nldbl-sscanf.c:22:1: note: in expansion of macro
‘strong_alias’
   22 | strong_alias (sscanf, _IO_sscanf)
      | ^~~~~~~~~~~~


Other targets, including non-le ppc64-linux-gnu, compile fine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-08-10  3:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  3:45 bero at lindev dot ch [this message]
2020-08-10 14:21 ` [Bug build/26360] " carlos at redhat dot com
2020-08-10 15:54 ` bero at lindev dot ch
2020-10-23 21:39 ` suratiamol at gmail dot com
2020-12-06 23:35 ` bero at lindev dot ch
2020-12-07 18:15 ` joseph at codesourcery dot com

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-26360-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).