dwarves.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florin Iucha <florin-zX39fKdjKLBeoWH0uzbU5w@public.gmane.org>
To: Arnaldo Carvalho de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: building pahole on Ubuntu 8.04 AMD64
Date: Thu, 20 Mar 2008 16:48:29 -0500	[thread overview]
Message-ID: <20080320214829.GV3247@iris.iucha.org> (raw)
In-Reply-To: <20080320205109.GE4034-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>

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

On Thu, Mar 20, 2008 at 05:51:09PM -0300, Arnaldo Carvalho de Melo wrote:
> > I'm trying to build the pahole tools on Ubuntu 8.04 AMD64 and I'm
> > getting a build error:
> > 
> > $ make
> > [  5%] Building C object CMakeFiles/dwarves.dir/dwarves.o
> > [ 11%] Building C object CMakeFiles/dwarves.dir/ctf_loader.o
> > [ 17%] Building C object CMakeFiles/dwarves.dir/libctf.o
> > [ 23%] Building C object CMakeFiles/dwarves.dir/dwarf_loader.o
> > Linking C shared library libdwarves.so
> > /usr/bin/ld:
> > /usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib64/libdw.a(dwarf_begin.o):
> > relocation R_X86_64_32 against `a local symbol' can not be used when
> > making a shared object; recompile with -fPIC
> > /usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib64/libdw.a: could
> > not read symbols: Bad value
> > collect2: ld returned 1 exit status
> > make[2]: *** [libdwarves.so.1.0.0] Error 1
> > make[1]: *** [CMakeFiles/dwarves.dir/all] Error 2
> > make: *** [all] Error 2
> > 
> > I grepped for -fPIC and it seems to be passed on the command line for
> > many of the sources.  I'm using libdw-dev version 0.131-3 and binutils
> > 2.18.1~cvs20080103-0uubuntu1 as packaged by Ubuntu.
> 
> Strange, looks like you have libdw-dev 32bits installed? can you check
> that? I.e. that cmake is not mixing somehow libraries?
> 
> Also I'm adding dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org to the CC list, you don't have to
> subscribe, but it would be a good idea, there are more people there that
> I know have built this code on ubuntu/debian and that could be of more
> help than me, that use debian rarely :-\

$ ar x /usr/lib/libdw.a
$ ls | head -10
$ file dwarf_addrdie.o
dwarf_addrdie.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped

As I said in the other e-mail (private to Arnaldo), I could build
pahole & friends by compiling the individual files, then feeding them
together with the static libraries to the linker.  So that would indicate
the libraries and toolchain are fine, but maybe they don't provide all
the things that the build system expects.

Cheers,
florin

-- 
Bruce Schneier expects the Spanish Inquisition.
      http://geekz.co.uk/schneierfacts/fact/163

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2008-03-20 21:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080320200244.GS3247@iris.iucha.org>
     [not found] ` <20080320200244.GS3247-8+3tsXFunua1C7ntjtBYng@public.gmane.org>
2008-03-20 20:51   ` building pahole on Ubuntu 8.04 AMD64 Arnaldo Carvalho de Melo
     [not found]     ` <20080320205109.GE4034-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2008-03-20 21:03       ` Thomas Girard
2008-03-20 21:48       ` Florin Iucha [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=20080320214829.GV3247@iris.iucha.org \
    --to=florin-zx39fkdjklbeowh0uzbu5w@public.gmane.org \
    --cc=acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 NNTP newsgroup(s).