From: Alberto Mijares <amijaresp@gmail.com>
To: libc-help@sourceware.org
Subject: Compiling glibc 2.14.1 on CentOS 6.10
Date: Wed, 9 Aug 2023 20:29:27 -0400 [thread overview]
Message-ID: <CAGZBXN9nj44dZgXDXmR11M5gzhyAg4yBuKKcq+vUJHbiwk4WFg@mail.gmail.com> (raw)
Hello all,
This is my first post to this list and I'm not a developer so please
forgive me if I look like a newbie.
I was assigned with the task to compile PHP 5.6 with an up-to-date
OpenSSL version for CentOS 6.10 so they can integrate their legacy app
with a third-party service. It has been a long journey and now I'm
very close.
Right now I'm trying to compile cmake. which is a requirement for
brotli and this one for Apache -> mod_php56.
The compilation of cmake fails because it cannot find a reference to
sendmmsg, only available since glibc 2.14 (according to a post
somewhere). CentOS comes with glibc 2.12.
So, that's why I'm trying to compile glibc 2.14.1. I'm using pkgsrc as
building framework and after a few patches I managed to get to this
point
make[2]: Entering directory `/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/elf'
cc -L/opt/zvi/gcc7/lib/gcc/x86_64-redhat-linux/7.5.0
-Wl,-R/opt/zvi/gcc7/lib/gcc/x86_64-redhat-linux/7.5.0
-L/opt/zvi/gcc7/lib64 -Wl,-R/opt/zvi/gcc7/lib64 -Wl,-zrelro
-L/opt/zvi/lib -L/usr/lib64 -Wl,-R/usr/lib64 -Wl,-R/opt/zvi/lib
-nostdlib -nostartfiles -r -o
/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/elf/librtld.map.o
'-Wl,-(' /usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/elf/dl-allobjs.os
/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/libc_pic.a
-lgcc '-Wl,-)' -Wl,-Map,/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/elf/librtld.mapT
/opt/zvi/x86_64-redhat-linux/bin/ld:
/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/libc_pic.a(init-first.os):(.data+0x0):
multiple definition of `__libc_multiple_libcs';
/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/elf/dl-allobjs.os:(.bss+0xf4):
first defined here
/opt/zvi/x86_64-redhat-linux/bin/ld:
/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/libc_pic.a(dl-addr.os):
in function `_dl_addr_inside_object':
dl-addr.c:(.text+0x353): multiple definition of
`_dl_addr_inside_object';
/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/elf/dl-allobjs.os:(.text+0x11d2e):
first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/glibc-configure/elf/librtld.map]
Error 1
make[2]: Leaving directory `/usr/pkgsrc/wip/glibc/work/glibc-2.14.1/elf'
make[1]: *** [elf/subdir_lib] Error 2
make[1]: Leaving directory `/usr/pkgsrc/wip/glibc/work/glibc-2.14.1'
make: *** [all] Error 2
*** Error code 2
Stop.
bmake[1]: stopped in /usr/pkgsrc/wip/glibc
*** Error code 1
Stop.
bmake: stopped in /usr/pkgsrc/wip/glibc
This is what I'm using:
gcc version 7.5.0 (GCC)
GNU Make 3.81
GNU ld (GNU Binutils) 2.40
Linux 2.6.32-754.el6.x86_64
pkgsrc-2023Q2
For getting there, I bootstrapped pkgsrc with the system tools and the
compiled gcc7. Then, all the packages were made with gcc7 and combo.
Any hint, suggestion or advice would be very appreciated. Of course
I'm willing to provide more info if needed.
Best regards,
Alberto Mijares
next reply other threads:[~2023-08-10 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:29 Alberto Mijares [this message]
2023-08-10 17:48 ` Adhemerval Zanella Netto
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=CAGZBXN9nj44dZgXDXmR11M5gzhyAg4yBuKKcq+vUJHbiwk4WFg@mail.gmail.com \
--to=amijaresp@gmail.com \
--cc=libc-help@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).