From: ludo@gnu.org (Ludovic Courtès)
To: ais@euve8129.vserver.de
Cc: 14549@debbugs.gnu.org
Subject: bug#14549: warning while compiling guile 2.0.9
Date: Tue, 04 Jun 2013 12:29:55 +0200 [thread overview]
Message-ID: <87li6q9nj0.fsf@gnu.org> (raw)
In-Reply-To: <bb5cb1f86ab838f9bdc4d1a762995c86.squirrel@www.skuschel.de> (ais@euve8129.vserver.de's message of "Mon, 3 Jun 2013 10:40:58 +0200")
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 10:29 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 [this message]
2013-06-04 13:43 ` ais
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=87li6q9nj0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=14549@debbugs.gnu.org \
--cc=ais@euve8129.vserver.de \
/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).