Make sure you rm ${PETSC_ARCH}/conf/prometheus before running. Removing the
external package is not enough to force a rebuild.
Barry
On Aug 30, 2011, at 1:58 PM, Satish Balay wrote:
> Mark,
>
> can you retry with latest petsc-dev and send us logs to petsc-maint -
> if this issue perisists? [so I can reporoduce]
>
> thanks,
> Satish
>
> On Tue, 30 Aug 2011, Mark F. Adams wrote:
>
>> I got a somewhat similar error on my Mac this AM when configuring with
>> prometheus:
>>
>> Undefined symbols:
>> "_isend_len", referenced from:
>> _isend_len$non_lazy_ptr in libpromfei.a(Prometheus_LinSysCore.o)
>> _isend_len$non_lazy_ptr in libprometheus.a(prometheus.o)
>> _isend_len$non_lazy_ptr in libprometheus.a(prom_kkt.o)
>> .....
>>
>> I tried deleting externalpackages and reconfiguring, no luck, so
>> reconfigured w/o prometheus and it worked.
>>
>> Mark
>>
>> On Aug 30, 2011, at 2:23 PM, Jed Brown wrote:
>>
>>> On Tue, Aug 30, 2011 at 13:20, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>> In file included from
>>> /sandbox/petsc/petsc-dev-2/src/sys/comm/sectioncopy.c:3:
>>> /sandbox/petsc/petsc-dev-2/include/sieve/BasicCommunication.hh: In member
>>> function ?void ALE::MPIMover<Value_>::constructRequests()?:
>>> /sandbox/petsc/petsc-dev-2/include/sieve/BasicCommunication.hh:133: error:
>>> ?isend_ct? was not declared in this scope
>>> /sandbox/petsc/petsc-dev-2/include/sieve/BasicCommunication.hh:134: error:
>>> ?isend_len? was not declared in this scope
>>> /sandbox/petsc/petsc-dev-2/include/sieve/BasicCommunication.hh:149: error:
>>> ?irecv_ct? was not declared in this scope
>>> /sandbox/petsc/petsc-dev-2/include/sieve/BasicCommunication.hh:150: error:
>>> ?irecv_len? was not declared in this scope
>>>
>>> Fixed here, as noted in my buildbot reply on petsc-maint this morning.
>>>
>>> http://petsc.cs.iit.edu/petsc/petsc-dev/rev/4f6483a470e2
>>
>>
