public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/31412] New: GCC 6 failed to build i386 glibc on Fedora 39
Date: Sat, 24 Feb 2024 18:41:09 +0000	[thread overview]
Message-ID: <bug-31412-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31412
           Summary: GCC 6 failed to build i386 glibc on Fedora 39
           Product: glibc
           Version: 2.40
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
                CC: carlos at redhat dot com, fweimer at redhat dot com
  Target Milestone: ---
            Target: i386

[hjl@gnu-cfl-3 tmp]$ cat x.c
#include <iostream>

int
main ()
{
  std::cout << "Hello, world!";
  return 0;
}
[hjl@gnu-cfl-3 tmp]$ /usr/gcc-6.4.1-x32/bin/g++ -m32 x.c -static
/usr/local/bin/ld: /lib/../lib/libc.a(offtime.o): in function `__offtime':
(.text+0x3c): undefined reference to `__divmoddi4'
/usr/local/bin/ld: (.text+0xa2): undefined reference to `__divmoddi4'
/usr/local/bin/ld: (.text+0x22e): undefined reference to `__divmoddi4'
collect2: error: ld returned 1 exit status
[hjl@gnu-cfl-3 tmp]$ /usr/gcc-7.4.1-x32/bin/g++ -m32 x.c -static
[hjl@gnu-cfl-3 tmp]$ 

Since /lib/libc.a on Fedora 39 was compiled with GCC 13, it uses __divmoddi4
which was added to GCC 7 and GCC 6 won't be able to create static binary on
Fedora 39.  Why is static linking required here?

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

             reply	other threads:[~2024-02-24 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 18:41 hjl.tools at gmail dot com [this message]
2024-02-24 23:27 ` [Bug build/31412] " fw at deneb dot enyo.de
2024-02-25 12:17 ` hjl.tools at gmail 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-31412-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).