Link error: ./.libs/libherc.so: undefined reference to `s370_vm_blockio'

[Wendell Nichols]

Since my latest update/sync hercules no longer links.  Anybody else see
this or is it peculiar to my system?
wcn
gcc -W -Wall -O3 -march=k8 -fomit-frame-pointer .libs/herculesS.o
-Wl,--warn-common -o .libs/hercules bootstrap.o hdlmain.o -pthread
-pthread -Wl,--export-dynamic  ./.libs/libherc.so
/home/wcn00/src/hercules_trunk/.libs/libherct.so
/home/wcn00/src/hercules_trunk/.libs/libhercd.so
/home/wcn00/src/hercules_trunk/.libs/libhercu.so
/home/wcn00/src/hercules_trunk/.libs/libhercs.so
/home/wcn00/src/hercules_trunk/decNumber/.libs/libdecNumber.so
./.libs/libhercs.so -lpthread -lrt -lz -lresolv -lnsl -lm -ldl -lbz2
-Wl,--rpath -Wl,/usr/local/lib
./.libs/libherc.so: undefined reference to `s370_vm_blockio'
./.libs/libherc.so: undefined reference to `z900_vm_blockio'
./.libs/libherc.so: undefined reference to `s390_vm_blockio'
collect2: ld returned 1 exit status
gmake[2]: *** [hercules] Error 1
gmake[2]: Leaving directory `/local/home/wcn00/src/hercules_trunk'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/local/home/wcn00/src/hercules_trunk'
gmake: *** [all] Error 2

[Roger Bowler]

--- In hercules-390@..., Wendell Nichols wrote:
> Since my latest update/sync hercules no longer links.
> ./.libs/libherc.so: undefined reference to `s370_vm_blockio'
> ./.libs/libherc.so: undefined reference to `z900_vm_blockio'
> ./.libs/libherc.so: undefined reference to `s390_vm_blockio'

You need to run autogen.sh and configure to pick up recently added module vmd250.

Regards,
Roger Bowler

[Gregg C Levine-2]

Hello!
First things first. When did you last accomplish an update/synch? And on
what specie of Linux is this running on? Or are you not running on Linux,
but one of the examples of open source software out there.

I myself run Hercules on Slackware Linux, that's the 12.1 release. And I did
see something strange but that wasn't for a long time, when Harold came up
with the good work for running an Open Solaris port.

I've also seen some strange things, such as the recent ones described by
Fish and another gentleman.
--
Gregg C Levine hansolofalcon@...
"The Force will be with you always." Obi-Wan Kenobi
 


> -----Original Message-----
> From: hercules-390@... [mailto:hercules-390@...]
On
> Behalf Of Wendell Nichols
> Sent: Tuesday, October 13, 2009 10:22 AM
> To: hercules-390@...
> Subject: [hercules-390] Link error: ./.libs/libherc.so: undefined
reference to

> `s370_vm_blockio'
>
> Since my latest update/sync hercules no longer links.  Anybody else see
> this or is it peculiar to my system?
> wcn
> gcc -W -Wall -O3 -march=k8 -fomit-frame-pointer .libs/herculesS.o
> -Wl,--warn-common -o .libs/hercules bootstrap.o hdlmain.o -pthread
> -pthread -Wl,--export-dynamic  ./.libs/libherc.so
> /home/wcn00/src/hercules_trunk/.libs/libherct.so
> /home/wcn00/src/hercules_trunk/.libs/libhercd.so
> /home/wcn00/src/hercules_trunk/.libs/libhercu.so
> /home/wcn00/src/hercules_trunk/.libs/libhercs.so
> /home/wcn00/src/hercules_trunk/decNumber/.libs/libdecNumber.so
> ./.libs/libhercs.so -lpthread -lrt -lz -lresolv -lnsl -lm -ldl -lbz2
> -Wl,--rpath -Wl,/usr/local/lib
> ./.libs/libherc.so: undefined reference to `s370_vm_blockio'
> ./.libs/libherc.so: undefined reference to `z900_vm_blockio'
> ./.libs/libherc.so: undefined reference to `s390_vm_blockio'
> collect2: ld returned 1 exit status
> gmake[2]: *** [hercules] Error 1
> gmake[2]: Leaving directory `/local/home/wcn00/src/hercules_trunk'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory `/local/home/wcn00/src/hercules_trunk'
> gmake: *** [all] Error 2
>

[Gregg C Levine-2]

Hello!
Thank you Roger. That step slipped my mind. The last time I did that was the
first time I retrieved the first delivery from the SVN servers. I normally
run the configure scripts about twice during the cycle. One time after about
the first seven or eight retrievals, and the second time around when we get
a big update. That last one was based on the work Harold did for the Open
Solaris activities.

What I just posted goes into the other details, and naturally clews on the
displayed error indicated to me that we've got an interesting issue, that
since Hercules does run nearly everywhere, what can go wrong indeed. This is
evidenced on the issues for AIX of course. While we can't go about blaming
anyone named Murphy here, this is indeed an interesting issue.

Incidentally Vanya, I can't blame you for this, so you are off the hook.
Fish we've done good again.
--
Gregg C Levine hansolofalcon@...
"The Force will be with you always." Obi-Wan Kenobi
 


> -----Original Message-----
> From: hercules-390@... [mailto:hercules-390@...]
On
> Behalf Of Roger Bowler
> Sent: Tuesday, October 13, 2009 11:12 AM
> To: hercules-390@...
> Subject: [hercules-390] Re: Link error: ./.libs/libherc.so: undefined
reference to

> `s370_vm_blockio'
>
>
>
> --- In hercules-390@..., Wendell Nichols wrote:
> > Since my latest update/sync hercules no longer links.
> > ./.libs/libherc.so: undefined reference to `s370_vm_blockio'
> > ./.libs/libherc.so: undefined reference to `z900_vm_blockio'
> > ./.libs/libherc.so: undefined reference to `s390_vm_blockio'
>
> You need to run autogen.sh and configure to pick up recently added module

vmd250.
>
> Regards,
> Roger Bowler
>

[Wendell Nichols]

Thanks Roger.  Sorry if top posting is wrong here... the rules are
different all over :)
wcn

Roger Bowler wrote:

>  
>
>
>
> --- In hercules-390@...
> <mailto:hercules-390%40yahoogroups.com>, Wendell Nichols wrote:
> > Since my latest update/sync hercules no longer links.
> > ./.libs/libherc.so: undefined reference to `s370_vm_blockio'
> > ./.libs/libherc.so: undefined reference to `z900_vm_blockio'
> > ./.libs/libherc.so: undefined reference to `s390_vm_blockio'
>
> You need to run autogen.sh and configure to pick up recently added
> module vmd250.
>
> Regards,
> Roger Bowler
>
>