Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001218]: PATCH: X.org xkbcomp library path issues
Date: Wed, 14 Feb 2007 01:11:05 -0800	[thread overview]
Message-ID: <8b34e6b4f9aa5da55f2d419b0dfb4f50@busybox.net> (raw)


The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1218 
====================================================================== 
Reported By:                foogod
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1218
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             02-14-2007 01:11 PST
Last Modified:              02-14-2007 01:11 PST
====================================================================== 
Summary:                    PATCH: X.org xkbcomp library path issues
Description: 
The X.org 6.8.2 source needs to build a native version of the xkbcomp
utility during cross-compilation.  To do this, it attempts to link it with
libxkbfile and libX11 from the build system, which it assumes will be found
in /usr/X11R6/lib.

The attached patch adds /usr/lib to the search path for those people using
distributions that put the X libraries in /usr/lib instead of /usr/X11/lib.
 Note that it is still necessary to have the appropriate devel package for
libxkbfile and libX11 installed in order to build properly.

This is all rather broken anyway, as the X sources are blindly assuming
that the host system not only has X libraries installed but that they're
going to be compatible with the utilities (from a potentially different X
distribution) that are being built.  A more correct solution would be to
modify things to build a host version of libxkbfile and libX11 from the
6.8.2 sources and link to those (but that's a much larger endeavor, and if
I'm going to work on that sort of thing I think I'll just start over with
the newer 7.1 sources, which I'll probably look into shortly.)

But anyway, this patch at least allows X to compile on my system (Ubuntu
Edgy)..
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-14-07 01:11  foogod         New Issue                                    
02-14-07 01:11  foogod         Status                   new => assigned     
02-14-07 01:11  foogod         Assigned To               => buildroot       
02-14-07 01:11  foogod         File Added: buildroot.17879.xorg_xkbcomp.patch   
                
======================================================================

                 reply	other threads:[~2007-02-14  9:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8b34e6b4f9aa5da55f2d419b0dfb4f50@busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /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