public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Maxim Koltsov <maksbotan@gentoo.org>
Cc: binutils@sourceware.org
Subject: Re: GNU Binutils on OpeBSD
Date: Sun, 24 Apr 2011 19:28:00 -0000	[thread overview]
Message-ID: <BANLkTik_rQAHa9qNz1x0mm=SreMERXrpVQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimp4xDT9AEva878gKefZJfD4QToYA@mail.gmail.com>

On Sun, Apr 24, 2011 at 2:41 PM, Maxim Koltsov wrote:
> I'm building binutils on OpenBSD 4.8. I've ported OpenBSD's binutils
> patch to binutils-2.21, so bfd is aware of openbsd now. But i get very
> strange error with --enable-shared: libopcodes.so has DT_NEEDED
> pointing to libbfd.so in temporaly location:
>   NEEDED      /home/maksbotan/gentoo/var/tmp/portage/sys-devel/binutils-2.21/work/build/opcodes/../bfd/.libs/libbfd.so
> Of course, this cannot be found, and tools like as and objdump cannot
> work. And when compiling binutils on linux, libopcodes.so has only
> 'libbfd-2.21.so' in DT_NEEDED. Can you figure out what problem is
> cause by? My patch is attached.

pretty sure this isnt a bug.  you probably need to `make install` first.
-mike

  reply	other threads:[~2011-04-24 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 18:41 Maxim Koltsov
2011-04-24 19:28 ` Mike Frysinger [this message]
     [not found]   ` <BANLkTinY2uodMryK3aFB7Zh7etwuOh5M-A@mail.gmail.com>
2011-04-24 20:56     ` Mike Frysinger
     [not found]       ` <BANLkTim8CDtJO7vrKq--dfJipTBU69Po8w@mail.gmail.com>
     [not found]         ` <BANLkTikqs7ghsJ63PKLKHiAx38PE0QMRfw@mail.gmail.com>
2011-04-25  4:47           ` Maxim Koltsov
2011-04-25  5:06             ` Mike Frysinger
2011-04-25 11:35               ` Maxim Koltsov
2011-04-25 12:42                 ` Alan Modra
2011-04-25 12:50                   ` Максим Кольцов

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='BANLkTik_rQAHa9qNz1x0mm=SreMERXrpVQ@mail.gmail.com' \
    --to=vapier@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=maksbotan@gentoo.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).