[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051003: Compiling McIDAS on FC4 64bit (cont.)



>From: =?ISO-8859-1?Q?Christian_Pag=E9?= <address@hidden>
>Organization:  UQAM
>Keywords:  200510031831.j93IVMG7009290 McIDAS Fedora Core 4

Hi Christian,

re:
>I got further, but had this...

>g77 -v -g -s -O -o decoder decoder.o -L. -L/usr/X11R6/lib -lsdi
>-lmcidas -ldl -lm
>Driving: g77 -v -g -s -O -o decoder decoder.o -L. -L/usr/X11R6/lib
>-lsdi -lmcidas -ldl -lfrtbegin -lg2c -lm -lg2c -lm -shared-libgcc
>Reading specs from /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/specs
>Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
>--infodir=/usr/share/info --enable-shared --enable-threads=posix
>--disable-checking --with-system-zlib --enable-__cxa_atexit
>--enable-languages=c,c++,f77 --disable-libgcj
>--host=x86_64-redhat-linux
>Thread model: posix
>gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-47.fc4)
> /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/collect2 --eh-frame-hdr -m
>elf_x86_64 -Y P,/usr/lib64 -dynamic-linker /lib64/ld-linux-x86-64.so.2
>-o decoder -s /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/crt
> 1.o
>/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/crti.o
>/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/crtbegin.o -L.
>-L/usr/X11R6/lib -L/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3
>-L/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64
>-L/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../.. -L/lib/../lib64
>-L/usr/lib/../lib64 decoder.o -lsdi -lmcidas -ldl -lfrtbegin -lg2c -lm
>-lg2c -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
>/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/crtend.o
>/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/crtn.o
>decoder.o(.text+0x16bd): In function `end_of_line':
>/kepler/mcidas/mcidas2005/src/decoder.c:983: undefined reference to `wnvblk_'
>collect2: ld returned 1 exit status
>link    decoder:                FAILED

Hmm...  I sent you the previous note after doing a build on my
dual 3.2 Ghz FC4 64-bit work machine on which I had run into the same
problem you were reporting.  I figured that if adding the '-j 1' flag
to make worked on my machine it should also work on yours, but it
evidently did not/not entirely.

The wnvblk_ entry point is contained in the wnvblk.o object module.
Try adding that module to the McIDAS library and continuing make:

<as 'mcidas'>
cd ~mcidas/mcidas2005/src

ar r libmcidas.a wnvblk.o
ranlib libmcidas.a

make -j 1

 -- or --

make -j 1 all

Follow this same procedure for each additional missing entry point
you run into.

Again, please let me know if this works for you.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.

>From address@hidden  Mon Oct  3 18:42:52 2005

Hi Tom,

It is pretty awkward that even with -j 1, it still breaks the
compilation sequence...
But your suggestion did work!!

Many thanks,

Christian


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.