All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: werner <w.landgraf@ru.ru>, linux-kernel@vger.kernel.org
Cc: "T. Makphaibulchoke" <tmac@hp.com>,
	Andreas Gruenbacher <a.gruenbacher@computer.org>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: 3.15-rc6  build / link failed  fs/built-in  mb_cache_entry problems
Date: Mon, 26 May 2014 22:04:45 -0700	[thread overview]
Message-ID: <53841CED.9010800@infradead.org> (raw)
In-Reply-To: <redirect-87012843@zbackend1.aha.ru>

On 05/26/2014 11:17 AM, werner wrote:
> building the kernel isnt successful,
> 
> problem with _mbècache_entry_release and _get
> 
> see below
> 
> there are also other errors
> 
> 
> The whole compiler list and config, see enclosed
> 
> 

First of all, my build using your kernel config file builds -- no errors,
just plenty of warnings.  I am using gcc version 4.7.2.  What gcc version
are you using?

mbcache.c uses __builtin_log2().  Maybe your gcc version does not support
that builtin function.

@tmac:  can mbcache.c #include <linux/log2.h> and use ilog2(NR_BG_LOCKS)
instead of using __builtin_log2(NR_BG_LOCKS) ?
(ref. commit ID 1f3e55fe02d12213f87869768aa2b0bad3ba9a7d)


> 
> 
> Since appr 3.10 ,  even if the kernels compile and build , on meanwhile 70% of the computers where I try to boot, the booting process crashs on different positions.

Please use return/line feed every 70-72 characters instead of assuming that
all email clients will display the text correctly.  They don't.

> 
> Currently, the quality is rather bad, similar as it was during the versions  2.6.30 ... 36 .
> 
> So it would be good, if the programmers would check everything more careful   (im not a programmer but only an user)
> 
> Enclosed is a compiling list, someone could see through this, and correct all problems, such as mismatches, undefined variables, etc
> 
> 
> W.Landgraf
> 
> 
> 
> 
> 
> ..
> 
> fs/built-in.o: In function `__mb_cache_entry_release':
> mbcache.c:(.text+0xa0d5f): undefined reference to `log2'
> mbcache.c:(.text+0xa0d6b): undefined reference to `__fixunsdfsi'
> mbcache.c:(.text+0xa0e22): undefined reference to `log2'
> mbcache.c:(.text+0xa0e34): undefined reference to `__fixunsdfsi'
> mbcache.c:(.text+0xa0f4e): undefined reference to `log2'
> mbcache.c:(.text+0xa0f60): undefined reference to `__fixunsdfsi'
> fs/built-in.o: In function `__mb_cache_entry_find':
> mbcache.c:(.text+0xa107e): undefined reference to `log2'
> mbcache.c:(.text+0xa108a): undefined reference to `__fixunsdfsi'
> mbcache.c:(.text+0xa115c): undefined reference to `log2'
> mbcache.c:(.text+0xa116e): undefined reference to `__fixunsdfsi'
> mbcache.c:(.text+0xa11dc): undefined reference to `log2'
> mbcache.c:(.text+0xa11e8): undefined reference to `__fixunsdfsi'
> mbcache.c:(.text+0xa126e): undefined reference to `log2'
> mbcache.c:(.text+0xa1280): undefined reference to `__fixunsdfsi'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3bdc): undefined reference to `log2'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3bf1): undefined reference to `__fixunsdfsi'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3d14): undefined reference to `log2'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3d26): undefined reference to `__fixunsdfsi'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3da7): undefined reference to `log2'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3db3): undefined reference to `__fixunsdfsi'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3e5e): undefined reference to `log2'
> fs/built-in.o: In function `mb_cache_entry_get':
> (.text+0xa3e70): undefined reference to `__fixunsdfsi'
> make: [vmlinux] Error 1 (ignored)



-- 
~Randy

  reply	other threads:[~2014-05-27  5:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 18:17 3.15-rc6 build / link failed fs/built-in mb_cache_entry problems werner
2014-05-27  5:04 ` Randy Dunlap [this message]
2014-05-27 22:22   ` Thavatchai Makphaibulchoke
2014-05-27 22:51     ` Randy Dunlap
     [not found]       ` <web-87633644@zbackend1.aha.ru>
2014-05-28 21:54         ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2014-05-25 10:04 werner

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=53841CED.9010800@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=a.gruenbacher@computer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmac@hp.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=w.landgraf@ru.ru \
    /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.