On Mon, Jan 13, 2020 at 09:47:37AM +0100, Guillermo Rodriguez Garcia wrote:
> El dom., 12 ene. 2020 a las 13:52, Michael Olbrich
> (<[email protected]>) escribió:
> >
> > On Tue, Dec 10, 2019 at 07:55:36PM +0100, Guillermo Rodríguez wrote:
> > > Signed-off-by: Guillermo Rodriguez <[email protected]>
> > > ---
> > >  .../0003-include-sysmacros-for-new-glibc.patch  | 17 +++++++++++++++++
> > >  patches/udev-182/series                         |  1 +
> > >  2 files changed, 18 insertions(+)
> > >  create mode 100644 
> > > patches/udev-182/0003-include-sysmacros-for-new-glibc.patch
> > >
> > > diff --git a/patches/udev-182/0003-include-sysmacros-for-new-glibc.patch 
> > > b/patches/udev-182/0003-include-sysmacros-for-new-glibc.patch
> > > new file mode 100644
> > > index 000000000..b2f8db670
> > > --- /dev/null
> > > +++ b/patches/udev-182/0003-include-sysmacros-for-new-glibc.patch
> > > @@ -0,0 +1,17 @@
> > > +Fix build with recent glibc releases where <sys/sysmacros.h> is no
> > > +longer included as part of <sys/types.h>.
> > > +
> > > +Ref.: https://wiki.gentoo.org/wiki/Glibc_2.26_porting_notes/sysmacros.h
> > > +
> > > +Index: udev-182/src/libudev.h
> > > +===================================================================
> >
> > Please provide a proper patch header. Just recreating the patches with
> > git[1] should work.
> 
> I created the patch using quilt as described in the ptxdist
> documentation (https://www.ptxdist.org/doc/dev_manual.html#using-quilt).
> If you don't intend to support this workflow, then I think you should
> cleary state that in the docs.

Indeed, I should add a comment to the docs about this.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
[email protected]

Reply via email to