public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Samuli Suominen <ssuominen@gentoo.org>
Cc: libffi-discuss@sourceware.org
Subject: Re: souurce for old version of libffi
Date: Mon, 29 Oct 2012 11:40:00 -0000	[thread overview]
Message-ID: <508E6B13.20904@redhat.com> (raw)
In-Reply-To: <508E68C0.8080804@gentoo.org>

On 10/29/2012 11:30 AM, Samuli Suominen wrote:
> On 29/10/12 12:21, Andrew Haley wrote:
>> On 10/28/2012 12:50 AM, tim.beech wrote:
>>> I'm packaging GHC (Glasgow Haskell Compiler) for Salix, a Slackware
>>> derivative, and it depends on old versions of libgmp and libffi.
>>>
>>> Specificaly, it is looking for /usr/lib/libffi.so.3
>>> and finding libffi.so.6
>>>
>>> These numbers don't seem to correspond to the version numbers for
>>> libffi; as far as I know, the latest libffi for Slackware is
>>> libffi-3.something.
>>>
>>> I've searched without success. I'd be extremely grateful if anyone could
>>> point me in the direction of a tarball.
>>
>> Please, don't do this.  Let's fix GHC.  I may be able to help.
> 
> I believe this is the link you are looking for:
> 
> http://hackage.haskell.org/trac/ghc/ticket/5743
> http://bugs.gentoo.org/show_bug.cgi?id=411925 (downstream bug linking to 
> the above bug)

Yes, that looks like it.  AFAIK most distros won't allow packages to
bundle magic library versions anyway.

> The problem was that the bundled libffi conflicted with the system 
> libffi, as in, both got picked up one way or another

Yes, I see.

Andrew.


      reply	other threads:[~2012-10-29 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 23:50 tim.beech
2012-10-28 13:31 ` Tim Beech
2012-10-29 10:21 ` Andrew Haley
2012-10-29 11:34   ` Samuli Suominen
2012-10-29 11:40     ` Andrew Haley [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=508E6B13.20904@redhat.com \
    --to=aph@redhat.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=ssuominen@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).