public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "knappr2 at earthlink dot net" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/23977] make check fails run-ar.sh in versions 0.173-0.175
Date: Wed, 12 Dec 2018 21:25:00 -0000	[thread overview]
Message-ID: <bug-23977-10460-oaRw6Kumrw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23977-10460@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Rashawn <knappr2 at earthlink dot net> ---
(In reply to Mark Wielaard from comment #3)
> Comment on attachment 11451 [details]
> test-suite.log
> 
> It looks like the file we want to put into the ar has a numeric uid that
> cannot be represented in the ar header. I am not sure yet how that could
> happen.
> 
> Does it work if you do the build and run the test not on an nfs file system?

Hello Mark and others,

I did build onto the machine's local file system and encountered the same
error. I then went back and read through all of the configure options listed
via ./configure --help. I notice, in addition to --prefix, the
--enable-deterministic-archives might be worth trying as it is the only option
which mentions anything about archives, and based on the binutils description
of -D regarding setting uid and guids to zero it made sense because the make
check error complained about ar_uid. This worked, and I was able to install the
latest version 0.175 into the NFS allocation as originally planned. 

My configure line using GCC 8.0.2 ended up like this: ./configure
--prefix=$eupref --enable-deterministic-archives CC=gcc 2>&1 | tee
../build-out-files/2018_1212_elfutils-0.175_gcc-8.2.0_configure-01.out.

Thank you for your input and advice. I am happy to have this solved.

Regards,

-Rashawn

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

  parent reply	other threads:[~2018-12-12 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 18:59 [Bug general/23977] New: " knappr2 at earthlink dot net
2018-12-11 19:12 ` [Bug general/23977] " mark at klomp dot org
2018-12-11 20:31 ` knappr2 at earthlink dot net
2018-12-11 23:35 ` mark at klomp dot org
2018-12-12 21:25 ` knappr2 at earthlink dot net [this message]
2018-12-25 13:20 ` mark at klomp 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-23977-10460-oaRw6Kumrw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@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).