Bugzilla Bug 220211

nco won't complete compilation.

Reproducible: Always

Steps to Reproduce:
1. emerge -a nco
Actual Results:  
if mpicc -DHAVE_CONFIG_H -I. -I. -I../..     -O2 -pipe -march=opteron -std=c99
-D_BSD_SOURCE -D_POSIX_SOURCE -MT ncwa.o -MD -MP -MF ".deps/ncwa.Tpo" -c -o
ncwa.o ncwa.c; \
        then mv -f ".deps/ncwa.Tpo" ".deps/ncwa.Po"; else rm -f
".deps/ncwa.Tpo"; exit 1; fi
 mpicc -DHAVE_CONFIG_H -I. -I. -I../.. -O2 -pipe -march=opteron -std=c99
-D_BSD_SOURCE -D_POSIX_SOURCE -MT nco_var_rth.lo -MD -MP -MF
.deps/nco_var_rth.Tpo -c nco_var_rth.c -o nco_var_rth.o >/dev/null 2>&1
mpncra.c: In function ‘main’:
mpncra.c:1207: error: too few arguments to function
‘nco_cnv_arm_time_install’
make[3]: *** [mpncra.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory
`/var/tmp/portage/sci-misc/nco-3.9.2/work/nco-3.9.2/src/nco'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/sci-misc/nco-3.9.2/work/nco-3.9.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/sci-misc/nco-3.9.2/work/nco-3.9.2'
make: *** [all] Error 2
 * 
 * ERROR: sci-misc/nco-3.9.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line  227:  Called die

Expected Results:  
Installation

Created an attachment (id=151783) [edit]
nco-3.9.2-emergeinfo_buildlog-2008.05.04_03:15:43.lzma

unlzma this file.

Thanks for your bug report. This looks like an mpi
problem. I've bumped nco to 3.9.4 in portage which
works fine for me using openmpi. Please give it a
shot and re-open should the problem persist.

BTW, next time please post your attachments in plain 
text unless they are huge (more than a few hundred kB 
or so).

Thanks,
Markus

(In reply to comment #2)
> Thanks for your bug report. This looks like an mpi
> problem. I've bumped nco to 3.9.4 in portage which
> works fine for me using openmpi. Please give it a
> shot and re-open should the problem persist.
> 
> BTW, next time please post your attachments in plain 
> text unless they are huge (more than a few hundred kB 
> or so).
> 
> Thanks,
> Markus
> 

Hi Markus,
Please understand that due the large volume and frequency of my submitting bug
reports, I created a script which automatically performs this function for me.
It is as much for my own interest and the process of transmission and storage,
that they are compressed using lzma. I think it's a simple thing to run unlzma
or lzcat on these files.

Shingoshi

Thanks! Excellent job. I'll look forward to working with you in the future.
Hopefully not for bugs though.

Shingoshi

(In reply to comment #3)
> I think it's a simple thing to run unlzma
> or lzcat on these files.

Only if I am at a full fledged box with these tools
installed. Not infrequently, I have to rely on a browser
only to do initial bug screenings and suggest things to
try. I won't be able to help in a timely manner in cases 
where important information is submitted in non-ASCII format.
Why don't you adjust your script to submit things as plain
text if their size doesn't exceed a certain limit?


Thanks again for your help.

cheers,
Markus 

I keep thinking that everyone spends their days like me, sitting in front of
their own computer. I'll try and figure out how to determine the size of the
file, and if it exceeds a certain value, then I'll compress it. Otherwise, I'll
leave them in plain-text (as default).

Shingoshi