Re: Bug#181661: opie-libs-fb: [m68k] FTBFS
I forget to Cc: debian-glibc.
At Thu, 20 Feb 2003 05:29:56 -0700,
Ivan E. Moore II <rkrusty@earthlink.net> wrote:
> On Thu, Feb 20, 2003 at 10:34:03AM +0100, Geert Uytterhoeven wrote:
> > On Wed, 19 Feb 2003, Christian T. Steigies wrote:
> > > On Wed, Feb 19, 2003 at 03:51:06PM -0700, Ivan E. Moore II wrote:
> > > > On Wed, Feb 19, 2003 at 04:48:58PM -0600, Christian T. Steigies wrote:
> > > > > Moin,
> > > > > On Wed, Feb 19, 2003 at 03:18:23PM -0700, Ivan E. Moore II wrote:
> > > > > >
> > > > > > Yea it seems to be that ADV_SEQUENTIAL doesn't seem to exist on m68k
> > > > > > or is in some header that I'm not depending on. This is specific to
> > > > > > m68k so far. On x86 it's out of /usr/include/bits/mman.h
> > > > >
> > > > > buildd@aahz:/usr/include>grep -r ADV_SEQUENTIAL *
> > > > > asm/mman.h:#define MADV_SEQUENTIAL 0x2 /* read-ahead aggressively */
> > > > >
> > > > > Do you have to change the source/Makefile so that this is found on m68k?
> > > >
> > > > When I get home this evening I will take a look at the source and see how
> > > > it's trying to use this. Why is it in a different location on m68k?
> > >
> > > On i386 it is defined in both locations:
> > >
> > > cts@lepcts:/usr/include>grep -r ADV_SEQUENTIAL *
> > > asm/mman.h:#define MADV_SEQUENTIAL 0x2 /* read-ahead aggressively */
> > > bits/mman.h:# define MADV_SEQUENTIAL 2 /* Expect sequential page references. */
> > >
> > > So is there an error on i386, on m68k, or both? Maybe the kernel-hackers
> > > know.
> >
> > In 2.4.20, it's defined in asm/mman.h on all architectures.
> >
> > According to madvise(2), you have to include <sys/mman.h>, which includes
> > <bits/mman.h> (on Debian/ia32). But <sys/mman.h> and <bits/mman.h> are
> > glibc-domain, not kernel domain.
> >
> > Gr{oetje,eeting}s,
> >
>
> Any input on this libc6 folks?
It's glibc bug. The latest upstream glibc fixes this problem.
We can fix it to pull from upstream cvs. Please reassign it
to glibc as you need.
Regards,
-- gotom
Reply to: