All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zankel <chris@zankel.net>
To: Jan Dittmer <jdi@l4x.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	michal.k.k.piotrowski@gmail.com, wli@holomorphy.com,
	rth@twiddle.net
Subject: Re: 2.6.23-rc2 cross compile regressions (alpha,sparc,xtensa)
Date: Mon, 06 Aug 2007 00:42:08 -0700	[thread overview]
Message-ID: <46B6D0D0.2010209@zankel.net> (raw)
In-Reply-To: <46B6CE6B.7010808@l4x.org>

Jan,

Thanks for your report. I am working on some patches that I plan to 
submit this week to fix those issues.

Thanks,
-Chris

Jan Dittmer wrote:
> sparc/defconfig:
>  CC      init/main.o
> In file included from include/linux/proc_fs.h:5,
>                 from init/main.c:14:
> include/linux/fs.h:848: warning: `struct flock' declared inside 
> parameter list
> include/linux/fs.h:848: warning: its scope is only this definition or 
> declaration, which is probably not what you want
> include/linux/fs.h:850: warning: `struct flock' declared inside 
> parameter list
> include/linux/fs.h:853: warning: `struct flock64' declared inside 
> parameter list
> include/linux/fs.h:855: warning: `struct flock64' declared inside 
> parameter list
> init/main.c: In function `init_post':
> init/main.c:782: error: `O_RDWR' undeclared (first use in this function)
> init/main.c:782: error: (Each undeclared identifier is reported only once
> init/main.c:782: error: for each function it appears in.)
> make[2]: *** [init/main.o] Error 1
> make[1]: *** [init] Error 2
> make: *** [_all] Error 2
> 
> xtensa/defconfig:
>  CC      arch/xtensa/kernel/process.o
> arch/xtensa/kernel/process.c:50: error: `INR_OPEN' undeclared here (not 
> in a function)
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[7].rlim_cur')
> arch/xtensa/kernel/process.c:50: error: `INR_OPEN' undeclared here (not 
> in a function)
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[7].rlim_max')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[7]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[8]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[9]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[10]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[11]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[12]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[13]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim[14]')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.rlim')
> arch/xtensa/kernel/process.c:50: error: initializer element is not constant
> arch/xtensa/kernel/process.c:50: error: (near initialization for 
> `init_signals.<anonymous>')
> arch/xtensa/kernel/process.c: In function `xtensa_execve':
> arch/xtensa/kernel/process.c:449: error: implicit declaration of 
> function `getname'
> arch/xtensa/kernel/process.c:449: warning: assignment makes pointer from 
> integer without a cast
> arch/xtensa/kernel/process.c:460: error: implicit declaration of 
> function `putname'
> make[2]: *** [arch/xtensa/kernel/process.o] Error 1
> make[1]: *** [arch/xtensa/kernel] Error 2
> make: *** [_all] Error 2
> 
> alpha/defconfig:
>  LD      .tmp_vmlinux1
> arch/alpha/kernel/built-in.o(.text+0xaaa8): In function 
> `pdev_save_srm_config':
> include/linux/slub_def.h:154: undefined reference to 
> `__kmalloc_size_too_large'
> arch/alpha/kernel/built-in.o(.text+0xaaac):include/linux/slub_def.h:154: 
> undefined reference to `__kmalloc_size_too_large'
> arch/alpha/kernel/built-in.o(.text+0xd0a8): In function 
> `module_frob_arch_sections':
> include/linux/slub_def.h:154: undefined reference to 
> `__kmalloc_size_too_large'
> arch/alpha/kernel/built-in.o(.text+0xd0ac):include/linux/slub_def.h:154: 
> undefined reference to `__kmalloc_size_too_large'
> arch/alpha/kernel/built-in.o(.text+0x19388): In function 
> `srmcons_get_private_struct':
> include/linux/slub_def.h:154: undefined reference to 
> `__kmalloc_size_too_large'
> arch/alpha/kernel/built-in.o(.text+0x1938c):include/linux/slub_def.h:154: 
> more undefined references to `__kmalloc_size_too_large' follow
> make[1]: *** [.tmp_vmlinux1] Error 1
> make: *** [_all] Error 2
> 
> With patch: ia64/defconfig.
> Not compiling: blackfin,cris,frv,h8300,v850
> 
> Jan
> 
> 


      parent reply	other threads:[~2007-08-06  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06  7:31 2.6.23-rc2 cross compile regressions (alpha,sparc,xtensa) Jan Dittmer
2007-08-06  7:34 ` David Miller
2007-08-06  7:42 ` Christian Zankel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B6D0D0.2010209@zankel.net \
    --to=chris@zankel.net \
    --cc=jdi@l4x.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=rth@twiddle.net \
    --cc=wli@holomorphy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.