Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 465792 - sys-libs/uclibc - Add definition of MSG_WAITFORONE and MSG_CMSG_CLOEXEC
Summary: sys-libs/uclibc - Add definition of MSG_WAITFORONE and MSG_CMSG_CLOEXEC
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Embedded Gentoo Team
URL: http://git.uclibc.org/uClibc/commit/?...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-13 14:29 UTC by pmn
Modified: 2013-05-19 05:21 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pmn 2013-04-13 14:29:47 UTC
this patch:
<http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/uclibc/uclibc-0.9.33/define-MSG_CMSG_CLOEXEC.patch>
has been commited into the git repo of uclibc and is needed to build systemd on systems with native uclibc. i was wondering if it's possbile to incorporate this for 0.9.33.2 for now until uclibc's next release cycle.

Reproducible: Always
Comment 1 pmn 2013-04-13 14:32:46 UTC
FYI, i.e. if someone would like to test this with systemd:
i use the set of patches here to build systemd on uclibc:

<http://git.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd>
Comment 2 SpanKY gentoo-dev 2013-04-15 21:26:01 UTC
patches in random projects (like yocto) are not interesting.  the git commits to the actual uClibc repo are the only thing i'm going to pull in.
Comment 3 pmn 2013-04-15 22:03:54 UTC
(In reply to comment #2)
> patches in random projects (like yocto) are not interesting.  the git
> commits to the actual uClibc repo are the only thing i'm going to pull in.

you mean this?
http://git.uclibc.org/uClibc/plain/libc/sysdeps/linux/common/bits/socket.h

that will do.
Comment 4 pmn 2013-04-15 22:12:58 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > patches in random projects (like yocto) are not interesting.  the git
> > commits to the actual uClibc repo are the only thing i'm going to pull in.
> 
> you mean this?
> http://git.uclibc.org/uClibc/plain/libc/sysdeps/linux/common/bits/socket.h
> 
> that will do.

oh i see, they don't use the patch from yocto upstream.