From: ali@internetdog.org (Ali Bahar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problems with disabling Optimization
Date: Mon, 6 Jun 2011 10:52:47 +0800 [thread overview]
Message-ID: <20110606025247.GC15480@internetdog.org> (raw)
In-Reply-To: <BANLkTi=n2SMrvgdgZx66se+pu7VYDPBR3Q@mail.gmail.com>
> Disabling O2 and Os on Kernel building, I am getting the
> following error. Can you please help me in debugging this.
> ERROR: "intel_gmbus_is_forced_bit" [drivers/gpu/drm/i915/i915.ko] undefined!
> ERROR: "__udivdi3" [drivers/gpu/drm/i915/i915.ko] undefined!
> make[2]: *** [__modpost] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2
It's been a while since I (last) disabled these, but I did not run
into a compilation error because of it. And I recall the box needing
i915, too. Is this a case of simply needing to do a _clean_ build?
later,
ali
PS IIRC, a CONFIG option exists _but_ I also had to edit a makefile to
get everything disabled -- though don't ask me when and where that
was! :-)
next prev parent reply other threads:[~2011-06-06 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:28 Problems with disabling Optimization Prabhu nath
2011-06-02 14:49 ` Dave Hylands
2011-06-06 2:52 ` Ali Bahar [this message]
2011-06-06 5:12 ` Dave Hylands
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=20110606025247.GC15480@internetdog.org \
--to=ali@internetdog.org \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).