public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
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: Fri, 01 Jun 2018 13:54:00 -0000	[thread overview]
Message-ID: <37524AAC-FFE3-4254-B1CE-FC64CA4727E8@googlemail.com> (raw)
In-Reply-To: <2b24fce5-9b5c-1edd-eb30-3448a5894657@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]

The commands I provided where the exact ones, just double dash is garbled by my mail client: — vs --
But I think I found now the reason. Since you claimed you always compile like that and never had issues, I tried with a vagrant virtual box on centos and it worked without any problem and also way faster.

The problem I had was because I was running the build in docker container on MacOS inside a mounted volume.
So I will try to first copy my base directory inside the docker container to build it there and then copy back the resulting files and if this still fails I have to check how I could run my builds on a VM directly instead of docker.

Thanks for your hints which took me to the conclusion that something with my environment must be wrong.

> Am 01.06.2018 um 13:43 schrieb Florian Weimer <fweimer@redhat.com>:
> 
> On 06/01/2018 01:38 PM, Andreas Hubert wrote:
>> My goal is to pack this in a RPM, but currently I just try to build it directly on the command line. Only after that works my next step would be to make it work with a spec file.
> 
> In this case, please show us the *exact* commands you use, not garbled by your mail client.  This includes the SCL activation step.
> 
>> Maybe I have something wrong with my DTS 7 setup.. do you maybe have any sources you follow to setup you build environment that I could try to follow?
> 
> I install devtoolset-7-gcc and devtoolset-7-gcc-c++, and the configure glibc with:
> 
> ../git/configure --prefix=/usr CC=/opt/rh/devtoolset-7/root/usr/bin/gcc CXX=/opt/rh/devtoolset-7/root/usr/bin/g++
> make -j4
> 
> Alternatively, running
> 
> scl enable devtoolset-7 -- bash
> 
> and entering
> 
> ../git/configure --prefix=/usr
> make -j4
> 
> in the subshell (!) works as well.
> 
> Thanks,
> Florian


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]

      reply	other threads:[~2018-06-01 13:54 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
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 [this message]

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=37524AAC-FFE3-4254-B1CE-FC64CA4727E8@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).