From: Anthony Green <green@moxielogic.com>
To: ɺɺ <byweinno@163.com>
Cc: libffi-discuss@sourceware.org, bug-guile@gnu.org
Subject: Re: undefined ffi_type_pointer problem mipsel linux
Date: Wed, 07 Dec 2011 10:54:00 -0000 [thread overview]
Message-ID: <4EDF45D6.5000302@moxielogic.com> (raw)
In-Reply-To: <7276900f.5f2e.134177f887f.Coremail.byweinno@163.com>
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.
AG
>
> Thanks
>
> bo cheng
>
>
>
> CCLD guile
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_pointer'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_float'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_void'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_sint64'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_prep_cif'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_uint32'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_double'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_prep_closure_loc'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_call'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_sint8'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_closure_free'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_closure_alloc'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_uint8'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_sint32'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_uint16'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_sint16'
> ./.libs/libguile-2.0.so: undefined reference to `ffi_type_uint64'
> collect2: ld returned 1 exit status
> make[3]: *** [guile] Error 1
> make[3]: Leaving directory `/root/soft/guile-2.0.3/libguile'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/root/soft/guile-2.0.3/libguile'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/
>
>
> Theres is in ffi.h
>
>
> /* These are defined in types.c */
> extern ffi_type ffi_type_void;
> extern ffi_type ffi_type_uint8;
> extern ffi_type ffi_type_sint8;
> extern ffi_type ffi_type_uint16;
> extern ffi_type ffi_type_sint16;
> extern ffi_type ffi_type_uint32;
> extern ffi_type ffi_type_sint32;
> extern ffi_type ffi_type_uint64;
> extern ffi_type ffi_type_sint64;
> extern ffi_type ffi_type_float;
> extern ffi_type ffi_type_double;
> extern ffi_type ffi_type_pointer;
>
>
>
>
next parent reply other threads:[~2011-12-07 10:54 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 [this message]
2011-12-07 20:18 ` bug#10241: " Andy Wingo
[not found] ` <11e8df07.6762.134179f0d3b.Coremail.byweinno@163.com>
2011-12-07 20:18 ` 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=4EDF45D6.5000302@moxielogic.com \
--to=green@moxielogic.com \
--cc=bug-guile@gnu.org \
--cc=byweinno@163.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).