From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8696] xdriver_xf86-input-mouse install header files in target directory
Date: Wed, 17 Feb 2016 10:21:28 +0000 [thread overview]
Message-ID: <bug-8696-163-BBx5ibwu2s@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8696-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8696
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
Status|NEW |ASSIGNED
--- Comment #5 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Yes, this has been the case for a long time now.
I even had a patch series to fix that once and for all:
http://lists.busybox.net/pipermail/buildroot/2015-November/143562.html
But it was dismissed in favour of Gustavoz' pkg-conf fixups. However,
that series did not completely fix the Xorg weirdness, but since it
was not causing regressions (i.e. the bad paths were prsent before and
after), the pkg-conf fixes were applied, and my series got forgotten.
I'll respin that in a moment...
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-02-17 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 11:55 [Buildroot] [Bug 8696] New: xdriver_xf86-input-mouse install header files in target directory bugzilla at busybox.net
2016-02-15 20:51 ` [Buildroot] [Bug 8696] " bugzilla at busybox.net
2016-02-15 20:55 ` bugzilla at busybox.net
2016-02-15 21:01 ` bugzilla at busybox.net
2016-02-15 21:24 ` bugzilla at busybox.net
2016-02-17 10:21 ` bugzilla at busybox.net [this message]
2016-03-10 14:46 ` bugzilla at busybox.net
2016-03-11 18:12 ` bugzilla at busybox.net
2016-10-23 9:37 ` bugzilla at busybox.net
2016-10-23 19:59 ` bugzilla at busybox.net
2016-10-23 20:09 ` bugzilla at busybox.net
2016-10-24 16:41 ` bugzilla at busybox.net
2016-10-26 20:38 ` bugzilla at busybox.net
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-8696-163-BBx5ibwu2s@https.bugs.busybox.net/ \
--to=bugzilla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.