RE: SAP DB 7.4 build problems on Red Hat Linux 8.0
Marko Asplund <[email protected]> Fri, 21 Mar 2003 14:24:45 +0200 (EET)
| Newsgroups | gmane.comp.db.sapdb.sources |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 20 Mar 2003, Dittmar, Daniel wrote: > ... > Building should also work with Python 2.2 and Perl 5.6, although this is rarely tested. We're currently in the process of making the buid scripts compatible with Perl 5.8. the build scripts could very well work with Python v2.2 but the problem is that $TOOL/installtools.pl tries to find config.h which Python v2.2 (or at least the Red Hat 8 package) doesn't have at all (include and lib paths might be non-standard as well). as to the Perl v5.8.0 here's the error message i got: cpcdrv.lnk fast Can't load '/home/aspa/tmp/sapdb/sapdb-7.4/DevTool/lib/perl5/PipeExec.so\ ' for module SAPDB::Install::PipeExec: /home/aspa/tmp/sapdb/sapdb-7.4/De\ vTool/lib/perl5/PipeExec.so: undefined symbol: PL_sv_undef at /usr/lib/p\ erl5/5.8.0/i386-linux-thread-multi/DynaLoader.pm line 229. at /home/aspa/tmp/sapdb/sapdb-7.4/DevTool/lib/perl5/SAPDB/Install/SysI\ nfo.pm line 31 Compilation failed in require at /home/aspa/tmp/sapdb/sapdb-7.4/DevTool\ /lib/perl5/SAPDB/Install/SysInfo.pm line 31. Compilation failed in require at /home/aspa/tmp/sapdb/sapdb-7.4/DevTool\ /bin/ToolLib.pm line 266. COMMAND error 255 this seems more like a dynamic loading incompatibility issue than a problem with the script syntax itself. > > 1) > > !dbmcli -s -R $INSTROOT inst_reg -k $INSTROOT -c > > ERR > > -24994,ERR_RTE: runtime environment error > > 1,mkstemp failed:Permission denied > > COMMAND error 1 > > 'reginst.mac' not made because of dependency errors > > Assuming that you haven't installed the binary version of SAP DB before, there are some directories missing. You can create them through the script $TOOL/bin/prepare_inst.pl, which must be executed as root. You could also set the environment variable NOREG, but then you couldn't actually use the software you just build, you could only package it. i ran $TOOL/bin/prepare_inst.pl but it doesn't seem to have an effect on this problem. i'm running the build as a normal user, should i do it with root? which directory is the build system trying to access here? > ... > > 4) > > bison: output.c:1236: output_parser: Assertion > > `actions_dumped == 1' fa\ > > iled. > > error while executing > > /home/aspa/tmp/sapdb/sapdb-7.4/DevTool/gnu/bin/bi\ > > son -v -o vls14_parse.c -d vls14_parse.y : > > COMMAND error 255 > > FlexLexer.h > > vls14_scan.skl fast binary > > vls14_parse.y fast > > vls14_parse.y:1310: warning: previous rule lacks an ending `;' > > vls14_parse.y:1313: warning: previous rule lacks an ending `;' > > vls14_parse.y:1384: warning: previous rule lacks an ending `;' > > bison: output.c:1236: output_parser: Assertion > > `actions_dumped == 1' fa\ > > iled. > > error while executing > > /home/aspa/tmp/sapdb/sapdb-7.4/DevTool/gnu/bin/bi\ > > son -v -o vls14_parse.c -d vls14_parse.y : > > COMMAND error 255 > > 'vls14_scan.l' not made because of dependency errors > > Our bison input requires an older version of bison. I thought that it's part of the build tools, but apparently, it ain't. I'll put that version on the ftp server. i installed GNU Bison v1.28 which made this problem go away. best regards, -- aspa http://www.kronodoc.fi/