From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77204] New: make fails due to wrong file names in man
Date: Tue, 08 Apr 2014 20:57:14 +0000 [thread overview]
Message-ID: <bug-77204-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1117 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=77204
Priority: medium
Bug ID: 77204
Assignee: dri-devel@lists.freedesktop.org
Summary: make fails due to wrong file names in man
Severity: normal
Classification: Unclassified
OS: All
Reporter: tamas.haraszti@uni-heidelberg.de
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: libdrm
Product: DRI
make fails with:
/bin/sed: can't read drm-mm.7: No such file or directory
looking into the man folder I can find:
Makefile drm-kms.7 drm-memory.xml drmAvailable.3 drmHandleEvent.xml
drm\-gem.7
Makefile.am drm-kms.xml drm.7 drmAvailable.xml
drmModeGetResources.3 drm\-mm.7
Makefile.in drm-memory.7 drm.xml drmHandleEvent.3
drmModeGetResources.xml drm\-ttm.7
Thus all MANPAGE_ALIASES contain an extra \.
Renaming the files allows the make to proceed.
System: gentoo linux, newest automake, cmake, bash...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2414 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-04-08 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 20:57 bugzilla-daemon [this message]
2014-04-08 21:12 ` [Bug 77204] make fails due to wrong file names in man bugzilla-daemon
2019-09-24 17:08 ` 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-77204-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 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.