From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76320] New: libpciaccess seems to require xorg-macros for no reason
Date: Tue, 18 Mar 2014 14:02:37 +0000 [thread overview]
Message-ID: <bug-76320-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1244 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76320
Priority: medium
Bug ID: 76320
Assignee: dri-devel@lists.freedesktop.org
Summary: libpciaccess seems to require xorg-macros for no
reason
Severity: normal
Classification: Unclassified
OS: All
Reporter: kallisti5@unixzen.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: libdrm
Product: DRI
Looking at libpciaccess, the configure.ac seems to require xorg-macros when it
is not needed in any way shape or form. Removing the xorg-macros still results
in a functioning build.
I did have to disable the man pages, this may not be related though:
make[2]: Entering directory `/home/e1529750/Code/libpciaccess-0.13.2/man'
/bin/sed < scanpci.man > scanpci.
Usage: /bin/sed [OPTION]... {script-only-if-no-other-script} [input-file]...
-n, --quiet, --silent
suppress automatic printing of pattern space
Mentioning this as libdrm is supposed to not rely on xorg to function, but it
relies on libpciaccess which requires xorg-macros.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2541 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-03-18 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 14:02 bugzilla-daemon [this message]
2014-03-26 15:42 ` [Bug 76320] libpciaccess requires xorg-macros when it may not be available on all target platforms (ones lacking Xorg) bugzilla-daemon
2014-03-26 20:23 ` bugzilla-daemon
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=bug-76320-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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