From: ais@euve8129.vserver.de
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#14549: warning while compiling guile 2.0.9
Date: Tue, 4 Jun 2013 15:43:20 +0200 [thread overview]
Message-ID: <1d610deadf9c59110c9f981687fbd02f.squirrel@www.skuschel.de> (raw)
In-Reply-To: <87li6q9nj0.fsf@gnu.org>
Hi Ludovic,
thanks for the reply.
The compilation did not succeed. There're several reasons behind it.
One thing is that the pthread_np.h should be avoided on OpenBSD
alltogether, since this it implements just a short fraction of functions.
So if functions from pthread_np.h should be used, then they must be tested
one by one and not assuming that if the file is present so are the
functions. I simply renamed the file "pthread_np.h" to
"pthread_np.h.original" and ran configure and this time configure
succeeded without any complaint.
The other thing with OpenBSD is, that the stock-installation of the
Boehm-GC package is more or less broken. I compiled my own version of this
library and then I could compile guile successfully, but the linker did
complain about some pthread_np* functions.
Using the stock installation/package then there's a conflict with some
defines being set (notably: GC_REDIRECT_TO_LOCAL). The stock installation
has no such file (gc_local_alloc.h) so the defines inside must be set
accordingly.
Currently I'm very busy to follow up this problem but I'm very willing to
provide more information on this topic, since I keen on having a current
version of Guile running under OpenBSD.
Sebastian
> Hi,
>
> Thanks for the report.
>
> ais@euve8129.vserver.de skribis:
>
>> Compiling guile 2.0.9 under OpenBSD 5.2 x86
>
> Did compilation eventually succeed? Did you run âmake checkâ?
>
>> checking pthread.h usability... yes
>> checking pthread.h presence... yes
>> checking for pthread.h... yes
>> checking pthread_np.h usability... no
>> checking pthread_np.h presence... yes
>> configure: WARNING: pthread_np.h: present but cannot be compiled
>> configure: WARNING: pthread_np.h: check for missing prerequisite
>> headers?
>> configure: WARNING: pthread_np.h: see the Autoconf documentation
>> configure: WARNING: pthread_np.h: section "Present But Cannot Be
>> Compiled"
>
> Could you send the output of:
>
> grep pthread_np config.log
>
> Thanks,
> Ludoâ.
>
next prev parent reply other threads:[~2013-06-04 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 8:40 bug#14549: warning while compiling guile 2.0.9 ais
2013-06-04 10:29 ` Ludovic Courtès
2013-06-04 13:43 ` ais [this message]
2016-06-20 21:25 ` Andy Wingo
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=1d610deadf9c59110c9f981687fbd02f.squirrel@www.skuschel.de \
--to=ais@euve8129.vserver.de \
--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).