On Fri, Oct 30, 2015 at 5:02 PM, Balaco Baco <balacob...@imap.cc> wrote:
> I restarted, now I've got another kernel source (2.6.32.68), knowing
> that it may be old, but it's the "newer old" for 2.6, and I hoped that
> it would work.

Are you an archeologist? ;-)
Is there a particular reason why you can't use something recent?

> Steps done:
>
> 1. downloaded https://cdn. kernel
> .org/pub/linux/kernel/v2.6/longterm/v2.6.32/linux-2.6.32.68.tar.xz
> 2. extract with tar cJf (whatever)
> 3. A few commands:
>     make defconfig ARCH=um
>     # config is saved on a file, to be restarted from a known point
>     whenever needed
>     make menuconfig ARCH=um
>     make mrproper                    # zero start guarantee when
>     repeating these steps
>     make mrproper ARCH=um   #  "
>     make ARCH=uml
>
> 4. It stops a few seconds after, with a few errors that may be simple to
> fix:
>
> ===============
> arch/um/os-Linux/start_up.c: In function 'check_coredump_limit':
> arch/um/os-Linux/start_up.c:340:16: error: storage size of 'lim' isn't
> known
>   struct rlimit lim;
>                 ^
> arch/um/os-Linux/start_up.c:341:2: error: implicit declaration of
> function 'getrlimit' [-Werror=implicit-function-declaration]
>   int err = getrlimit(RLIMIT_CORE, &lim);
>   ^
> arch/um/os-Linux/start_up.c:341:22: error: 'RLIMIT_CORE' undeclared
> (first use in this function)
>   int err = getrlimit(RLIMIT_CORE, &lim);
>                       ^
> arch/um/os-Linux/start_up.c:341:22: note: each undeclared identifier is
> reported only once for each function it appears in
> arch/um/os-Linux/start_up.c:349:22: error: 'RLIM_INFINITY' undeclared
> (first use in this function)
>   if (lim.rlim_cur == RLIM_INFINITY)
>                       ^
> arch/um/os-Linux/start_up.c:340:16: warning: unused variable 'lim'
> [-Wunused-variable]
>   struct rlimit lim;
>                 ^
> cc1: some warnings being treated as errors
> make[1]: *** [arch/um/os-Linux/start_up.o] Error 1
> make: *** [arch/um/os-Linux] Error 2
>
> ===============
>
> Do you know the reason for these two errors? And how I should fix them?

It depends what libc you're using. AFAICT libc moved a header file to
a new location.

-- 
Thanks,
//richard

------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Reply via email to