Re: [PATCH v2 1/3] Avoid cyclic header dependencies

Corinna Vinschen <[email protected]>
Newsgroups gmane.comp.lib.newlib
Message-ID <[email protected]>
On May 16 14:40, Sebastian Huber wrote:
> RTEMS uses a considerable part of FreeBSD kernel and user space sources.
> These sources are compiled with a __FreeBSD__ define.  On 2018-06-26
> Gerald Pfeifer changed the GCC provided <stddef.h> so that it includes
> <sys/_types.h> if __FreeBSD__ is defined.  The Newlib <sys/_types.h>
> included <sys/lock.h> which includes <sys/cdefs.h> on RTEMS which
> includes <stddef.h>.  To get rid of this cyclic dependency move the
> optional _flock_t definition to <sys/reent.h>.
> 
> Signed-off-by: Sebastian Huber <[email protected]>
> ---
>  newlib/libc/include/sys/_types.h | 5 -----
>  newlib/libc/include/sys/reent.h  | 5 +++++
>  2 files changed, 5 insertions(+), 5 deletions(-)

Series pushed.  Can you please add a cover letter when sending a series?
It's kind of awkward to reply to a single patch in the series if the
entire series is affected.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlz03QUACgkQ9TYGna5E
T6AZMRAAmU+9IrCeIfPTHvIGqYtONwqNNzXVQ0UP7iFLekvY7sIoKJPLdfTbWYrg
asE5/pki0B9tB6SfOrw67eiTZvGm875wVaXrsbrJq6sYDzCMDusmFdoQuzkadcSl
sQvQiL1BhzbN3tt3PcnlV2WGVt/xpEFaEZTxalNRUSiexCL5Hor0CZCOESbX7C7f
HFDwyFliUQIAL7nIFNhzmyMwqwWtYjkp6WjNoWwpoQ54v4gZETp5DUkCit0U8Yyl
5xYjrMEo/YJVfNAyCa5ay0AblqiEKRp5JEbauHGNvZeH04A+VIREZs6XIkn/sM32
bbGgNYvIzYl3upPdKSdrsUNng4D5JkbTZaNwEaAqWKlhfHM7a3iDMs1kuP5XmKuO
b5jTQKcM1MdkUue9aQi6kL2VC7lVA6EKdUefn6bYp12heJIN6j5hvAdRGnqz1dmd
3bhf9XKAaO0EsOJoxsDNYYJnjlilPV11+bn5Ja5Kw9H6hZgy7n0iKQb0wVGzHwcZ
mutOO1Voyl4RG01+NL0BN4guNqBrvXuy/XJmHigQPFrpn0DQbHp+VR9uukWCmDSX
iI0hz4I9FdVwbBNd/JbmfIihxjoL6nAzjcbPtcpXI6byO/A+XSRWkS2Yja9O4Pl3
sYyrWvDRuIWnJGqVFfmbJIFXyzGV+/zeeB5MOdcv8dKC8lNL5ko=
=Eknk
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.