public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Luca Contini" <luca.contini@mediaenabling.com>
To: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
Cc: MTD-Linux <linux-mtd@lists.infradead.org>
Subject: Re: missing function 'unlikely'
Date: Mon, 15 Sep 2003 10:23:55 +0200	[thread overview]
Message-ID: <020901c37b62$b3ef9420$a970a8c0@topo> (raw)
In-Reply-To: a05200f3ebb8347166dbf@[130.161.115.44]

> At 10:12 +0200 09-09-2003, Luca Contini wrote:
> >Hi all,
> >I've downloaded the snapshot 2003-08-28 and I'm trying to use it with
kernel
> >2.4.18.
> >The mtdblock module is compiled with no problems but when i try to insert
it I
> >get this error:
> >'unresolved symbol unlikely'
> >I've done a grep on the entire kernel tree but with no result.
>
> Which version of gcc are you using ?
>
> unlikely() is an optimization hint to the compiler, telling it that
> the conditional statement in question is expected to be false.
>
> As a hack, you can disable it by including
>
> #define unlikely(x) (x)
>
> in the affected source files. I would suggest upgrading your tools,
though.

Hi,
thank you very much, I've successfully fixed the above problem... but there
is another one:

** mtd_blkdevs.o: unresolved symbol mtd_table_mutex **
** mtd_blkdevs.o: unresolved symbol mtd_table **

The mtdcore.c source should export those symbols... but there is no way to
insert mtd_blkdevs.o module without this error.
Any suggestion?


Luca

>
> HTH,
>
> JDB.
> -- 
> LART. 250 MIPS under one Watt. Free hardware design files.
> http://www.lart.tudelft.nl/
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>

      reply	other threads:[~2003-09-15  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09  8:12 missing function 'unlikely' Luca Contini
2003-09-09  9:14 ` J.D. Bakker
2003-09-15  8:23   ` Luca Contini [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='020901c37b62$b3ef9420$a970a8c0@topo' \
    --to=luca.contini@mediaenabling.com \
    --cc=bakker@thorgal.et.tudelft.nl \
    --cc=linux-mtd@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox