From: Geert U. <ge...@li...> - 2013-05-12 21:10:49
|
On Sun, 12 May 2013, Geert Uytterhoeven wrote: > However, the full list of errors isn't that unmanageable, so I'm following > up with a digested list... arch/um/drivers/cow_user.c:216: error: implicit declaration of function 'htobe32': 1 errors in 1 logs arch/um/drivers/cow_user.c:249: error: implicit declaration of function 'htobe64': 1 errors in 1 logs arch/um/drivers/cow_user.c:303: error: implicit declaration of function 'be32toh': 1 errors in 1 logs arch/um/drivers/cow_user.c:330: error: implicit declaration of function 'be64toh': 1 errors in 1 logs arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs arch/um/os-Linux/skas/process.c:321: error: (Each undeclared identifier is reported only once: 1 errors in 1 logs arch/um/os-Linux/skas/process.c:321: error: for each function it appears in.): 1 errors in 1 logs arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' undeclared (first use in this function): 1 errors in 1 logs arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' undeclared (first use in this function): 1 errors in 1 logs arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier is reported only once: 1 errors in 1 logs arch/um/os-Linux/start_up.c:245: error: for each function it appears in.): 1 errors in 1 logs arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' undeclared (first use in this function): 1 errors in 1 logs arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs v3.10-rc1/um-i386/um-defconfig Old host environment on kissb? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: richard -r. w. <ric...@gm...> - 2013-05-12 21:17:35
|
Geert, On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven <ge...@li...> wrote: > On Sun, 12 May 2013, Geert Uytterhoeven wrote: >> However, the full list of errors isn't that unmanageable, so I'm following >> up with a digested list... > > arch/um/drivers/cow_user.c:216: error: implicit declaration of function 'htobe32': 1 errors in 1 logs > arch/um/drivers/cow_user.c:249: error: implicit declaration of function 'htobe64': 1 errors in 1 logs > arch/um/drivers/cow_user.c:303: error: implicit declaration of function 'be32toh': 1 errors in 1 logs > arch/um/drivers/cow_user.c:330: error: implicit declaration of function 'be64toh': 1 errors in 1 logs > arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs > arch/um/os-Linux/skas/process.c:321: error: (Each undeclared identifier is reported only once: 1 errors in 1 logs > arch/um/os-Linux/skas/process.c:321: error: for each function it appears in.): 1 errors in 1 logs > arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' undeclared (first use in this function): 1 errors in 1 logs > arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs > arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' undeclared (first use in this function): 1 errors in 1 logs > arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier is reported only once: 1 errors in 1 logs > arch/um/os-Linux/start_up.c:245: error: for each function it appears in.): 1 errors in 1 logs > arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs > arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' undeclared (first use in this function): 1 errors in 1 logs > arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs > v3.10-rc1/um-i386/um-defconfig > Old host environment on kissb? This really looks like a host environment issue. PTRACE_O_TRACESYSGOOD for example is defined in /usr/include/linux/ptrace.h -- Thanks, //richard |
From: Geert U. <ge...@li...> - 2013-05-13 08:19:05
|
On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger <ric...@gm...> wrote: > On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven > <ge...@li...> wrote: >> On Sun, 12 May 2013, Geert Uytterhoeven wrote: >>> However, the full list of errors isn't that unmanageable, so I'm following >>> up with a digested list... >> >> arch/um/drivers/cow_user.c:216: error: implicit declaration of function 'htobe32': 1 errors in 1 logs >> arch/um/drivers/cow_user.c:249: error: implicit declaration of function 'htobe64': 1 errors in 1 logs >> arch/um/drivers/cow_user.c:303: error: implicit declaration of function 'be32toh': 1 errors in 1 logs >> arch/um/drivers/cow_user.c:330: error: implicit declaration of function 'be64toh': 1 errors in 1 logs >> arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs >> arch/um/os-Linux/skas/process.c:321: error: (Each undeclared identifier is reported only once: 1 errors in 1 logs >> arch/um/os-Linux/skas/process.c:321: error: for each function it appears in.): 1 errors in 1 logs >> arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' undeclared (first use in this function): 1 errors in 1 logs >> arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs >> arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' undeclared (first use in this function): 1 errors in 1 logs >> arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier is reported only once: 1 errors in 1 logs >> arch/um/os-Linux/start_up.c:245: error: for each function it appears in.): 1 errors in 1 logs >> arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs >> arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' undeclared (first use in this function): 1 errors in 1 logs >> arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' undeclared (first use in this function): 1 errors in 1 logs >> v3.10-rc1/um-i386/um-defconfig >> Old host environment on kissb? > > This really looks like a host environment issue. > PTRACE_O_TRACESYSGOOD for example is defined in /usr/include/linux/ptrace.h Yep, just like e.g. htobe32(). Michael, Stephen: Any chance this can be fixed? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Michael E. <mi...@el...> - 2013-05-13 10:13:07
|
Geert Uytterhoeven <ge...@li...> wrote: >On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger ><ric...@gm...> wrote: >> On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven >> <ge...@li...> wrote: >>> On Sun, 12 May 2013, Geert Uytterhoeven wrote: >>>> However, the full list of errors isn't that unmanageable, so I'm >following >>>> up with a digested list... >>> >>> arch/um/drivers/cow_user.c:216: error: implicit declaration of >function 'htobe32': 1 errors in 1 logs >>> arch/um/drivers/cow_user.c:249: error: implicit declaration of >function 'htobe64': 1 errors in 1 logs >>> arch/um/drivers/cow_user.c:303: error: implicit declaration of >function 'be32toh': 1 errors in 1 logs >>> arch/um/drivers/cow_user.c:330: error: implicit declaration of >function 'be64toh': 1 errors in 1 logs >>> arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' >undeclared (first use in this function): 1 errors in 1 logs >>> arch/um/os-Linux/skas/process.c:321: error: (Each undeclared >identifier is reported only once: 1 errors in 1 logs >>> arch/um/os-Linux/skas/process.c:321: error: for each function it >appears in.): 1 errors in 1 logs >>> arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' >undeclared (first use in this function): 1 errors in 1 logs >>> arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' >undeclared (first use in this function): 1 errors in 1 logs >>> arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' >undeclared (first use in this function): 1 errors in 1 logs >>> arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier >is reported only once: 1 errors in 1 logs >>> arch/um/os-Linux/start_up.c:245: error: for each function it appears >in.): 1 errors in 1 logs >>> arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' >undeclared (first use in this function): 1 errors in 1 logs >>> arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' >undeclared (first use in this function): 1 errors in 1 logs >>> arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' >undeclared (first use in this function): 1 errors in 1 logs >>> v3.10-rc1/um-i386/um-defconfig >>> Old host environment on kissb? >> >> This really looks like a host environment issue. >> PTRACE_O_TRACESYSGOOD for example is defined in >/usr/include/linux/ptrace.h > >Yep, just like e.g. htobe32(). > >Michael, Stephen: Any chance this can be fixed? Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. cheers -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
From: Geert U. <ge...@li...> - 2013-05-13 10:02:20
|
On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman <mi...@el...> wrote: >>> This really looks like a host environment issue. >>> PTRACE_O_TRACESYSGOOD for example is defined in >>/usr/include/linux/ptrace.h Actually these are in both /usr/include/sys/ptrace.h and /usr/include/linux/ptrace.h on my system. >>Yep, just like e.g. htobe32(). /usr/include/endian.h >>Michael, Stephen: Any chance this can be fixed? > > Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. Perhaps just the cross C library? On Ubuntu 10.04, both /usr/include/endian.h and /usr/include/sys/ptrace.h are provided by libc6-dev. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: richard -r. w. <ric...@gm...> - 2013-05-13 10:07:29
|
On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman <mi...@el...> wrote: > > > Geert Uytterhoeven <ge...@li...> wrote: > >>On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger >><ric...@gm...> wrote: >>> On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven >>> <ge...@li...> wrote: >>>> On Sun, 12 May 2013, Geert Uytterhoeven wrote: >>>>> However, the full list of errors isn't that unmanageable, so I'm >>following >>>>> up with a digested list... >>>> >>>> arch/um/drivers/cow_user.c:216: error: implicit declaration of >>function 'htobe32': 1 errors in 1 logs >>>> arch/um/drivers/cow_user.c:249: error: implicit declaration of >>function 'htobe64': 1 errors in 1 logs >>>> arch/um/drivers/cow_user.c:303: error: implicit declaration of >>function 'be32toh': 1 errors in 1 logs >>>> arch/um/drivers/cow_user.c:330: error: implicit declaration of >>function 'be64toh': 1 errors in 1 logs >>>> arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' >>undeclared (first use in this function): 1 errors in 1 logs >>>> arch/um/os-Linux/skas/process.c:321: error: (Each undeclared >>identifier is reported only once: 1 errors in 1 logs >>>> arch/um/os-Linux/skas/process.c:321: error: for each function it >>appears in.): 1 errors in 1 logs >>>> arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' >>undeclared (first use in this function): 1 errors in 1 logs >>>> arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' >>undeclared (first use in this function): 1 errors in 1 logs >>>> arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' >>undeclared (first use in this function): 1 errors in 1 logs >>>> arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier >>is reported only once: 1 errors in 1 logs >>>> arch/um/os-Linux/start_up.c:245: error: for each function it appears >>in.): 1 errors in 1 logs >>>> arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' >>undeclared (first use in this function): 1 errors in 1 logs >>>> arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' >>undeclared (first use in this function): 1 errors in 1 logs >>>> arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' >>undeclared (first use in this function): 1 errors in 1 logs >>>> v3.10-rc1/um-i386/um-defconfig >>>> Old host environment on kissb? >>> >>> This really looks like a host environment issue. >>> PTRACE_O_TRACESYSGOOD for example is defined in >>/usr/include/linux/ptrace.h >> >>Yep, just like e.g. htobe32(). >> >>Michael, Stephen: Any chance this can be fixed? > > Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. Looks like you are the first man on planet earth who tries do build UML/x86 on powerpc. :D -- Thanks, //richard |
From: Geert U. <ge...@li...> - 2013-05-13 10:18:17
|
On Mon, May 13, 2013 at 12:07 PM, richard -rw- weinberger <ric...@gm...> wrote: > On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman > <mi...@el...> wrote: >> Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. > > Looks like you are the first man on planet earth who tries do build > UML/x86 on powerpc. :D Well, it used to work: http://kisskb.ellerman.id.au/kisskb/target/2974/ Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: richard -r. w. <ric...@gm...> - 2013-05-13 10:20:33
|
On Mon, May 13, 2013 at 12:18 PM, Geert Uytterhoeven <ge...@li...> wrote: > On Mon, May 13, 2013 at 12:07 PM, richard -rw- weinberger > <ric...@gm...> wrote: >> On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman >> <mi...@el...> wrote: > >>> Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. >> >> Looks like you are the first man on planet earth who tries do build >> UML/x86 on powerpc. :D > > Well, it used to work: http://kisskb.ellerman.id.au/kisskb/target/2974/ Cool! -- Thanks, //richard |
From: Stephen R. <sf...@ca...> - 2013-05-15 03:07:52
|
Hi all, On Mon, 13 May 2013 12:20:24 +0200 richard -rw- weinberger <ric...@gm...> wrote: > > On Mon, May 13, 2013 at 12:18 PM, Geert Uytterhoeven > <ge...@li...> wrote: > > On Mon, May 13, 2013 at 12:07 PM, richard -rw- weinberger > > <ric...@gm...> wrote: > >> On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman > >> <mi...@el...> wrote: > > > >>> Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. > >> > >> Looks like you are the first man on planet earth who tries do build > >> UML/x86 on powerpc. :D > > > > Well, it used to work: http://kisskb.ellerman.id.au/kisskb/target/2974/ > > Cool! We started getting these PTRACE_ errors on Nov 4, 2011. Just before that, we have commit 966e803ab125 ("um: unify ptrace_user.h") which seems to have lost the include of linux/ptrace.h and now only includes sys/ptrace.h ... -- Cheers, Stephen Rothwell sf...@ca... |
From: Michael E. <mi...@el...> - 2013-05-13 12:16:04
|
On Mon, 2013-05-13 at 12:07 +0200, richard -rw- weinberger wrote: > On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman > <mi...@el...> wrote: > > > > > > Geert Uytterhoeven <ge...@li...> wrote: > > > >>On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger > >><ric...@gm...> wrote: > >>> On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven > >>> <ge...@li...> wrote: > >>>> On Sun, 12 May 2013, Geert Uytterhoeven wrote: > >>>>> However, the full list of errors isn't that unmanageable, so I'm > >>following > >>>>> up with a digested list... > >>>> > >>>> arch/um/drivers/cow_user.c:216: error: implicit declaration of > >>function 'htobe32': 1 errors in 1 logs > >>>> arch/um/drivers/cow_user.c:249: error: implicit declaration of > >>function 'htobe64': 1 errors in 1 logs > >>>> arch/um/drivers/cow_user.c:303: error: implicit declaration of > >>function 'be32toh': 1 errors in 1 logs > >>>> arch/um/drivers/cow_user.c:330: error: implicit declaration of > >>function 'be64toh': 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:321: error: (Each undeclared > >>identifier is reported only once: 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:321: error: for each function it > >>appears in.): 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier > >>is reported only once: 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:245: error: for each function it appears > >>in.): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> v3.10-rc1/um-i386/um-defconfig > >>>> Old host environment on kissb? > >>> > >>> This really looks like a host environment issue. > >>> PTRACE_O_TRACESYSGOOD for example is defined in > >>/usr/include/linux/ptrace.h > >> > >>Yep, just like e.g. htobe32(). > >> > >>Michael, Stephen: Any chance this can be fixed? > > > > Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. > > Looks like you are the first man on planet earth who tries do build > UML/x86 on powerpc. :D :) It has given us some trouble over the years. I'll talk to Stephen tomorrow about it and see if we can get it working again. cheers |
From: Stephen R. <sf...@ca...> - 2013-05-15 03:02:57
|
On Mon, 13 May 2013 22:15:52 +1000 Michael Ellerman <mi...@el...> wrote: > > On Mon, 2013-05-13 at 12:07 +0200, richard -rw- weinberger wrote: > > On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman > > <mi...@el...> wrote: > > > > > > > > > Geert Uytterhoeven <ge...@li...> wrote: > > > > > >>On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger > > >><ric...@gm...> wrote: > > >>> On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven > > >>> <ge...@li...> wrote: > > >>>> On Sun, 12 May 2013, Geert Uytterhoeven wrote: > > >>>>> However, the full list of errors isn't that unmanageable, so I'm > > >>following > > >>>>> up with a digested list... > > >>>> > > >>>> arch/um/drivers/cow_user.c:216: error: implicit declaration of > > >>function 'htobe32': 1 errors in 1 logs > > >>>> arch/um/drivers/cow_user.c:249: error: implicit declaration of > > >>function 'htobe64': 1 errors in 1 logs > > >>>> arch/um/drivers/cow_user.c:303: error: implicit declaration of > > >>function 'be32toh': 1 errors in 1 logs > > >>>> arch/um/drivers/cow_user.c:330: error: implicit declaration of > > >>function 'be64toh': 1 errors in 1 logs > > >>>> v3.10-rc1/um-i386/um-defconfig > > >>>> Old host environment on kissb? > > >>> > > >>> This really looks like a host environment issue. > > >>> PTRACE_O_TRACESYSGOOD for example is defined in > > >>/usr/include/linux/ptrace.h > > >> > > >>Yep, just like e.g. htobe32(). > > >> > > >>Michael, Stephen: Any chance this can be fixed? > > > > > > Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. > > > > Looks like you are the first man on planet earth who tries do build > > UML/x86 on powerpc. :D > > :) It has given us some trouble over the years. > > I'll talk to Stephen tomorrow about it and see if we can get it working > again. So htobe32 etc were introduced in glibc 2.9 - our build environment is glibc 2.3 ... Documentation/Changes does not specify a minimum version of glibc. -- Cheers, Stephen Rothwell sf...@ca... |
From: Geert U. <ge...@li...> - 2013-05-15 06:51:01
|
On Wed, May 15, 2013 at 4:57 AM, Stephen Rothwell <sf...@ca...> wrote: > So htobe32 etc were introduced in glibc 2.9 - our build environment is > glibc 2.3 ... Documentation/Changes does not specify a minimum version of > glibc. This is a UML "requirement", not a generic Linux build environment requirement. Introduced by commit d824d06328904f610b47652dcd488392f2fc62b6 Author: Al Viro <vi...@ze...> Date: Thu Apr 5 23:35:03 2012 -0400 um: switch cow_user.h to htobe{32,64}/betoh{32,64} ... rather than open-coding the 64bit versions. endian.h has those guys. Signed-off-by: Al Viro <vi...@ze...> Signed-off-by: Richard Weinberger <ri...@no...> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |