unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: David De La Harpe Golden <david@harpegolden.net>
Cc: 10313@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
	Manuel Giraud <manuel@ledu-giraud.fr>
Subject: bug#10313: configure fails to find include path on openbsd
Date: Mon, 02 Jan 2012 13:42:35 -0500	[thread overview]
Message-ID: <xbhb0eeyjo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4EF549AC.3050104@harpegolden.net> (David De La Harpe Golden's message of "Sat, 24 Dec 2011 03:40:28 +0000")


I agree that the Emacs build process should not add /usr/local back to
the include etc paths if the BSDs have decided to remove it.
(I assume this is true for all of them, not just OpenBSD?)

So rather than adding this patch, I suggest doing nothing for Emacs
24.1, but after that actually removing the existing configure.in piece
that sets LD_SWITCH_SYSTEM to /usr/local/lib for freebsd.

Does the same apply to /usr/pkg for netbsd (see configure.in)?


Though it seems odd to me to have a system where gcc does not look in
/usr/local, yet that is where packages get installed. If I were using
such a system, I'd just end up putting /usr/local in CPPFLAGS and
LDFLAGS all the time. Are things in /usr/local found at run-time, or do
they also have to set LD_LIBRARY_PATH, or use -rpath as well during
compilation (the netbsd entry in configure.in uses the latter)?





  reply	other threads:[~2012-01-02 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 10:51 bug#10313: 24.0.92; configure fails to find include path on openbsd Manuel Giraud
2011-12-17  1:23 ` bug#10313: " Paul Eggert
2011-12-17  3:07   ` Glenn Morris
2011-12-24  3:40   ` David De La Harpe Golden
2012-01-02 18:42     ` Glenn Morris [this message]
2012-01-02 18:51       ` Paul Eggert
2012-01-02 20:54       ` David De La Harpe Golden
2012-01-02 21:51       ` David De La Harpe Golden
2012-01-03 14:10     ` Manuel Giraud
2012-01-09 16:43     ` Manuel Giraud
2012-01-09 17:12       ` Paul Eggert

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xbhb0eeyjo.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=10313@debbugs.gnu.org \
    --cc=david@harpegolden.net \
    --cc=eggert@cs.ucla.edu \
    --cc=manuel@ledu-giraud.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).