From: Andy Wingo <wingo@pobox.com>
To: Anthony Green <green@moxielogic.com>
Cc: ɺɺ <byweinno@163.com>,
10241-done@debbugs.gnu.org, libffi-discuss@sourceware.org
Subject: Re: bug#10241: undefined ffi_type_pointer problem mipsel linux
Date: Wed, 07 Dec 2011 20:18:00 -0000 [thread overview]
Message-ID: <87pqg0kufv.fsf@pobox.com> (raw)
In-Reply-To: <4EDF45D6.5000302@moxielogic.com> (Anthony Green's message of "Wed, 07 Dec 2011 05:54:14 -0500")
On Wed 07 Dec 2011 11:54, Anthony Green <green@moxielogic.com> writes:
> On 12/7/2011 2:49 AM, ɺɺ wrote:
>> Dear Mr. Green :
>>
>> My box is fuloong 6004, loongson2f cpu, mips64, little endian, more
>> info see
>> http://www.linux-mips.org/wiki/Loongson#Loongson_2F
>>
>> Here I want install autogen, then needs guile dependency, guile needs
>> libffi, when I install libffi, afterthat I install guile, problem is
>> that undefined ffi_type_pointer, I try to several methods, it still
>> can be ok. I checked the ffi.h is extern, shall I defined the use
>> #define for each one ?
>
>
> This just looks like libffi isn't being linked to guile at all. Can you
> verify that libffi was actually built and installed in the right place?
> Next, I would see what "CCLD guile" is really doing. I'm not sure how
> guile is built these days, but maybe you just have to add V=1 to the
> "make" command line.
Indeed. Libffi certainly builds on mipsel machines, as does Guile, so I
suspect this is an error configuring Guile. Perhaps you needed to set
PKG_CONFIG_PATH, ɺɺ?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-12-07 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7276900f.5f2e.134177f887f.Coremail.byweinno@163.com>
2011-12-07 10:54 ` Anthony Green
2011-12-07 20:18 ` Andy Wingo [this message]
[not found] ` <11e8df07.6762.134179f0d3b.Coremail.byweinno@163.com>
2011-12-07 20:18 ` bug#10241: " Mark H Weaver
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=87pqg0kufv.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10241-done@debbugs.gnu.org \
--cc=byweinno@163.com \
--cc=green@moxielogic.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).