public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "john.frankish at outlook dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29938] New: glibc-2.36 fails to build with Os with undefined reference to strcpy
Date: Fri, 23 Dec 2022 12:52:31 +0000	[thread overview]
Message-ID: <bug-29938-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29938
           Summary: glibc-2.36 fails to build with Os with undefined
                    reference to strcpy
           Product: glibc
           Version: 2.36
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: john.frankish at outlook dot com
                CC: carlos at redhat dot com
  Target Milestone: ---

glibc-2.36 fails to build with Os, but builds without error with O2.

Built using:

echo "rootsbindir=/usr/sbin" > configparms

CC="gcc -mtune=generic -Os -pipe" ../configure --prefix=/usr --disable-werror
--enable-kernel=5.4.3 --enable-stack-protector=strong
--with-headers=/usr/include libc_cv_slibdir=/lib --enable-obsolete-rpc
--libexecdir=/usr/lib/glibc

find . -name config.make -type f -exec sed -i 's/-g -O2//g' {} \;
find . -name config.status -type f -exec sed -i 's/-g -O2//g' {} \;
find ../ -name Makeconfig -type f -exec sed -i 's/-g -O2//g' {} \;

make

/usr/lib/gcc/x86_64-tc-linux-gnu/12.2.0/../../../../x86_64-tc-linux-gnu/bin/ld:
/sources/glibc-2.36/build/elf/librtld.os: in function `_dl_start_profile':
(.text+0x9587): undefined reference to `strcpy'
/usr/lib/gcc/x86_64-tc-linux-gnu/12.2.0/../../../../x86_64-tc-linux-gnu/bin/ld:
/sources/glibc-2.36/build/elf/librtld.os: in function `_dl_load_cache_lookup':
(.text+0xe5fd): undefined reference to `strcpy'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1346: /sources/glibc-2.36/build/elf/ld.so] Error 1

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

             reply	other threads:[~2022-12-23 12:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23 12:52 john.frankish at outlook dot com [this message]
2022-12-24  1:09 ` [Bug build/29938] " goldstein.w.n at gmail dot com
2022-12-25  9:26 ` john.frankish at outlook dot com
2022-12-26 20:23 ` goldstein.w.n at gmail dot com
2022-12-27 14:17 ` john.frankish at outlook dot com
2022-12-27 14:18 ` john.frankish at outlook dot com
2022-12-29 12:59 ` adhemerval.zanella at linaro dot org
2022-12-29 13:00 ` adhemerval.zanella at linaro dot org
2022-12-31 11:35 ` john.frankish at outlook dot com
2022-12-31 13:32 ` adhemerval.zanella at linaro dot org
2022-12-31 15:50 ` john.frankish at outlook dot com
2023-01-03 15:13 ` adhemerval.zanella at linaro dot org
2023-01-03 16:28 ` john.frankish at outlook 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-29938-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).