On Dec 16, 2011, at 7:39 PM, Paul H. Hargrove wrote:
> I've noticed that on, for instance, FreeBSD I must compile openmpi-1.5.5rc1 with "gmake" rather than "make".
> I didn't see "GNU Make" listed as a build dependency in the README, and so I wonder if this was known.
> The failure mode seen with Berkeley Make in place of GNU Make is somewhat non-intuitive:
>> Making all in asm
>> CC asm.lo
>> /usr/bin/perl '/home/phargrov/OMPI//openmpi-1.5.5rc1/opal/asm/generate-asm.pl' 'AMD64' 'default-.text-.globl-:--.L-_at_-1-0-1-1-0' '/home/phargrov/OMPI//openmpi-1.5.5rc1/opal/asm/base' '../../opal/asm/generated/atomic-amd64-linux-nongas.s'
>> Use of uninitialized value $1 in concatenation (.) or string at /home/phargrov/OMPI//openmpi-1.5.5rc1/opal/asm/generate-asm.pl line 16.
>> Could not open ../../opal/asm/generated/atomic-amd64-linux-nongas.s:
>> *** Error code 2
> And I don't have any clue what the relation may be between that error and the version of make.
No, this is not desirable. Gah. :-(
Can you look in opal/asm/base/Maekfile and see what the values of OPAL_ASSEMBLY_ARCH and OPAL_ASSEMBLY_FORMAT are? Specifically: are they non-empty on these two cases?
I ask because the only place generate-asm.pl is invoked is via a Makefile rule:
$(PERL) '$(top_srcdir)/opal/asm/generate-asm.pl' '@OPAL_ASSEMBLY_ARCH@' '@OPAL_ASSEMBLY_FORMAT@' '$(top_srcdir)/opal/asm/base' '$(top_builddir)/opal/asm/generated/@OMPI_ASM_FILE@'
$1 should correspond to @OPAL_ASSEMBLY_ARCH@, and it should never be empty.
For corporate legal information go to: