|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
380 herc linux install issueshi,
i tried upgrading my tk3 install to mvs380. no happy ending. the chart at http://mvs380.sourceforge.net/s380diagram.html shows: 1) Hercules-3.06 http://www.hercules-390.org/hercules-3.06-native.zip this has no source code and is setup for Windows. 2) Hercules380-3_06-6_0.zip http://downloads.sourceforge.net/(...)hercules380-3_06-6_0.zip this has no source code and is setup for Windows. 3) Turnkey-3.iso http://www.ibiblio.org/jmaynard/turnkey-mvs-3.zip this has herc source code, both 2.16.2 and 2.16.5 releases. but if i use ubuntu's package manager (Synaptic), it shows "hercules 3.05-2" as the latest release. exactly what level is the hercules source? i downloaded (both LX64 and LX86 versions of) hercules-SVN-5482.tar.gz, but since i used Synaptic to install the package - which it said was at 3.05-2, i didn't install the 2.16.5 release from the ibiblio .zip file (it appeared to be downlevel). however, Synaptic's hercules-3.05-2 runs, using the tk3 mvs3.8j package. 4) mvs380-1_0.zip http://downloads.sourceforge.net/sourceforge/mvs380/mvs380-1_0.zip in this .zip's install directory, there is a file, inst380.txt, which states: Now install the S/380 version of Hercules, ie Hercules/380 cd\ md herc380 cd herc380 unzip INSTALL_FROM\hercules380-3_06-4_0 (or later). Note that Unix users will need to recompile Hercules/380 themselves, after applying the patch file as per the instructions in the README.S380 in the Hercules/380 archive. but the patch file to which it refers, hercules380-3_06-6_0, is step 2, which is a .zip file that is setup for Windows, and the only file which makes any sense to an *ix user is hercules380-3_06-6_0.txt, which states: + http://www.hercules-390.org + + to support the S/380 architecture. + + If you wish to recreate the source code (Unix users + must do this), you will need to go there and download so now i've got to go back and glom the source from hercules-390.org? is the 3.05-2 release given me by ubuntu's Synaptic newer? more comprehensive? more/less features? despite my confusion on the source issue, i followed the herc380 stuff and did an autoconf-configure-make-install process of the source from the hercules-3.06 file i glommed from ibiblio (latest file contained within is panel.c, dated 2009/01/20@12:18:34): - the first time, it finished through make install; - then i read the patch should go on first, so i applied the patch (but had to use the cmd, "patch -p1 -i <file>", as it hung in "waiting for terminal input" mode without the -i); and - the second time (after the patch), it failed, with this: ./.libs/libherc.so: undefined reference to `s370_trace_svc_return' ./.libs/libherc.so: undefined reference to `s370_trace_task_dispatch' ./.libs/libherc.so: undefined reference to `s370_trace_initial_srb_dispatch' ./.libs/libherc.so: undefined reference to `s370_trace_io_interruption' ./.libs/libherc.so: undefined reference to `s370_trace_program_interruption' ./.libs/libherc.so: undefined reference to `s370_trace_svc_interruption' further restores of the /herc380 directory from both the ibiblio's 3.06 and then hercules380-3_06-6_0 followed by patch / autoconf / ./configure / make yield "error 2" and "error 1": if gcc -DHAVE_CONFIG_H -I. -I. -I. -I. -I./decNumber -W -Wall -O3 -march=k8 -fomit-frame-pointer -MT hdlmain.o -MD -MP -MF ".deps/hdlmain.Tpo" -c -o hdlmain.o hdlmain.c; \ then mv -f ".deps/hdlmain.Tpo" ".deps/hdlmain.Po"; else rm -f ".deps/hdlmain.Tpo"; exit 1; fi rm: cannot remove `hercules': Is a directory make[2]: *** [hercules] Error 1 make[2]: Leaving directory `/herc380' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/herc380' make: *** [all] Error 2 i'm sure i've made errors in this process, despite trying to follow the MVS-380 instructions to the letter. if someone could please lmk where i went wrong, i could write up really precise, clear information, and i'm willing to maintain it as the various herc / mvs(flavor) releases and source change. tia yvette |
|
|
Re: 380 herc linux install issues--- In hercules-390@..., yvette hirth <yvette@...> wrote:
> > i tried upgrading my tk3 install to mvs380. no happy ending. > 2) Hercules380-3_06-6_0.zip > http://downloads.sourceforge.net/(...)hercules380-3_06-6_0.zip Please don't post about the Hercules derivative here. If you can reproduce a problem on normal Hercules, that is fine, but the Hercules developers don't support or endorse 380. > so now i've got to go back and glom the source from hercules-390.org? Yes. > is the 3.05-2 release given me by ubuntu's Synaptic newer? more > comprehensive? more/less features? > > despite my confusion on the source issue, i followed the herc380 stuff > and did an autoconf-configure-make-install process of the source from > the hercules-3.06 file i glommed from ibiblio (latest file contained > within is panel.c, dated 2009/01/20@12:18:34): You can't use the latest daily snapshot. You must use the one and only official 3.06 release. Go to http://www.hercules-390.org/ and see where it says "source tarball". Here's an exact link: http://www.hercules-390.org/hercules-3.06.tar.gz I suggest you make sure this builds on its own first, because you might be the first person to try 380 on your flavour of Unix. Any problem regarding the building of official 3.06 on your environment is on-topic here though. BFN. Paul. |
|
|
Re: 380 herc linux install issuesOn Wednesday, October 14, 2009 yvette hirth wrote:
> i tried upgrading my tk3 install to mvs380. no happy ending. Hello Yvette, mvs380 uses a modified version of Hercules which is not supported by the hercules-390 project. Problems installing mvs380 are probably best dealt with on the mvs380 support forum at http://groups.yahoo.com/group/hercules-os380 -- Regards, Roger Bowler http://perso.wanadoo.fr/rbowler Hercules "I can't believe it's not a mainframe!" |
| Free embeddable forum powered by Nabble | Forum Help |