From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9291] New: perl: SysV message queues not configured, even if available
Date: Thu, 22 Sep 2016 06:56:14 +0000 [thread overview]
Message-ID: <bug-9291-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9291
Bug ID: 9291
Summary: perl: SysV message queues not configured, even if
available
Product: buildroot
Version: 2016.02
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mail2k at web.de
CC: buildroot at uclibc.org
Target Milestone: ---
Buildroot 2016.02 with perl-5.22.1 compiled for i686-linux:
Problem on the target:
perl -e "msgget(90001, 1);"
msgget not implemented at -e line 1.
This is a configuration error. SysV-IPC is available on the target.
./configure in the perl directory gives the following:
...
Checking for msgctl ... found
Checking for msgget ... found
Checking for msgrcv ... found
Checking for msgsnd ... found
Checking for msync ... found
Checking for munmap ... found
...
Nevertheless, HAS_MSG is not defined in config.h and the message queues are not
compiled in.
If I manually define HAS_MSG in config.h and do "make", I get a perl executable
with msgget that works on my target. But that is not the way to solve this
problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-09-22 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 6:56 bugzilla at busybox.net [this message]
2016-10-22 20:02 ` [Buildroot] [Bug 9291] perl: SysV message queues not configured, even if available bugzilla at busybox.net
2017-02-13 20:46 ` bugzilla at busybox.net
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-9291-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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