public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: elfutils build error
Date: Fri, 26 Feb 2016 20:51:49 +0100	[thread overview]
Message-ID: <1456516309.7770.187.camel@redhat.com> (raw)
In-Reply-To: CADieKzv88qG8=O3LHp0Q=KFKOPqZ5_=qMmMOgDTO7DXHR91nGg@mail.gmail.com

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

On Fri, 2016-02-26 at 19:45 +0100, phi gcc wrote:
> I grabbed the elfutils-0.165.tar.bz2
> CU82$ tar xf elfutils-0.165.tar.bz2
> CU82$ cd elfutils-0.165
> CU82$ configure
> ...
> =====================================================================
>         elfutils: 0.165 (eu_version: 165)
> =====================================================================
> 
>     Prefix                             : /usr/local
>     Program prefix ("eu-" recommended) : NONE
>     Source code location               : .
>     Maintainer mode                    :
>     libebl modules subdirectory        : elfutils
>     build arch                         : x86_64-unknown-linux-gnu
> 
>   RECOMMENDED FEATURES (should all be yes)
>     gzip support                       : yes
>     bzip2 support                      : yes
>     lzma/xz support                    : yes
>     libstdc++ demangle support         : yes
>     File textrel check                 : yes
>     Symbol versioning                  : yes
> 
>   NOT RECOMMENDED FEATURES (should all be no)
>     Experimental thread safety         : no
> 
>   OTHER FEATURES
>     Deterministic archives by default  : false
>     Native language support            : yes
> 
>   EXTRA TEST FEATURES (used with make check)
>     have bunzip2 installed (required)  : yes
>     debug branch prediction            : no
>     gprof support                      : no
>     gcov support                       : no
>     run all tests under valgrind       : no
>     gcc undefined behaviour sanitizer  : no
>     use rpath in tests                 : no
>     test biarch                        : no
> 
> 
> CU82$ make
> make --no-print-directory all-recursive
> Making all in config
> ...
> 
> ldgeneric.o: In function `ld_generic_open_outfile':
> /home/phi/elfutils-0.165/src/ldgeneric.c:2669: warning: the use of `mktemp' is d
> angerous, better use `mkstemp' or `mkdtemp'
>   CC       elflint.o
>   CCLD     elflint
> ./ld: unrecognized option '--sysroot=/'
> Try `ld --help' or `ld --usage' for more information.
> collect2: error: ld returned 64 exit status
> make[2]: *** [elflint] Error 1
> rm i386_ld.o
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> ========================
> 
> Am I doing something obviously wrong ?

I think what is happening is that you have "." (the current directory)
in your PATH. So when the build is in src/ it picks up the just build
src/ld program. Which isn't really ready, and doesn't understand
--sysroot. Best to remove "." from your PATH.

Cheers,

Mark

             reply	other threads:[~2016-02-26 19:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 19:51 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-02 14:20 Mark Wielaard
2016-02-28  8:56 phi gcc
2016-02-28  7:40 phi gcc
2016-02-26 21:31 phi gcc
2016-02-26 21:04 phi gcc
2016-02-26 20:16 Mark Wielaard
2016-02-26 20:11 phi gcc
2016-02-26 20:09 phi gcc
2016-02-26 18:45 phi gcc

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=1456516309.7770.187.camel@redhat.com \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.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).