public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Damian Ivanov <damianatorrpm@gmail.com>
To: libffi-discuss@sourceware.org
Subject: Re: libffi pkgconfig
Date: Mon, 07 Feb 2011 15:41:00 -0000	[thread overview]
Message-ID: <AANLkTin=tgg6uxa6dsKP7C7OZXhdecBzxTTYgtKn3OJx@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimef9KnmHAbSLe1eNN8wKJiBM2uHJzTXFNPjEPJ@mail.gmail.com>

Yeah, they marked my bug already as WONTFIX.

2011/2/7 Damian Ivanov <damianatorrpm@gmail.com>:
> 2011/2/7 Damian Ivanov <damianatorrpm@gmail.com>:
>> Yeah, they marked my bug already as WONTFIX.
>>
>> 2011/2/7 Anthony Green <green@redhat.com>:
>>> Damian Ivanov <damianatorrpm@gmail.com> writes:
>>>
>>>> Ok it has been a while but I have one more question to that :)
>>>> Can someone have a look at
>>>> https://bugzilla.novell.com/show_bug.cgi?id=657789 and tell me if this
>>>> is the same libffi :D In openSUSE the libffi has a version number
>>>> above 4,
>>>
>>> Somebody is building this from the GCC sources and packaging it up.  I
>>> don't recommend this.  I think you are on the right track with this:
>>>
>>> https://bugzilla.novell.com/show_bug.cgi?id=669804
>>>
>>> AG
>>>
>>>
>>>
>>>> that does not contain libffi.pc (or did not before, because
>>>> of my bug report they added a file manually for that). In the build
>>>> service like I menitioned in the bug report I found a libffi that is
>>>> the right one (3.0.9) with libffi.pc included.
>>>>
>>>> Best regards,
>>>> Damian
>>>>
>>>> 2010/12/10 Anthony Green <green@redhat.com>:
>>>>> Damian Ivanov <damianatorrpm@gmail.com> writes:
>>>>>
>>>>>> Hi there,
>>>>>>
>>>>>> I have a problem compiling wayland, the NG display server on openSUSE
>>>>>> 11.4. The build process fails with the missing libffi message, still
>>>>>> libffi-devel and libffi are installed, but there is no libffi.pc (for
>>>>>> pkgconfig) file included.
>>>>>> I've filed a bug report for that at
>>>>>> https://bugzilla.novell.com/show_bug.cgi?id=657789 . Should the distro
>>>>>> include/generate the .pc file or could you include it?
>>>>>
>>>>> libffi.pc comes with libffi and will get installed with make install.
>>>>> It should be part of their libffi-devel package.
>>>>>
>>>>> AG
>>>>>
>>>
>>
>

  reply	other threads:[~2011-02-07 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 13:08 Damian Ivanov
2010-12-10 13:58 ` Anthony Green
2011-02-06 18:33   ` Damian Ivanov
2011-02-06 18:42     ` Samuli Suominen
2011-02-08  9:44       ` Andrew Haley
2011-02-07 11:57     ` Anthony Green
     [not found]       ` <AANLkTikhKTh9NLFzrbw1=mLJjcJj9ZOtV09iBvHgaugq@mail.gmail.com>
2011-02-07 15:37         ` Damian Ivanov
2011-02-07 15:41           ` Damian Ivanov [this message]
     [not found]         ` <m3pqr3u99j.fsf@redhat.com>
2011-02-07 16:36           ` Damian Ivanov

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='AANLkTin=tgg6uxa6dsKP7C7OZXhdecBzxTTYgtKn3OJx@mail.gmail.com' \
    --to=damianatorrpm@gmail.com \
    --cc=libffi-discuss@sourceware.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).