Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15306] New: glibc build fails
Date: Tue, 31 Jan 2023 22:41:33 +0000	[thread overview]
Message-ID: <bug-15306-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15306

            Bug ID: 15306
           Summary: glibc build fails
           Product: buildroot
           Version: unspecified
          Hardware: Macintosh
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: russelljbrennan@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

I'm trying to build glibc in a [Docker
Container](https://github.com/batocera-linux/batocera.linux/blob/master/Dockerfile)
and I'm getting two error.

The first happens on a clean build, and it *looks like* a path is being munged.
The file `tdgppitrmssgwsgadebug/backtrace.os` is specified and doesn't exist,
although `debug/backtrace.os` does exist:

```
...
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ar:
tdgppitrmssgwsgadebug/backtrace.os: No such file or directory
make[3]: *** [../o-iterator.mk:9:
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/libc_nonshared.a]
Error 1
make[3]: *** Waiting for unfinished jobs....
sed -e 's@
/bcm2837/build/glibc-2\.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/@
$(common-objpfx)@g' -e
's@^/bcm2837/build/glibc-2\.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/@$(common-objpfx)@g'
-e 's@  *\.\.\/\([^     \]*\)@ $(..)\1@g' -e 's@^\.\.\/\([^    
\]*\)@$(..)\1@g' \
   
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.h.dT
>
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.h.dT2
rm -f
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.h.dT
mv -f
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.h.dT2
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.h.d
mv -f
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.hT
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/dl-link.h
make[3]: Leaving directory
'/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/elf'
make[2]: *** [Makefile:484: elf/subdir_lib] Error 2
make[2]: Leaving directory
'/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca'
make[1]: *** [Makefile:9: all] Error 2
make[1]: Leaving directory
'/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build'
make: *** [package/pkg-generic.mk:293:
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/.stamp_built]
Error 2
make: Leaving directory '/build/buildroot'
make: *** [bcm2837-build] Error 2
```

If I resume the build after that error, building progresses but I get a second
error which I guess might be caused by the first:

```
builder@92c3583543fb:/bcm2837/build$
/bcm2837/host/bin/aarch64-buildroot-linux-gnu-gcc   -nostdlib -nostartfiles
-shared -o
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/elf/ld.so.new
-Wl,-z,relro -Wl,-z,defs
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/elf/librtld.os
-Wl,--version-script=/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/ld.map
-Wl,-soname=ld-linux-aarch64.so.1
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ld:
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/elf/librtld.os:
in function `_dl_make_stacks_executable':
(.text+0x24b0): undefined reference to `__lll_lock_wake_private'
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ld:
(.text+0x24c0): undefined reference to `__lll_lock_wait_private'
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ld:
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/elf/librtld.os:
in function `__thread_gscope_wait':
(.text+0xe500): undefined reference to `__lll_lock_wake_private'
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ld:
(.text+0xe508): undefined reference to `__lll_lock_wait_private'
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ld:
/bcm2837/build/glibc-2.36-66-ga1dc0be03c9dd850b864bd7a9c03cf8e396eb7ca/build/elf/librtld.os:
in function `_dl_init_static_tls':
(.text+0xf594): undefined reference to `__lll_lock_wait_private'
/bcm2837/host/lib/gcc/aarch64-buildroot-linux-gnu/12.2.0/../../../../aarch64-buildroot-linux-gnu/bin/ld:
(.text+0xf5b0): undefined reference to `__lll_lock_wake_private'
```


I have tried (with the same result):
- An older version of glibc
- An older version of ubuntu (20.04)

I also see the exact same symptom reported here
https://homematic-forum.de/forum/viewtopic.php?f=65&t=71547

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-01-31 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 22:41 bugzilla [this message]
2023-01-31 22:42 ` [Buildroot] [Bug 15306] glibc build fails in Docker container bugzilla
2023-02-12 18:15 ` bugzilla
2023-02-12 19:57 ` bugzilla
2023-02-13  0:43 ` bugzilla
2023-02-13 11:44 ` bugzilla
2023-03-12 15:17 ` bugzilla
2023-03-12 17:36 ` bugzilla
2023-03-12 19:38 ` bugzilla

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-15306-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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