From: Andreas Hubert <anhubert@googlemail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-help@sourceware.org
Subject: Re: Building 2.27 on CentOS
Date: Tue, 29 May 2018 12:05:00 -0000 [thread overview]
Message-ID: <8B580C00-0D93-4DB3-990F-9E7EAA734358@googlemail.com> (raw)
In-Reply-To: <73359be3-8709-5740-c0c6-63896d4106df@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Basically just run
configure —prefix=/somewhere/else
make
I tried with different options and CFLAGS etc. but currently I always end up with the same error.
Currently I try with CC=“gcc -fPIC” but make takes really a while on my machine..
When I use make -j6 then I get another error that some .os file does not exist, which I guess in this case is because the multiple jobs disturb each other.
I tried to attach config.log and make.log, but it seemed it didn’t came through on this mailinglist then.
> Am 29.05.2018 um 13:25 schrieb Florian Weimer <fweimer@redhat.com>:
>
> On 05/29/2018 11:21 AM, Andreas Hubert wrote:
>> I’d like to build glibc under a CentOS to be packed in a RPM and a different root dir.
>> But currently I have problems with my build and hope someone can help me.
>
> I regularly build upstream glibc with DTS 7 and have not seen anything like this. How do you invoke configure and make?
>
> Thanks,
> Florian
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2018-05-29 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 9:21 Andreas Hubert
2018-05-29 11:25 ` Florian Weimer
2018-05-29 12:05 ` Andreas Hubert [this message]
2018-06-01 10:45 ` Andreas Hubert
2018-06-01 11:33 ` Florian Weimer
2018-06-01 11:38 ` Andreas Hubert
2018-06-01 11:43 ` Florian Weimer
2018-06-01 13:54 ` Andreas Hubert
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=8B580C00-0D93-4DB3-990F-9E7EAA734358@googlemail.com \
--to=anhubert@googlemail.com \
--cc=fweimer@redhat.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).