* Re: undefined ffi_type_pointer problem mipsel linux [not found] <7276900f.5f2e.134177f887f.Coremail.byweinno@163.com> @ 2011-12-07 10:54 ` Anthony Green 2011-12-07 20:18 ` bug#10241: " Andy Wingo [not found] ` <11e8df07.6762.134179f0d3b.Coremail.byweinno@163.com> 1 sibling, 1 reply; 3+ messages in thread From: Anthony Green @ 2011-12-07 10:54 UTC (permalink / raw) To: ɺɺ; +Cc: libffi-discuss, bug-guile 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; > > > > ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bug#10241: undefined ffi_type_pointer problem mipsel linux 2011-12-07 10:54 ` undefined ffi_type_pointer problem mipsel linux Anthony Green @ 2011-12-07 20:18 ` Andy Wingo 0 siblings, 0 replies; 3+ messages in thread From: Andy Wingo @ 2011-12-07 20:18 UTC (permalink / raw) To: Anthony Green; +Cc: ɺɺ, 10241-done, libffi-discuss 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/ ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <11e8df07.6762.134179f0d3b.Coremail.byweinno@163.com>]
* Re: bug#10241: undefined ffi_type_pointer problem mipsel linux [not found] ` <11e8df07.6762.134179f0d3b.Coremail.byweinno@163.com> @ 2011-12-07 20:18 ` Mark H Weaver 0 siblings, 0 replies; 3+ messages in thread From: Mark H Weaver @ 2011-12-07 20:18 UTC (permalink / raw) To: 珊珊; +Cc: 10241, green, libffi-discuss Can you please run "make V=1" so that we can see the complete command used in the failing link (CCLD guile) command? As Anthony Green said, it appears that libffi was not linked. I can think of a few possible reasons: * Did you forget to run "ldconfig" after installing libffi? * Was libffi present when you last ran Guile's configure? * Is there a problem with pkg-config on your system? (What is the output of "pkg-config --libs libffi"?) Thanks, Mark ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-12-07 20:18 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <7276900f.5f2e.134177f887f.Coremail.byweinno@163.com> 2011-12-07 10:54 ` undefined ffi_type_pointer problem mipsel linux Anthony Green 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
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).