I can confirm this appears to be fixed in the "1.5a1r4236M" tarball which Jeff provided.

-Paul

On 1/31/2012 11:46 PM, Brice Goglin wrote:
I fixed this one, thanks.
Brice



Le 01/02/2012 03:50, Paul H. Hargrove a écrit :
The problem I described below is ALSO present in hwloc-1.4
-Paul

On 1/31/2012 5:19 PM, Paul H. Hargrove wrote:
On my old Red Hat 8 box, I see the following failure from "make
install" of hwloc-1.3.1:

make[5]: Entering directory
`/home/pcp1/phargrov/OMPI/hwloc-1.3.1-linux-x86-32-elan/BLD/tests/linux'

/bin/sed -e 's/abs_top_builddir\/utils/bindir/' -e
'/abs_top_builddir/d' -i /home/pcp1/phargrov/OMPI/hwloc-1.3
.1-linux-x86-32-elan/INST/bin/hwloc-gather-topology
/bin/sed: invalid option -- i
Usage: /bin/sed [OPTION]... {script-only-if-no-other-script}
[input-file]...

   -n, --quiet, --silent
                  suppress automatic printing of pattern space
   -e script, --expression=script
                  add the script to the commands to be executed
   -f script-file, --file=script-file
                  add the contents of script-file to the commands to
be executed
       --help     display this help and exit
   -V, --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

E-mail bug reports to: bug-gnu-ut...@gnu.org .
Be sure to include the word ``sed'' somewhere in the ``Subject:''
field.
 From that usage output, I suspect hwloc shouldn't be using "-i".

Version on the failing system is "GNU sed version 3.02".
So, this portion of the Makefile should be rewritten not to use the
-i (in-place) option which appears specific to GNU sed-4.x

-Paul



--
Paul H. Hargrove                          phhargr...@lbl.gov
Future Technologies Group
HPC Research Department                   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

Reply via email to