public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "koldat at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29576] New: librtld.os: in function `_dl_start_profile': (.text+0x9444): undefined reference to `strcpy'
Date: Fri, 16 Sep 2022 15:39:46 +0000	[thread overview]
Message-ID: <bug-29576-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29576
           Summary: librtld.os: in function `_dl_start_profile':
                    (.text+0x9444): undefined reference to `strcpy'
           Product: glibc
           Version: 2.36
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: koldat at gmail dot com
                CC: carlos at redhat dot com
  Target Milestone: ---

When building glibc 2.36 I started to see "undefined reference to `strcpy'".

This was working for 2.36. I have found similar issue #29454 that have fixed
one problem of strcpy. Second one is still there. I have tried very latest 2.36
commit in release branch with same result (I have seen patch was backborted
there to fix one of strcpy issues).

I even replaced strcpy wiht stpccy in sprof.c (only place with strcpy withing
elf directory), but did not help. Anyone any idea what can be done?


mv -f /home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/rtld-libc.aT
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/rtld-libc.a
make[3]: Leaving directory '/home/abuild/aports/main/glibc/src/glibc-2.36/elf'
gcc -Wl,--as-needed,-O1,--sort-common  -nostdlib -nostartfiles -r -o
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/librtld.os '-Wl,-('
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/dl-allobjs.os
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/rtld-libc.a -lgcc
'-Wl,-)' \
         
-Wl,-Map,/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/librtld.os.map
gcc -Wl,--as-needed,-O1,--sort-common  -nostdlib -nostartfiles -shared -o
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/ld.so.new
\
          -Wl,-z,relro -Wl,-z,defs -Wl,-z,now   \
          -Wl,-z,pack-relative-relocs \
          /home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/librtld.os
-Wl,--version-script=/home/abuild/aports/main/glibc/src/glibc-2.36/build/ld.map
\
          -Wl,-soname=ld-linux-x86-64.so.2
/usr/lib/gcc/x86_64-alpine-linux-gnu/11.2.1/../../../../x86_64-alpine-linux-gnu/bin/ld:
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/librtld.os: in function
`_dl_start_profile':
(.text+0x9444): undefined reference to `strcpy'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1346:
/home/abuild/aports/main/glibc/src/glibc-2.36/build/elf/ld.so] Error 1
make[2]: Leaving directory '/home/abuild/aports/main/glibc/src/glibc-2.36/elf'
make[1]: *** [Makefile:484: elf/subdir_lib] Error 2
make[1]: Leaving directory '/home/abuild/aports/main/glibc/src/glibc-2.36'

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

             reply	other threads:[~2022-09-16 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 15:39 koldat at gmail dot com [this message]
2022-09-16 15:41 ` [Bug build/29576] " koldat at gmail dot com
2022-09-17 15:35 ` carlos at redhat dot com
2022-09-19  6:44 ` koldat at gmail dot com
2022-09-19  6:46 ` koldat at gmail dot com
2022-09-19 14:07 ` adhemerval.zanella at linaro dot org
2022-09-19 18:09 ` carlos at redhat dot com
2022-10-09 14:55 ` romain.naour at gmail dot com
2022-10-09 22:09 ` adhemerval.zanella at linaro dot org
2022-12-29 13:00 ` adhemerval.zanella at linaro dot org

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-29576-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).