From: Jens <jensl@laas.mine.nu>
To: musl@lists.openwall.com
Subject: Re: semtcl for x86_64
Date: Sat, 22 Sep 2012 19:09:12 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.02.1209221908220.12327@laas.mine.nu> (raw)
In-Reply-To: <20120922120453.GT254@brightrain.aerifal.cx>
On Sat, 22 Sep 2012, Rich Felker wrote:
> On Sat, Sep 22, 2012 at 11:17:14AM +0200, Jens wrote:
>>
>>
>> On Sat, 22 Sep 2012, Jens wrote:
>>
>>>
>>> Hello I have some trouble getting semctl working:
>>>
>>> Tried in both musl and uclibc to compare.
>>
>> Forgot to mention its musl 0.9.6.
>>
>> Cheers,
>> Jens
>
> Should be fixed now... Please let me know if it's still broken.
Now I ran into shmctl which I think have the same problem.
Regards,
Jens
>
> Rich
>
next prev parent reply other threads:[~2012-09-22 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 8:26 Jens
2012-09-22 9:17 ` Jens
2012-09-22 12:04 ` Rich Felker
2012-09-22 12:17 ` Jens
2012-09-22 12:25 ` Rich Felker
2012-09-22 17:09 ` Jens [this message]
2012-09-22 20:09 ` Rich Felker
2012-09-22 12:14 ` Jens
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=alpine.LNX.2.02.1209221908220.12327@laas.mine.nu \
--to=jensl@laas.mine.nu \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).