From: Sven Joachim <svenjoac@gmx.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: X11R7 failure
Date: Thu, 22 Apr 2010 20:36:21 +0200 [thread overview]
Message-ID: <87pr1r72sa.fsf@turtle.gmx.de> (raw)
In-Reply-To: <87633jtl2x.fsf@stupidchicken.com> (Chong Yidong's message of "Thu, 22 Apr 2010 14:10:14 -0400")
On 2010-04-22 20:10 +0200, Chong Yidong wrote:
> I just got a build failure report from one of the pretesters:
>
>> I have just looked at the failure to build it on NetBSD 5.0.2
>> AMD64, our first system with X11R7. The configure script fails to
>> detect the presence of X11 libraries, even though they are present:
>>
>> % ls -1 /usr/X11R7/lib/lib* | wc -l
>> 323
>
> I don't know if there is anything we can do about this, since the X11
> checks are made by Autoconf. We're using Autoconf 6.2 for emacs-23, but
> glancing at the output of Autoconf 6.5 from the trunk, looks like it
> doesn't look for /usr/X11R7 either.
It is version 2.65 (not 6.5), and this version does look in /usr/X11R7:
,----
| % grep -n X11R7 configure
| 6987:/usr/X11R7/include
| 6993:/usr/include/X11R7
| 6999:/usr/local/X11R7/include
| 7005:/usr/local/include/X11R7
`----
> I'm not using X11R7 yet, but my impression was that it isn't supposed to
> live under /usr/X11R7, but directly in /usr. Does anyone know what the
> situation is?
The standard installation directory for X.Org is /usr, but NetBSD
apparently uses /usr/X11R7. The autoconf changelog mentions that it
caters to that since version 2.64:
2009-05-11 Patrick Welche <prlw1@cam.ac.uk> (tiny change)
Also try X11R7 when looking for X11 files, for NetBSD.
* lib/autoconf/libs.m4 (_AC_PATH_X_DIRECT): Also try directories
with X11R7 in the name.
Sven
prev parent reply other threads:[~2010-04-22 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 18:10 X11R7 failure Chong Yidong
2010-04-22 18:36 ` Sven Joachim [this message]
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=87pr1r72sa.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.