I removed the BSD option and reworked the sed commands. Sorry for the
mess.
On Sep 8, 2009, at 4:03 PM, William Kyngesburye wrote:
Oops, I think it's the OSX arch options I added this weekend - they
use the -E sed flag that's in BSD sed, but maybe not in GNU sed? I
wasn't sure if I should (or how) to only check those parts on OSX
(it does NOT have anything to do with the OSX app option). Or is
there an equivalent -E option that works in GNU and BSD?
Is it OK to check the $system var in configure.in, when it's
something that's created by an autocof macro? Or is there an AC
macro that can do something based on the system?
On Sep 8, 2009, at 3:49 PM, Hamish wrote:
Hi,
with latest svn when I try to ./configure trunk I get a whole pile of
sed usage errors:
checking whether to use Python... yes
checking for python-config... /usr/bin/python2.5-config
checking for Python.h... yes
sed: invalid option -- E
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-
file]...
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"Oh, look, I seem to have fallen down a deep, dark hole. Now what
does that remind me of? Ah, yes - life."
- Marvin
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
