public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] DDD + libiberty binutils
Date: 07 Jul 2002 00:01:07 +0200	[thread overview]
Message-ID: <1025992871.16128.6.camel@nosferatu.lan> (raw)
In-Reply-To: <3D27344D.5090605@seul.org>

On Sat, 2002-07-06 at 20:17, Marko Mikulicic wrote:
> Hello,
> 
> DDD 3.3.1 fails to merge because it needs to install its own version of 
> libiberty which defines the function "xstrerror".
>   binutils-2.11.92.0.12.3-r2 doesn't define this function and ddd's 
> configure script enables the build of its own.
>   There are two problems:
> 
> 1) bug 4614: sandbox problem. DDD installs direclty in /usr/lib/libiberty.a
> 
> 2) since /usr/lib/libiberty.a is owned by binutils, I don't think it's	
>   a good idea to overwrite it. Also since it's a static lib, I don't
> see any reason to install it
> 

Nop.

>   question: does the build system of DDD need to be tweaked ?
>   Should the DDD team be informed of this ?
> 

Maybe ad a "LDPATH=${S}/path_to_own_libiberty" in the call to make ?

> 3) perhaps the masked binutils-2.12.xx package has this function.
>   in this case the ddd.ebuild should have the correct dependecy.
> 
> 

nosferatu root # epm -q binutils
binutils-2.12.90.0.7
nosferatu root # 

nosferatu root # grep xstrerror /usr/lib/libiberty.a 
Binary file /usr/lib/libiberty.a matches
nosferatu root # 



-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa




      reply	other threads:[~2002-07-06 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06 18:17 [gentoo-dev] DDD + libiberty binutils Marko Mikulicic
2002-07-06 22:01 ` Martin Schlemmer [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=1025992871.16128.6.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@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