From: "Whitlock, Bradley D" <bradley.d.whitlock@lmco.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: RE: EXTERNAL: Re: ERROR: file: "libguilereadline-v-17", message: "The specified module could not be found"
Date: Thu, 13 Jan 2011 12:13:21 -0500 [thread overview]
Message-ID: <D6D90A401251394A86F1F98B1E2B68421691CC505A@HVXMSP8.us.lmco.com> (raw)
In-Reply-To: <87sjwz720r.fsf@gnu.org>
Ludo,
I re-ran 'make' and got some warnings that I had not noticed before:
make all-recursive
make[3]: Entering directory `/c/home/guile-1.8.8/build/guile-readline'
Making all in ice-9
make[4]: Entering directory `/c/home/guile-1.8.8/build/guile-readline/ice-9'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/c/home/guile-1.8.8/build/guile-readline/ice-9'
make[4]: Entering directory `/c/home/guile-1.8.8/build/guile-readline'
/bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DSCM_IMPORT -I.
-I../../guile-readline -I. -I.. -I../../guile-readline/.. -g -O2 -MT readlin
e.lo -MD -MP -MF .deps/readline.Tpo -c -o readline.lo ../../guile-readline/readl
ine.c
libtool: compile: gcc -DHAVE_CONFIG_H -DSCM_IMPORT -I. -I../../guile-readline -
I. -I.. -I../../guile-readline/.. -g -O2 -MT readline.lo -MD -MP -MF .deps/readl
ine.Tpo -c ../../guile-readline/readline.c -DDLL_EXPORT -DPIC -o .libs/readline
.o
mv -f .deps/readline.Tpo .deps/readline.Plo
/bin/sh ./libtool --tag=CC --mode=link gcc -g -O2 -version-info 17:3:0 -expor
t-dynamic -no-undefined -o libguilereadline-v-17.la -rpath /usr/local/lib readl
ine.lo ../libguile/libguile.la -lreadline -ltermcap
*** Warning: linker path does not have real file for library -ltermcap.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libtermcap and none of the candidates passed a file format test
*** using a file magic. Last file checked: /usr/local/lib/libtermcap.a
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.
*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
libtool: link: ar cru .libs/libguilereadline-v-17.a .libs/readline.o
libtool: link: ranlib .libs/libguilereadline-v-17.a
libtool: link: ( cd ".libs" && rm -f "libguilereadline-v-17.la" && cp -p "../lib
guilereadline-v-17.la" "libguilereadline-v-17.la" )
So it looks like the dll version of libguilereadline-v-17 is not building because I don't have a dll of libtermcap (but I do have static version). Not sure how to get a dll termcap because the package seems really simple, I don't even think it recognizes --enable-shared option.
Here is the config output for termcap-1.3.1:
$ ../configure --disable-static --enable-shared --prefix=/usr/local
creating cache ./config.cache
checking for gcc... gcc
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for ranlib... ranlib
checking for a BSD compatible install... /bin/install -c
checking how to run the C preprocessor... gcc -E
checking for string.h... yes
checking for unistd.h... yes
checking whether cross-compiling... no
checking for ANSI C header files... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
$ make
gcc -c -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DTERMCAP_FILE=\"/
etc/termcap\" -I. -I.. -g ../termcap.c
gcc -c -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DTERMCAP_FILE=\"/
etc/termcap\" -I. -I.. -g ../tparam.c
gcc -c -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DTERMCAP_FILE=\"/
etc/termcap\" -I. -I.. -g ../version.c
ar rc libtermcap.a termcap.o tparam.o version.o
ranlib libtermcap.a
Definitely not building dll version...How do I get dll of termcap?
-Thanks
Brad
-----Original Message-----
From: Ludovic Courtès [mailto:ludo@gnu.org]
Sent: Tuesday, January 11, 2011 11:02 AM
To: Whitlock, Bradley D
Subject: EXTERNAL: Re: ERROR: file: "libguilereadline-v-17", message: "The specified module could not be found"
Hi,
"Whitlock, Bradley D" <bradley.d.whitlock@lmco.com> writes:
> It seems to me that the guile readline dll is not being built. I built guile as follows:
>
> cp /c/MinGW/lib/libws2_32.a /usr/local/lib
> ../configure -C --disable-static --enable-shared --prefix=/usr/local && make install
>
> Shouldn't there be a libguilereadline-v-17.dll.a in /usr/local/lib rather than libguilereadline-v-17.a ?
It could be that ‘configure’, or even ‘libtool --mode=link’, determined
that it can’t build shared libraries for some reason.
Can you grep ‘config.log’ for “shared” and also check the whole build
log for Libtool warnings?
Thanks,
Ludo’.
next parent reply other threads:[~2011-01-13 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D6D90A401251394A86F1F98B1E2B68421691C339DC@HVXMSP8.us.lmco.com>
[not found] ` <87sjwz720r.fsf@gnu.org>
2011-01-13 17:13 ` Whitlock, Bradley D [this message]
2011-01-13 17:38 ` EXTERNAL: Re: ERROR: file: "libguilereadline-v-17", message: "The specified module could not be found" Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D6D90A401251394A86F1F98B1E2B68421691CC505A@HVXMSP8.us.lmco.com \
--to=bradley.d.whitlock@lmco.com \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.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).