On 10314 March 1977, Mark Nipper wrote:
> Am I just crazy or did all of the archives die recently?
> I've tried amd64.debian.net, debian.csail.mit.edu and
> ftp.de.debian.org and all of their dists directories appear to be
> empty for each of the various amd64 distributi
On (08/06/05 10:09), Mark Nipper wrote:
> Am I just crazy or did all of the archives die recently?
> I've tried amd64.debian.net, debian.csail.mit.edu and
> ftp.de.debian.org and all of their dists directories appear to be
> empty for each of the various amd64 distributi
On Wed, Jun 08, 2005 at 10:09:23AM -0500, Mark Nipper wrote:
> Am I just crazy or did all of the archives die recently?
> I've tried amd64.debian.net, debian.csail.mit.edu and
> ftp.de.debian.org and all of their dists directories appear to be
> empty for each of
Am I just crazy or did all of the archives die recently?
I've tried amd64.debian.net, debian.csail.mit.edu and
ftp.de.debian.org and all of their dists directories appear to be
empty for each of the various amd64 distributions. apt-get and
dselect are very unhappy of course. And I
Thanks. Until it's fixed by the maintainer, I made my own version of
the package which builds and installs libiberty.so. It's a bit of a
hack, but I can submit the patch if it helps.
d
On Tue, 14 Dec 2004 00:41:40 +0100, Goswin von Brederlow
<[EMAIL PROTECTED]> wrote:
>
>
> Drew Hess <[EMAI
Drew Hess <[EMAIL PROTECTED]> writes:
> There aren't any Debian policy violations that I'm aware of... but I
> would like to use libiberty in my own shared library, and I can't on
> debian-amd64.
>
> I have followed up on a binutils bug that was submitted 2 years ago
> re: lack of shared libiberty
There aren't any Debian policy violations that I'm aware of... but I
would like to use libiberty in my own shared library, and I can't on
debian-amd64.
I have followed up on a binutils bug that was submitted 2 years ago
re: lack of shared libiberty on other archs, but I'm hoping that
raising this
Drew Hess <[EMAIL PROTECTED]> writes:
> binutils-dev only supplies a static archive for libiberty. On AMD64,
> this means that you can't use libiberty functions in shared libraries,
> because libiberty.a isn't compiled with -fPIC.
>
> Seems to me that all library packages on AMD64 should come wit
binutils-dev only supplies a static archive for libiberty. On AMD64,
this means that you can't use libiberty functions in shared libraries,
because libiberty.a isn't compiled with -fPIC.
Seems to me that all library packages on AMD64 should come with shared libs.
d
9 matches
Mail list logo
