public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Parkhurst" <brianp@spamcop.net>
To: <kloeri@gentoo.org>, <gentoo-alpha@lists.gentoo.org>
Subject: Re: [gentoo-alpha] ebuild update for Xorg-x11
Date: Tue, 26 Oct 2004 20:56:45 -0700	[thread overview]
Message-ID: <000a01c4bbd8$ffee16a0$3301a8c0@ICHIRO> (raw)
In-Reply-To: 20041027023635.GB2649@n610c.example.org

Thanks for the clarification.  Some of the information floating around out
there is a bit vague and piecing together an answer has been somewhat of a
challenge.  You did it in about 2 paragraphs.

This really answers most of the questions I've been trying to figure out for
the last many months.  I new it had to be possible as X was running on this
machine (Compaq RH 7.3 distro), prior to my building out the Gentoo.

Things to do on my part:

1.    Check my kernel build to confirm the floating point completion is
enabled in kernel
2.    Add mieee to my CFLAGS (my CXXFLAGS pick-up my CFLAGS)
3.    Try the USE="dlloader" flag
3a.    alternatively try patching the Xorg elf-loader

Brian Parkhurst.


----- Original Message ----- 
From: <kloeri@gentoo.org>
To: <gentoo-alpha@lists.gentoo.org>
Sent: Tuesday, October 26, 2004 7:36 PM
Subject: Re: [gentoo-alpha] ebuild update for Xorg-x11


> Just to clear up any possible confusion regarding both -mieee and PIC
code.
>
> Alpha processors prior to ev6 require a little help from libc / the kernel
to be IEEE compatible. Most code require this as Aron already mentioned. You
need to add -mieee to CFLAGS and it's cousin CXXFLAGS as well as enable
floating point completion in the kernel for this to work. Stuff like opengl
will probably break without this support.
>
> Regarding the possible PIC issues: shared libraries should be
compiled -fPIC (or -fpic) or you'll get linking errors on some archs. x86 is
mostly unaffected by this but you'll find that alpha complains loudly if
you'll try to link PIC and non-PIC code. Usually this results in errors
during the compilation aborting your emerge. Xfree and xorg-x11 is a little
different as it loads the driver modules dynamically at run-time using it's
own elf loader. This is also the reason that you'll see 'unsupported elf
relocation type' errors - the built-in elf loader doesn't support all the
relocation types that binutils does.
>
> There's basically two ways to solve this:
> 1. Patch the X elf loader to support all relocation types. There's some
patches floating around already that does this - at least to some extent.
> 2. Use dlload() instead of the built-in elf loader. You can turn on this
behaviour using USE="dlloader" and remerging xfree / xorg-x11. Beware that
this hasn't received as much testing yet as the built-in elf loader but it's
used by the Gentoo hardened project at least.
>
> Hope this clears up the confusion (if any).
>
> Regards,
> Bryan Ã~stergaard
> Gentoo/Alpha developer
>
> --
> gentoo-alpha@gentoo.org mailing list
>
>


--
gentoo-alpha@gentoo.org mailing list


  reply	other threads:[~2004-10-27  3:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 17:20 [gentoo-alpha] ebuild update for Xorg-x11 Brian C. Parkhurst
2004-10-26 20:15 ` Jeff Donsbach
2004-10-26 21:22   ` Aron Griffis
2004-10-26 21:35     ` Jeff Donsbach
2004-10-26 22:36     ` Brian C. Parkhurst
2004-10-26 23:04       ` Aron Griffis
2004-10-26 23:19         ` Brian Parkhurst
2004-10-27  2:36           ` kloeri
2004-10-27  3:56             ` Brian Parkhurst [this message]
2004-10-27  4:47           ` Jeff Donsbach
2004-10-27 14:23             ` Aron Griffis
2004-10-27 15:17               ` Jeff Donsbach
2004-11-22  0:11                 ` [gentoo-alpha] 2.6.9-gentoo-r4 kernel on Alpha issues? Brian Parkhurst
2004-11-22 17:11                   ` Brian Parkhurst
2004-10-27  4:43         ` [gentoo-alpha] ebuild update for Xorg-x11 Jeff Donsbach
2004-10-26 21:17 ` Aron Griffis

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='000a01c4bbd8$ffee16a0$3301a8c0@ICHIRO' \
    --to=brianp@spamcop.net \
    --cc=gentoo-alpha@lists.gentoo.org \
    --cc=kloeri@gentoo.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