unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: primus <rprimus@gmail.com>
To: bug-guile@gnu.org
Subject: Re: [1.9.12][OpenBSD] run time failure ...
Date: Fri, 10 Sep 2010 16:44:56 +0100	[thread overview]
Message-ID: <20100910154456.GH18170@x.lence.net> (raw)
In-Reply-To: <m38w39fyz4.fsf@unquote.localdomain>

On Fri, Sep 10, 2010 at 04:35:27PM +0200, Andy Wingo wrote:
> >
> > Nowhere do I specify that it should be a
> > static-only build.
> 
> It's statically linking libguile to guile. You sure you didn't pass
> --disable-shared on the configure line? Surely libtool can make shared
> libraries on openbsd?

Fri Sep 10 16:25:23 BST 2010

configure was run as:

env CFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure  2>&1 | tee <logfile>

# grep -A1 -i shared config.log
configure:9187: checking for shared library run path origin
configure:9200: result: done
configure:24931: checking whether the gcc -std=gnu99 linker (/usr/bin/ld) supports shared libraries
configure:25917: result: yes
configure:25977: gcc -std=gnu99 -shared  -fPIC -DPIC -o conftest conftest.o  -v 2\>\&1 \| /usr/bin/grep  -lc  \>/dev/null 2\>\&1
configure:25980: $? = 1
configure:27494: checking if libtool supports shared libraries
configure:27496: result: yes
configure:27499: checking whether to build shared libraries
configure:27520: result: yes
sharedstatedir='${prefix}/com'
sitedir='${datarootdir}/guile/site/2.0'

> 
> > # ldd ./libguile/guile
> > ./libguile/guile:
> >         Start    End      Type Open Ref GrpRef Name
> >         1c000000 3c042000 exe  1    0   0      ./libguile/guile
> [...]
> 
> Here guile should probably be a libtool helper script, and
> libguile/.libs/lt-guile should link to libguile-2.0.so.

# pwd
/usr/obj/micro/guile-1.9.12
# find . -name "*.so*" -print
# find . -name "*lt-guile*" -print
#

From logfile *.l6g:

posix.c:1844:5: warning: "HAVE_CUSERID" is not defined
  CC     net_db.lo
  CC     socket.lo
  CC     regex-posix.lo
  CCLD   libguile-2.0.la

*** Warning: linker path does not have real file for library -lm.
*** 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 libm and none of the candidates passed a file format test
*** using a regex pattern. Last file checked: /usr/local/lib/libiconv.so.4.0
*** 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.
  CC     guile-guile.o
  CCLD   guile
/usr/local/lib/libgmp.so.8.0: warning: vsprintf() is often misused, please use vsnprintf()
./.libs/libguile-2.0.a(posix.o)(.text+0x253f): In function `scm_tmpnam':
/usr/obj/micro/guile-1.9.12/libguile/posix.c:1317: warning: tmpnam() possibly used unsafely; consider using mkstemp()
./.libs/libguile-2.0.a(libguile_2.0_la-load.o)(.text+0x9df): In function `stringbuf_cat':
/usr/obj/micro/guile-1.9.12/libguile/load.c:378: warning: strcpy() is almost always misused, please use strlcpy()
./.libs/libguile-2.0.a(libguile_2.0_la-bytevectors.o)(.text+0x1982): In function `scm_utf32_to_string':
/usr/obj/micro/guile-1.9.12/libguile/bytevectors.c:1888: warning: strcat() is almost always misused, please use strlcat()
./.libs/libguile-2.0.a(libguile_2.0_la-srfi-14.o)(.text+0x463): In function `scm_sys_char_set_dump':
/usr/obj/micro/guile-1.9.12/libguile/srfi-14.c:2047: warning: sprintf() is often misused, please use snprintf()
  GEN    c-tokenize.o
  GEN    guile_filter_doc_snarfage

2nd paragraph:
	*** libtool will only create a static version of it.

What 'it' is being referred to?

The above message appears to be generated by:
	./build-aux/ltmain.sh

Reading through that now.

-- 
-primus
"If I had more time, I would have written you a shorter letter" - Pascal
"It isn't what you make, it's what you don't lose!"



  reply	other threads:[~2010-09-10 15:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 19:21 [1.9.12][OpenBSD] run time failure primus
2010-09-08 19:46 ` Andy Wingo
2010-09-08 20:07   ` primus
2010-09-08 21:58     ` Ludovic Courtès
2010-09-08 22:12   ` primus
2010-09-10  8:39     ` Andy Wingo
2010-09-10 13:47       ` primus
2010-09-10 14:35         ` Andy Wingo
2010-09-10 15:44           ` primus [this message]
2010-09-10 21:37             ` Ludovic Courtès
2010-09-10 16:44           ` [1.9.12][OpenBSD] [SOLUTION] " primus
2010-09-10 21:29       ` [1.9.12][OpenBSD] " Ludovic Courtès
2010-09-12 11:32         ` Andy Wingo
2010-09-12 17:41           ` Ludovic Courtès
2010-09-12 20:26             ` Andy Wingo
2010-09-12 20:38               ` Ludovic Courtès
2010-09-12 21:41                 ` Andy Wingo
2010-09-08 23:06   ` [1.9.12][OpenBSD] CFLAGS="-g -O0" " primus
2010-09-10  8:41     ` Andy Wingo
2010-09-10 13:53       ` primus

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=20100910154456.GH18170@x.lence.net \
    --to=rprimus@gmail.com \
    --cc=bug-guile@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).