public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: Adam Jackson <ajax@redhat.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [BUG] intel_drv.so fails to load
Date: Thu, 19 Jul 2012 08:04:25 +0200	[thread overview]
Message-ID: <5007A369.70908@t-online.de> (raw)
In-Reply-To: <1342640090.3590.61.camel@atropine>

Am 18.07.2012 21:34, schrieb Adam Jackson:
> So, one difference between the driver you built and the driver in
> factory:
>
> http://download.opensuse.org/pub/opensuse/factory/repo/oss/suse/i586/xf86-video-intel-2.20.0-1.1.i586.rpm
>
> Is that yours has this, and theirs doesn't:
>
> hate:~% eu-readelf -a intel_drv.so | grep TEXTREL
>    TEXTREL
>    FLAGS             TEXTREL
>
> This suggests that you managed to build the X driver without -fPIC, and
> eu-findtextrel(1) agrees.  This would cause the problem if text
> relocations are also not lazy, and I believe that to be the case. [1]
> To verify this assumption you could just jam -fPIC into CFLAGS and see
> if the result works, but that's just papering over the bug, not
> necessarily a fix.

Argh. Adding -fPIC to the flags of an icecream compile run does help.
Somehow. dlopen no longer fails and the build succeeds. kde4init
hangs forever without any error message, but it is possible for programs
started at the framebuffer console to use the X server. I´ll have to investigate
this issue further.

cu,
  Knut
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2012-07-19  6:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 20:08 [BUG] intel_drv.so fails to load Knut Petersen
2012-07-17 20:16 ` Chris Wilson
2012-07-17 20:41   ` Chris Wilson
2012-07-17 20:54     ` Knut Petersen
2012-07-17 21:11       ` Adam Jackson
2012-07-17 21:34         ` Knut Petersen
2012-07-17 21:16       ` Chris Wilson
2012-07-17 21:52         ` Knut Petersen
2012-07-18 14:02         ` Adam Jackson
2012-07-18 14:07           ` Chris Wilson
2012-07-18 14:29             ` Adam Jackson
2012-07-18 14:36               ` Chris Wilson
2012-07-18 19:47                 ` Adam Jackson
2012-07-18 22:34                   ` Chris Wilson
2012-07-19 14:08                     ` Adam Jackson
2012-07-18 18:04               ` Knut Petersen
2012-07-18 19:34                 ` Adam Jackson
2012-07-19  6:04                   ` Knut Petersen [this message]
2012-07-20 12:03               ` Knut Petersen
2012-07-20 15:10                 ` Adam Jackson
2012-07-20 16:01                   ` Knut Petersen
2012-07-17 20:41   ` Knut Petersen

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=5007A369.70908@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=ajax@redhat.com \
    --cc=intel-gfx@lists.freedesktop.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