Date: Tue, 21 Dec 2004 00:04:19 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 479 ************************************************** Monday 20 December 2004 Number 479 ************************************************** Subjects for today 1 Re: octave port : John Poltorak 2 Re: postgreSQL progress : lsunley at mb.sympatico.ca 3 Re: Building SMAKE/STAR etc : John Poltorak 4 Re: octave port : Andy Willis 5 Re: octave port : Steven Levine" 6 Re: postgreSQL progress : lsunley at mb.sympatico.ca 7 GCC 335 Problem with dlopen DLL init : lsunley at mb.sympatico.ca 8 Re: GCC 335 Problem with dlopen DLL init : Jeff Robinson 9 checking for a BSD-compatible install : John Poltorak 1 Re: Building SMAKE/STAR etc : Dave Yeo" 2 Re: Building SMAKE/STAR etc : Yuri Dario" 3 Re: Building SMAKE/STAR etc : Dave Yeo" 4 postgreSQL v8.0 rc1 beta is released : lsunley at mb.sympatico.ca 5 Building PDKSH with GCC 3.3.5 : John Poltorak 6 Building Emacs : John Poltorak 7 Python modules in Apache : John Poltorak 8 Re: GCC 335 Problem with dlopen DLL init : Knut St. Osmundsen" 9 Re: postgreSQL progress : Knut St. Osmundsen" 10 Re: postgreSQL v8.0 rc1 beta is released : John Poltorak 14 Re: GCC 335 Problem with dlopen DLL init : lsunley at mb.sympatico.ca 10 Re: GCC 335 Problem with dlopen DLL init : lsunley at mb.sympatico.ca **= Email 1 ==========================** Date: Sun, 19 Dec 2004 14:22:31 +0000 From: John Poltorak Subject: Re: octave port On Sun, Dec 19, 2004 at 12:01:58AM -0800, Steven Levine wrote: > In <41C45B88.1030709 at comcast.net>, on 12/18/04 > at 09:32 AM, Andy Willis said: > > >I think the netlib package is probably required as I don't see any > >executable in the gcc package and if you tell Octave to use f2c it > >expects an executable. > > True. Klaus's 2.1.23 sources included source for all the required > subpackages, so building from source built f2c. I don't know anything at all about Octave, butam interested in trying to build it automatically from source if possible. Where do I get the source? > BTW, ISTR that I was able to build Octave using Klaus's distribution. If > you get to sticking points, I might be able to figure out what he tweaked. I'd be interested in any patches and build instructions too. I'd like to include it in UX2BS if possible. > Regards, > > Steven > > -- > ---------------------------------------------------------------------- > "Steven Levine" MR2/ICE 2.60b #10183 Warp4/FP15/14.100c_W4 > www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) > ---------------------------------------------------------------------- > -- John **= Email 2 ==========================** Date: Sun, 19 Dec 2004 09:59:08 -0500 From: lsunley at mb.sympatico.ca Subject: Re: postgreSQL progress In <41C5434F.2060200 at anduin.net>, on 12/19/04 at 09:01 AM, "Knut St. Osmundsen" said: >lsunley at mb.sympatico.ca wrote: >> Hi >> >> I'm not sure if he (Venuto) is still working on his port, that is one of >> the reasons I decided to port the new v8.0 postgreSQL. The new version 8.0 >> of the database seems to support all the version 7 stuff and also allows >> for tablespaces etc. See the postgreSQL main web site for the changes >> http://www.postgresql.org >> >> The port I am doing will support the full functionality of the v7 port and >> more. The new v8 code has .exe files instead of scripts for things line >> initdb, createuser, createdb etc, etc. That means that users do not have >> to have a *nix shell around to use the database. >> >> Right now it is all working with the exception of the statistics >> reporting. I have a bug in there but the database itself works and >> executes SQL. >> >> I am working on an install package for the code so I can send it out for >> testing and/or "non-critical" use. That should be ready to go tomorrow >> (and I hope those are not "famous last words"). >> >> The postgreSQL folks are agreeable with including my OS/2 patches into the >> official release after the v8.0 GA is done. That would mean v8.1 would >> have OS/2 support. >> >> This particular port is dependant on GCC 3.3.5 LIBC06 fork code. The fork >> stuff works well. The main hack I had to do was to partly implement sysV >> semaphores and shared memory handling, and attach the shared memory region >> after every fork() call. The standard fork() automatically attaches shared >> memory for child processes but Knut has not done that yet (probably >> because it requires a full implementation of the *nix IPC handling). >Did you make use of the Dos API extensions for managing shared memory? >If not: DosAllocSharedMemEx for alloc, DosGetSharedMemEx and >DosGetNamedSharedMemEx for getting, and DosFreeMemEx for freeing. Must >#define INCL_EXAPIS to get the prototypes from os2emx.h. >See the bottom of os2emx.h for descriptions details and >src/emx/src/lib/sys/Dos*Ex.c for implementation. >Yes, I need to do the IPC framework when adding any shm, msg and sem >implementation. And presently I don't really have any spare time for >doing that. >Kind Regards, > knut No I did not use the *Ex implementations. I'll do that today. It will eliminate a number of mods to the postgreSQL code and simplify the sem and shm implementation that I did. Thanks for pointing that out. By the time I finish cleaning up my sem and shm code, it should probably go a fair way to providing an IPC framework. You can have it if you want... Maybe I should read the documentation.... I would have to do less work that way :-) Lorne -- ----------------------------------------------------------- lsunley at mb.sympatico.ca ----------------------------------------------------------- **= Email 3 ==========================** Date: Sun, 19 Dec 2004 16:23:30 +0000 From: John Poltorak Subject: Re: Building SMAKE/STAR etc On Sat, Dec 18, 2004 at 07:26:17AM -0800, Dave Yeo wrote: > On Thu, 16 Dec 2004 09:21:06 +0000, John Poltorak wrote: > > >What changes need to be made to various utilities such as smake, star etc > >developed by Joerg Schilling to make them build on OS/2? > > > >They come with build instructions for OS/2 but I haven't managed to make > >them work. Has anyone else? > > Building smake-1.2a23 I needed star to unpack the tar archive > star -x -copylinks < smake-1.2a23.tar.gz (run twice so symlinks all > resolve) But don't you need smake before you can build star? Sounds like a catch-22 situation... > Then need to remove -Zexe from psmake/MAKE-sh and > RULES/i386-os2-gcc.rul > and run sh Gmake.linux. Install seems to be broken when using Gnu Make > so copy smake/OBJ/i386-os2-gcc/smake.exe to PATH (or perhaps use its > absolute location) then something like smake INS_BASE=/usr/local > install will install to /usr/local. The thing is it is supposed to work on OS/2 out of the box - it even has OS/2 specific build scripts which one assumes did work for someone at one point. I'd just to find out if they ever did work for anyone. If they are in the package they must be there for a reason. > To build smake with Innotek_libc you need to add -lsocket to the LIBS= > in smake/Makefile. > Star-1.4.3 builds fine using smake but smake install is broken so star > needs to be installed manually. Same problems with getting it extracted > correctly, I started out by untarring in Linux and zipping it up and > transferring to OS/2 > Star-1.4.3 also dies if built with innotek_libc due to a sigill > Star-1.5 does not build due to unresolved symbol _unlink. I did suceed > in building it with innotek_libc but all it did was segfault and I > haven't got around to debugging. > IIRC cdrtools-2.01 built fine here using smake That's good. I will have to give it a try. > Dave > -- John **= Email 4 ==========================** Date: Sun, 19 Dec 2004 10:08:30 -0700 From: Andy Willis Subject: Re: octave port John Poltorak wrote: >On Sun, Dec 19, 2004 at 12:01:58AM -0800, Steven Levine wrote: > > >>In <41C45B88.1030709 at comcast.net>, on 12/18/04 >> at 09:32 AM, Andy Willis said: >> >> >> >>>I think the netlib package is probably required as I don't see any >>>executable in the gcc package and if you tell Octave to use f2c it >>>expects an executable. >>> >>> >>True. Klaus's 2.1.23 sources included source for all the required >>subpackages, so building from source built f2c. >> >> > >I don't know anything at all about Octave, butam interested in trying to >build it automatically from source if possible. Where do I get the source? > > > http://www.octave.org/download.html Unfortunately, do to being lax on my backups I wasted time I would have spent working on this trying to restore files instead. I think there is a good chance of this building if I get f2c built. Andy **= Email 5 ==========================** Date: Sun, 19 Dec 2004 09:14:46 -0800 From: "Steven Levine" Subject: Re: octave port In <20041219142231.N32443 at warpix.org>, on 12/19/04 at 02:22 PM, John Poltorak said: >I don't know anything at all about Octave, butam interested in trying to >build it automatically from source if possible. Where do I get the >source? http://www.octave.org There is an extensive set of extensions available at: http://octave.sourceforge.net/ These are mostly scripts. >I'd be interested in any patches and build instructions too. I'd like to >include it in UX2BS if possible. The sources and working binaries are at: http://hobbes.nmsu.edu/pub/os2/apps/math/octave You will find that that the makefiles have been heavily modified, compared to the base versions. Regards, Steven -- ---------------------------------------------------------------------- "Steven Levine" MR2/ICE 2.60b #10183 Warp4/FP15/14.100c_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) ---------------------------------------------------------------------- **= Email 6 ==========================** Date: Sun, 19 Dec 2004 12:29:49 -0500 From: lsunley at mb.sympatico.ca Subject: Re: postgreSQL progress Hi Again I tried the *Ex API for both semaphores and shared memory. The postgres server started using up 100% of CPU on both CPUs of my test machine... I backed out the semaphore Ex API and still got the same 100% CPU. Backed out the shared memory Ex API and it works again Is there anything I can do to find out what is happening? Lorne In <41C5434F.2060200 at anduin.net>, on 12/19/04 at 09:01 AM, "Knut St. Osmundsen" said: >Did you make use of the Dos API extensions for managing shared memory? >If not: DosAllocSharedMemEx for alloc, DosGetSharedMemEx and >DosGetNamedSharedMemEx for getting, and DosFreeMemEx for freeing. Must >#define INCL_EXAPIS to get the prototypes from os2emx.h. >See the bottom of os2emx.h for descriptions details and >src/emx/src/lib/sys/Dos*Ex.c for implementation. >Yes, I need to do the IPC framework when adding any shm, msg and sem >implementation. And presently I don't really have any spare time for >doing that. >Kind Regards, > knut -- ----------------------------------------------------------- lsunley at mb.sympatico.ca ----------------------------------------------------------- **= Email 7 ==========================** Date: Sun, 19 Dec 2004 12:37:18 -0500 From: lsunley at mb.sympatico.ca Subject: GCC 335 Problem with dlopen DLL init Hi I got this error when postgres is attempting to install a language createlang: language installation failed: ERROR: could not load library "/pgsql /lib/plpgsql.dll": dlopen rc=295 DosLoadModule error 295 says that this is ERROR_INIT_ROUTINE_FAILED The library was originally built with INITGLOBAL, I changed it to INITINSTANCE and still got the same error. The postgres server is running with two fork()'ed processes. Build with gcc -Zomf -Zdll Does anyone have a clue? Lorne exehdr output Operating System/2 Executable File Header Utility Version 4.00.005 Oct 20 2000 Copyright (C) IBM Corporation 1988-2000 Copyright (C) Microsoft Corp. 1988-1992. All rights reserved. Library: PLPGSQL Description: plpgsql DLL for postgreSQL 8.0.0rc1 Module type: Dynamic link library Per-process initialization Per-process termination Number of memory pages: 00000016 (22) Initial CS:EIP: object 1 offset 00000000 Initial SS:ESP: object 0 offset 00000000 Automatic data object: 2 no. virtual virtual map map flags address size index size 0001 00010000 000149b0 00000001 00000015 EXECUTABLE, READABLE, 32-bit 0002 00030000 00000370 00000016 00000001 READABLE, WRITEABLE, 32-bit Exports: ord obj offset name 1 1 0000b868 _plpgsql_parse_word exported 2 1 00012cd0 _plpgsql_dstring_get exported 3 1 00012cf4 _plpgsql_ns_setlocal exported 4 1 00006c20 _plpgsql_base_yylex exported 5 2 000002d0 _plpgsql_base_yyleng exported 6 2 000000d4 _plpgsql_base_yyout exported 7 1 00008e64 _plpgsql_call_handler exported 8 2 000002e0 _plpgsql_base_yytext exported 9 1 00008c0c _plpgsql_scanner_init exported 10 2 000000d8 _plpgsql_SpaceScanned exported 11 2 000002f0 _plpgsql_curr_compile exported 12 1 00012c54 _plpgsql_dstring_free exported 13 1 00012c20 _plpgsql_dstring_init exported 14 1 0000da0c _plpgsql_exec_trigger exported 15 2 00000230 _plpgsql_DumpExecTree exported 16 2 00000300 _plpgsql_error_lineno exported 17 1 0000d05c _plpgsql_HashTableInit exported 18 1 0001319c _plpgsql_convert_ident exported 19 1 0000ba14 _plpgsql_parse_dblword exported 20 1 0000d3f8 _plpgsql_exec_function exported 21 1 00013558 _plpgsql_stmt_typename exported 22 1 00008dc0 _plpgsql_init exported 23 1 0000856c _plpgsql_base_yy_switch_to_buffer exported 24 1 00008cfc _plpgsql_scanner_finish exported 25 1 0000cde4 _plpgsql_add_initdatums exported 26 1 00008bd8 _plpgsql_scanner_lineno exported 27 1 0000c9ec _plpgsql_parse_datatype exported 28 1 00012c68 _plpgsql_dstring_append exported 29 1 000085c4 _plpgsql_base_yy_load_buffer_state exported 30 1 0000bde4 _plpgsql_parse_wordtype exported 31 1 0000c5f4 _plpgsql_build_variable exported 32 1 0000ca28 _plpgsql_build_datatype exported 33 2 00000310 _plpgsql_error_funcname exported 34 1 0000bc60 _plpgsql_parse_tripword exported 35 1 00003910 _plpgsql_read_expression exported 36 1 00008520 _plpgsql_base_yyrestart exported 37 1 000089a0 _plpgsql_yylex exported 38 1 00008a64 _plpgsql_push_back_token exported 39 1 00008d1c _plpgsql_get_string_value exported 40 2 00000320 _plpgsql_Datums exported 41 1 00012bb8 _plpgsql_xact_cb exported 42 1 0000c3c0 _plpgsql_parse_wordrowtype exported 43 1 0000bf34 _plpgsql_parse_dblwordtype exported 44 1 0000a968 _plpgsql_compile exported 45 2 00000330 _plpgsql_nDatums exported 46 2 00000340 _plpgsql_yylval exported 47 1 00012d60 _plpgsql_ns_pop exported 48 2 00000350 _plpgsql_yychar exported 49 1 00012cdc _plpgsql_ns_init exported 50 1 0000cd80 _plpgsql_adddatum exported 51 1 00012d0c _plpgsql_ns_push exported 52 1 00001080 _plpgsql_yyparse exported 53 1 00008ae4 _plpgsql_yyerror exported 54 2 00000360 _plpgsql_yynerrs exported 55 1 0001462c _plpgsql_dumptree exported 56 1 00008fb8 _plpgsql_validator exported 57 1 00012fb0 _plpgsql_ns_rename exported 58 2 000000d0 _plpgsql_base_yyin exported 59 1 0000877c _plpgsql_base_yy_scan_buffer exported 60 1 0000c15c _plpgsql_parse_tripwordtype exported 61 1 00008884 _plpgsql_base_yy_scan_bytes exported 62 1 00012e5c _plpgsql_ns_lookup exported 63 1 000086e4 _plpgsql_base_yy_init_buffer exported 64 1 00008f28 _pg_finfo_plpgsql_validator exported 65 1 00008814 _plpgsql_base_yy_scan_string exported 66 1 0000cc84 _plpgsql_parse_err_condition exported 67 1 0000870c _plpgsql_base_yy_flush_buffer exported 68 1 0000c4c0 _plpgsql_parse_dblwordrowtype exported 69 1 00008694 _plpgsql_base_yy_delete_buffer exported 70 1 00008620 _plpgsql_base_yy_create_buffer exported 71 1 00012db0 _plpgsql_ns_additem exported 72 1 00008e08 _pg_finfo_plpgsql_call_handler exported exeinfo output Module name PLPGSQL Operating system OS/2 2.x CPU type 80386 exe level 0 version 0 Object Table 00014f75 (2 entries) Resource Table 00000080 (0 entries) Resident Name Table 00015055 (73 entries) Import Module Name Table 00019191 (2 entries) Import Proc Name Table 000191a3 Nonresident Name Table 00014c40 (39 bytes) Debug Information 00019a7e (23463 bytes) Imported Modules: 0 POSTGRES 1 libc06b2 Object Information : 1 : ( 84400) READABLE EXECUTABLE 2 : ( 880) READABLE WRITEABLE Total Code 84400 bytes Total Data 880 bytes Total Res 0 bytes Resource Information : -- ----------------------------------------------------------- lsunley at mb.sympatico.ca ----------------------------------------------------------- **= Email 8 ==========================** Date: Sun, 19 Dec 2004 14:05:58 -0600 From: Jeff Robinson Subject: Re: GCC 335 Problem with dlopen DLL init Just out of curiosity, is there supposed to be a space in between "/pgsql" and the "/lib" directories? Jeff lsunley at mb.sympatico.ca wrote: > Hi > > I got this error when postgres is attempting to install a language > > createlang: language installation failed: ERROR: could not load library > "/pgsql /lib/plpgsql.dll": dlopen rc=295 > > DosLoadModule error 295 says that this is ERROR_INIT_ROUTINE_FAILED > > The library was originally built with INITGLOBAL, I changed it to > INITINSTANCE and still got the same error. > > The postgres server is running with two fork()'ed processes. > > Build with gcc -Zomf -Zdll > > > Does anyone have a clue? > > Lorne > > > exehdr output > > Operating System/2 Executable File Header Utility > > Version 4.00.005 Oct 20 2000 > > Copyright (C) IBM Corporation 1988-2000 > > Copyright (C) Microsoft Corp. 1988-1992. > > All rights reserved. > > Library: PLPGSQL > Description: plpgsql DLL for postgreSQL 8.0.0rc1 > > Module type: Dynamic link library > Per-process initialization > Per-process termination > Number of memory pages: 00000016 (22) > Initial CS:EIP: object 1 offset 00000000 > Initial SS:ESP: object 0 offset 00000000 > Automatic data object: 2 > > no. virtual virtual map map flags > address size index size > 0001 00010000 000149b0 00000001 00000015 EXECUTABLE, READABLE, 32-bit 0002 > 00030000 00000370 00000016 00000001 READABLE, WRITEABLE, 32-bit > > > Exports: > ord obj offset name > 1 1 0000b868 _plpgsql_parse_word exported > 2 1 00012cd0 _plpgsql_dstring_get exported > 3 1 00012cf4 _plpgsql_ns_setlocal exported > 4 1 00006c20 _plpgsql_base_yylex exported > 5 2 000002d0 _plpgsql_base_yyleng exported > 6 2 000000d4 _plpgsql_base_yyout exported > 7 1 00008e64 _plpgsql_call_handler exported > 8 2 000002e0 _plpgsql_base_yytext exported > 9 1 00008c0c _plpgsql_scanner_init exported > 10 2 000000d8 _plpgsql_SpaceScanned exported > 11 2 000002f0 _plpgsql_curr_compile exported > 12 1 00012c54 _plpgsql_dstring_free exported > 13 1 00012c20 _plpgsql_dstring_init exported > 14 1 0000da0c _plpgsql_exec_trigger exported > 15 2 00000230 _plpgsql_DumpExecTree exported > 16 2 00000300 _plpgsql_error_lineno exported > 17 1 0000d05c _plpgsql_HashTableInit exported > 18 1 0001319c _plpgsql_convert_ident exported > 19 1 0000ba14 _plpgsql_parse_dblword exported > 20 1 0000d3f8 _plpgsql_exec_function exported > 21 1 00013558 _plpgsql_stmt_typename exported > 22 1 00008dc0 _plpgsql_init exported > 23 1 0000856c _plpgsql_base_yy_switch_to_buffer exported > 24 1 00008cfc _plpgsql_scanner_finish exported > 25 1 0000cde4 _plpgsql_add_initdatums exported > 26 1 00008bd8 _plpgsql_scanner_lineno exported > 27 1 0000c9ec _plpgsql_parse_datatype exported > 28 1 00012c68 _plpgsql_dstring_append exported > 29 1 000085c4 _plpgsql_base_yy_load_buffer_state exported > 30 1 0000bde4 _plpgsql_parse_wordtype exported > 31 1 0000c5f4 _plpgsql_build_variable exported > 32 1 0000ca28 _plpgsql_build_datatype exported > 33 2 00000310 _plpgsql_error_funcname exported > 34 1 0000bc60 _plpgsql_parse_tripword exported > 35 1 00003910 _plpgsql_read_expression exported > 36 1 00008520 _plpgsql_base_yyrestart exported > 37 1 000089a0 _plpgsql_yylex exported > 38 1 00008a64 _plpgsql_push_back_token exported > 39 1 00008d1c _plpgsql_get_string_value exported > 40 2 00000320 _plpgsql_Datums exported > 41 1 00012bb8 _plpgsql_xact_cb exported > 42 1 0000c3c0 _plpgsql_parse_wordrowtype exported > 43 1 0000bf34 _plpgsql_parse_dblwordtype exported > 44 1 0000a968 _plpgsql_compile exported > 45 2 00000330 _plpgsql_nDatums exported > 46 2 00000340 _plpgsql_yylval exported > 47 1 00012d60 _plpgsql_ns_pop exported > 48 2 00000350 _plpgsql_yychar exported > 49 1 00012cdc _plpgsql_ns_init exported > 50 1 0000cd80 _plpgsql_adddatum exported > 51 1 00012d0c _plpgsql_ns_push exported > 52 1 00001080 _plpgsql_yyparse exported > 53 1 00008ae4 _plpgsql_yyerror exported > 54 2 00000360 _plpgsql_yynerrs exported > 55 1 0001462c _plpgsql_dumptree exported > 56 1 00008fb8 _plpgsql_validator exported > 57 1 00012fb0 _plpgsql_ns_rename exported > 58 2 000000d0 _plpgsql_base_yyin exported > 59 1 0000877c _plpgsql_base_yy_scan_buffer exported > 60 1 0000c15c _plpgsql_parse_tripwordtype exported > 61 1 00008884 _plpgsql_base_yy_scan_bytes exported > 62 1 00012e5c _plpgsql_ns_lookup exported > 63 1 000086e4 _plpgsql_base_yy_init_buffer exported > 64 1 00008f28 _pg_finfo_plpgsql_validator exported > 65 1 00008814 _plpgsql_base_yy_scan_string exported > 66 1 0000cc84 _plpgsql_parse_err_condition exported > 67 1 0000870c _plpgsql_base_yy_flush_buffer exported > 68 1 0000c4c0 _plpgsql_parse_dblwordrowtype exported > 69 1 00008694 _plpgsql_base_yy_delete_buffer exported > 70 1 00008620 _plpgsql_base_yy_create_buffer exported > 71 1 00012db0 _plpgsql_ns_additem exported > 72 1 00008e08 _pg_finfo_plpgsql_call_handler exported > > exeinfo output > > Module name PLPGSQL > Operating system OS/2 2.x > CPU type 80386 > exe level 0 > version 0 > Object Table 00014f75 (2 entries) > Resource Table 00000080 (0 entries) > Resident Name Table 00015055 (73 entries) > Import Module Name Table 00019191 (2 entries) > Import Proc Name Table 000191a3 > Nonresident Name Table 00014c40 (39 bytes) > Debug Information 00019a7e (23463 bytes) > > Imported Modules: > 0 POSTGRES > 1 libc06b2 > > Object Information : > 1 : ( 84400) READABLE EXECUTABLE > 2 : ( 880) READABLE WRITEABLE > > Total Code 84400 bytes > Total Data 880 bytes > Total Res 0 bytes > > Resource Information : > -- ---------------- Whatza JamochaMUD? http://jamochamud.anecho.mb.ca Or other stuff: http://www.anecho.mb.ca/~jeffnik ----------------------------------------------------------- **= Email 9 ==========================** Date: Sun, 19 Dec 2004 20:13:07 +0000 From: John Poltorak Subject: checking for a BSD-compatible install When configure runs it normally checks for a BSD-compatible install and selects install.exe from the GNU Fileutils and this is usually identified by the INSTALL variable in the Makefile. But in addition there is also a varibale identified as INSTALL_PROGRAM which appears to be set to ${INSTALL}. Does anyone know whether the actual install performed when running 'make install' uses $INSTALL or $INSTALL_PROGRAM ? I have a requirement for some additional processing during installation and wondered if it was possible to define my own INSTALL_PROGRAM... Basically, what I would like to do as part of the install is to datestamp each file installed with respect to a particular reference file, ie I would like to include 'touch -r $ref_file' as part of install process. Does anyone have any idea about how I could achieve this? -- John **= Email 1 ==========================** Date: Sun, 19 Dec 2004 12:08:28 -0800 From: "Dave Yeo" Subject: Re: Building SMAKE/STAR etc On Sun, 19 Dec 2004 16:23:30 +0000, John Poltorak wrote: >On Sat, Dec 18, 2004 at 07:26:17AM -0800, Dave Yeo wrote: >> On Thu, 16 Dec 2004 09:21:06 +0000, John Poltorak wrote: >> >> >What changes need to be made to various utilities such as smake, star etc >> >developed by Joerg Schilling to make them build on OS/2? >> > >> >They come with build instructions for OS/2 but I haven't managed to make >> >them work. Has anyone else? snip > >But don't you need smake before you can build star? Sounds like a catch-22 >situation... As I think I mentioned I had to extract the source on Linux to begin with. Now there is a binary on Hobbes which you can start with. You'd have the same problem with tar if you were the first porter. > >> Then need to remove -Zexe from psmake/MAKE-sh and >> RULES/i386-os2-gcc.rul >> and run sh Gmake.linux. Install seems to be broken when using Gnu Make >> so copy smake/OBJ/i386-os2-gcc/smake.exe to PATH (or perhaps use its >> absolute location) then something like smake INS_BASE=/usr/local >> install will install to /usr/local. > >The thing is it is supposed to work on OS/2 out of the box - it even has >OS/2 specific build scripts which one assumes did work for someone at one >point. I'd just to find out if they ever did work for anyone. If they are >in the package they must be there for a reason. Joerg did mention that he hasn't built it on OS/2 in over a year so I guess it did work for him. What appears to of happened is that he added exeext (for cygwin?) to his build system and this conflicts with -Zexe on OS/2. Like most open source it is developing quickly and without an OS/2 maintainer things break. > > >> Star-1.4.3 also dies if built with innotek_libc due to a sigill The sigill (whatever that is) only happens with gzipped tar files. It untars fine. Also the build and install work alot better using symlinks instead of copying. It does break due to trying to use hardlinks during install and won't overwrite itself which could well be a problem with the gnufileutils built with Innotek_libc >> Star-1.5 does not build due to unresolved symbol _unlink. I did suceed >> in building it with innotek_libc but all it did was segfault and I >> haven't got around to debugging. >> IIRC cdrtools-2.01 built fine here using smake > >That's good. I will have to give it a try. > Dave **= Email 2 ==========================** Date: Sun, 19 Dec 2004 22:00:17 +0100 (CET) From: "Yuri Dario" Subject: Re: Building SMAKE/STAR etc Hi, >Joerg did mention that he hasn't built it on OS/2 in over a year so I guess it did work for >him. What appears to of happened is that he added exeext (for cygwin?) to his build here I built smake 1.2a23 using gcc 3.2.2 without problems. Bye, Yuri Dario /* * member of TeamOS/2 - Italy * http://www.os2power.com/yuri * http://www.teamos2.it */ **= Email 3 ==========================** Date: Sun, 19 Dec 2004 14:47:52 -0800 From: "Dave Yeo" Subject: Re: Building SMAKE/STAR etc On Sun, 19 Dec 2004 22:00:17 +0100 (CET), Yuri Dario wrote: >Hi, > >>Joerg did mention that he hasn't built it on OS/2 in over a year so I guess it did work for >>him. What appears to of happened is that he added exeext (for cygwin?) to his build > >here I built smake 1.2a23 using gcc 3.2.2 without problems. Innoteks libc doesn't mind -Zexe being used on foo.exe. EMX does. I was trying to build it with ux2bs since thats Johns enviroment. Dave **= Email 4 ==========================** Date: Sun, 19 Dec 2004 19:41:59 -0500 From: lsunley at mb.sympatico.ca Subject: postgreSQL v8.0 rc1 beta is released Hi All For anyone interested, I put a beta of postgreSQL v8.0 rc1 on Hobbes. The file is postgreSQL-8.0-rc1.zip It is built using the GCC 3.3.5 compiler, and I included libc06b2.dll with it. I am using OBJ_ANY to allocate shared memory so it will use the high memory region for buffers. This probably means you have to have Warp 4.5 to run it. Lorne -- ----------------------------------------------------------- lsunley at mb.sympatico.ca ----------------------------------------------------------- **= Email 5 ==========================** Date: Mon, 20 Dec 2004 09:44:52 +0000 From: John Poltorak Subject: Building PDKSH with GCC 3.3.5 I've built PDKSH with gcc 3.3.5 beta2 and get an sh.exe which runs without getting the 'no controlling tty' problem reported previously. Running make test results in:- Total failed: 96 (93 unexpected) Total passed: 102 This is slightly better than previously but nowhere near as good as the emx build, but the worst problem is that it dies when running the simplest of scripts such as this:- #! bin env which results in:- [G:\ux2bs.tmp\workdir\pdksh-5.2.14]sh temp Process terminated by SIGILL - pid=0x0a7f - tid=0x01 - G:\UX2BS.TMP\WORKDIR\PDKSH-5.2.14\SH.EXE Any ideas on what is wrong here? -- John **= Email 6 ==========================** Date: Mon, 20 Dec 2004 10:18:09 +0000 From: John Poltorak Subject: Building Emacs --BZ1f52eXV1Rdy+7l Content-Type: text/plain; charset=us-ascii Can anyone try building Emacs with the attached build script suitably adjusted for your own environment? It may need some slight manual intervention, which I would like to eliminate eventually, so would be grateful for any suggestions as to how it could be done. If you manage it with EMX/GCC, could you try it with gcc 3.3.5? -- John --BZ1f52eXV1Rdy+7l Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="G:\\build_emacs2.cmd" set path=g:\ux2bs\lib;g:\ux2bs\bin;c:\os2; set beginlibpath=g:/ux2bs\dll; env | sed "/^\/k/d;s/^/set /;s/=.*$/=/" >zap_env.cmd call zap_env.cmd set osrt=c: set uxrt=g: set bldrt=g: set bld_home=g:/ux2bs set repository=r:/unixos2/archives/source set workdir=g:/ux2bs/workdir set buildlogs=g:/ux2bs/logs set CONFIG_SITE=g:/ux2bs/lib/config.site set C_INCLUDE_PATH=g:/usr/include;g:/ux2bs/emx/include set CPLUS_INCLUDE_PATH=g:/usr/include/cpp;g:/usr/include;g:/ux2bs/emx/include/cpp;g:/ux2bs/emx/include set LIBRARY_PATH=g:/usr/lib;g:/ux2bs/emx/lib set beginlibpath=g:\usr\lib;g:\ux2bs\dll; set PATH=g:\usr\bin;g:\usr\X11R6\bin;g:\ux2bs\emx\bin;g:\usr\local\bin;g:\ux2bs\bin;c:\os2; set DPATH=c:\os2\system set TMP=g:\tmp set HOME=g:/home/root set ETC=g:\etc set TERM=ansi-color-3 set OS2_SHELL=c:\os2\cmd.exe set COMSPEC=c:\os2\cmd.exe set PAGER=less set HOSTNAME=localhost set host=192.168.0.1 cd %tmp% wget ftp://ftp.gnu.org/pub/gnu/emacs/emacs-20.7.tar.gz && tar zxf emacs-20.7.tar.gz wget ftp://ftp.gnu.org/pub/gnu/emacs/leim-20.7.tar.gz && tar zxf leim-20.7.tar.gz wget http://www.asahi-net.or.jp/~ik3a-nsmr/emacs-20.7-KIT1.9.tgz tar zxf emacs-20.7.tar.gz tar zxf leim-20.7.tar.gz cd emacs-20.7 chmod +rw -R * tar zxf ..\emacs-20.7-KIT1.9.tgz echo echo Enter patch and if correctly identified confirm by pressing enter echo configure.cmd --with-bsd-socket --with-xf86sup-pty SET INCLUDE=%C_INCLUDE_PATH% SET NAME=Bilbo Baggins make del src\emacs.exe make rem add emacs-20.7\src to SET PATH in the CONFIG.SYS SET EMACSROOT=g:/usr/local/emacs-20.7 SET EMACSLOADPATH=g:/usr/local/emacs-20.7/lisp;g:/usr/local/emacs-20.7/site-lisp;g:/usr/local/emacs-20.7/leim echo g:\usr\local\emacs-20.7\src\emacs.exe > emacs.cmd --BZ1f52eXV1Rdy+7l-- **= Email 7 ==========================** Date: Mon, 20 Dec 2004 10:23:47 +0000 From: John Poltorak Subject: Python modules in Apache Does anyone know what I need to do in Apache to be able to run Python modules? -- John **= Email 8 ==========================** Date: Mon, 20 Dec 2004 11:40:45 +0100 From: "Knut St. Osmundsen" Subject: Re: GCC 335 Problem with dlopen DLL init Hi, Is that output partly from dlerror? If so, DosLoadModule didn't indicate any object module - or the error handling is broken, which is more likely. The problem you have is probably related to POSTGRES.DLL to being able to load for some reason. The usual approach when dealing with such problem includes a debugger debugger, or the least debug printfs/logging. Set an breakpoint for load occurance on POSTGRES and PLPGSQL. When the breakpoints trigger, set a breakpoint in the dll*0*.o* of the dll(s) loaded. Then step the init code and try figure out why it all fails. Kind Regards, knut Btw, a requirement of fork() is that dlls are inited per instance. Global init won't work and might crash the child in a fork(), or simply not process anything for the dll. lsunley at mb.sympatico.ca wrote: > Hi > > I got this error when postgres is attempting to install a language > > createlang: language installation failed: ERROR: could not load library > "/pgsql /lib/plpgsql.dll": dlopen rc=295 > > DosLoadModule error 295 says that this is ERROR_INIT_ROUTINE_FAILED > > The library was originally built with INITGLOBAL, I changed it to > INITINSTANCE and still got the same error. > > The postgres server is running with two fork()'ed processes. > > Build with gcc -Zomf -Zdll > > > Does anyone have a clue? > > Lorne > > > exehdr output > > Operating System/2 Executable File Header Utility > > Version 4.00.005 Oct 20 2000 > > Copyright (C) IBM Corporation 1988-2000 > > Copyright (C) Microsoft Corp. 1988-1992. > > All rights reserved. > > Library: PLPGSQL > Description: plpgsql DLL for postgreSQL 8.0.0rc1 > > Module type: Dynamic link library > Per-process initialization > Per-process termination > Number of memory pages: 00000016 (22) > Initial CS:EIP: object 1 offset 00000000 > Initial SS:ESP: object 0 offset 00000000 > Automatic data object: 2 > > no. virtual virtual map map flags > address size index size > 0001 00010000 000149b0 00000001 00000015 EXECUTABLE, READABLE, 32-bit 0002 > 00030000 00000370 00000016 00000001 READABLE, WRITEABLE, 32-bit > > > Exports: > ord obj offset name > 1 1 0000b868 _plpgsql_parse_word exported > 2 1 00012cd0 _plpgsql_dstring_get exported > 3 1 00012cf4 _plpgsql_ns_setlocal exported > 4 1 00006c20 _plpgsql_base_yylex exported > 5 2 000002d0 _plpgsql_base_yyleng exported > 6 2 000000d4 _plpgsql_base_yyout exported > 7 1 00008e64 _plpgsql_call_handler exported > 8 2 000002e0 _plpgsql_base_yytext exported > 9 1 00008c0c _plpgsql_scanner_init exported > 10 2 000000d8 _plpgsql_SpaceScanned exported > 11 2 000002f0 _plpgsql_curr_compile exported > 12 1 00012c54 _plpgsql_dstring_free exported > 13 1 00012c20 _plpgsql_dstring_init exported > 14 1 0000da0c _plpgsql_exec_trigger exported > 15 2 00000230 _plpgsql_DumpExecTree exported > 16 2 00000300 _plpgsql_error_lineno exported > 17 1 0000d05c _plpgsql_HashTableInit exported > 18 1 0001319c _plpgsql_convert_ident exported > 19 1 0000ba14 _plpgsql_parse_dblword exported > 20 1 0000d3f8 _plpgsql_exec_function exported > 21 1 00013558 _plpgsql_stmt_typename exported > 22 1 00008dc0 _plpgsql_init exported > 23 1 0000856c _plpgsql_base_yy_switch_to_buffer exported > 24 1 00008cfc _plpgsql_scanner_finish exported > 25 1 0000cde4 _plpgsql_add_initdatums exported > 26 1 00008bd8 _plpgsql_scanner_lineno exported > 27 1 0000c9ec _plpgsql_parse_datatype exported > 28 1 00012c68 _plpgsql_dstring_append exported > 29 1 000085c4 _plpgsql_base_yy_load_buffer_state exported > 30 1 0000bde4 _plpgsql_parse_wordtype exported > 31 1 0000c5f4 _plpgsql_build_variable exported > 32 1 0000ca28 _plpgsql_build_datatype exported > 33 2 00000310 _plpgsql_error_funcname exported > 34 1 0000bc60 _plpgsql_parse_tripword exported > 35 1 00003910 _plpgsql_read_expression exported > 36 1 00008520 _plpgsql_base_yyrestart exported > 37 1 000089a0 _plpgsql_yylex exported > 38 1 00008a64 _plpgsql_push_back_token exported > 39 1 00008d1c _plpgsql_get_string_value exported > 40 2 00000320 _plpgsql_Datums exported > 41 1 00012bb8 _plpgsql_xact_cb exported > 42 1 0000c3c0 _plpgsql_parse_wordrowtype exported > 43 1 0000bf34 _plpgsql_parse_dblwordtype exported > 44 1 0000a968 _plpgsql_compile exported > 45 2 00000330 _plpgsql_nDatums exported > 46 2 00000340 _plpgsql_yylval exported > 47 1 00012d60 _plpgsql_ns_pop exported > 48 2 00000350 _plpgsql_yychar exported > 49 1 00012cdc _plpgsql_ns_init exported > 50 1 0000cd80 _plpgsql_adddatum exported > 51 1 00012d0c _plpgsql_ns_push exported > 52 1 00001080 _plpgsql_yyparse exported > 53 1 00008ae4 _plpgsql_yyerror exported > 54 2 00000360 _plpgsql_yynerrs exported > 55 1 0001462c _plpgsql_dumptree exported > 56 1 00008fb8 _plpgsql_validator exported > 57 1 00012fb0 _plpgsql_ns_rename exported > 58 2 000000d0 _plpgsql_base_yyin exported > 59 1 0000877c _plpgsql_base_yy_scan_buffer exported > 60 1 0000c15c _plpgsql_parse_tripwordtype exported > 61 1 00008884 _plpgsql_base_yy_scan_bytes exported > 62 1 00012e5c _plpgsql_ns_lookup exported > 63 1 000086e4 _plpgsql_base_yy_init_buffer exported > 64 1 00008f28 _pg_finfo_plpgsql_validator exported > 65 1 00008814 _plpgsql_base_yy_scan_string exported > 66 1 0000cc84 _plpgsql_parse_err_condition exported > 67 1 0000870c _plpgsql_base_yy_flush_buffer exported > 68 1 0000c4c0 _plpgsql_parse_dblwordrowtype exported > 69 1 00008694 _plpgsql_base_yy_delete_buffer exported > 70 1 00008620 _plpgsql_base_yy_create_buffer exported > 71 1 00012db0 _plpgsql_ns_additem exported > 72 1 00008e08 _pg_finfo_plpgsql_call_handler exported > > exeinfo output > > Module name PLPGSQL > Operating system OS/2 2.x > CPU type 80386 > exe level 0 > version 0 > Object Table 00014f75 (2 entries) > Resource Table 00000080 (0 entries) > Resident Name Table 00015055 (73 entries) > Import Module Name Table 00019191 (2 entries) > Import Proc Name Table 000191a3 > Nonresident Name Table 00014c40 (39 bytes) > Debug Information 00019a7e (23463 bytes) > > Imported Modules: > 0 POSTGRES > 1 libc06b2 > > Object Information : > 1 : ( 84400) READABLE EXECUTABLE > 2 : ( 880) READABLE WRITEABLE > > Total Code 84400 bytes > Total Data 880 bytes > Total Res 0 bytes > > Resource Information : > **= Email 9 ==========================** Date: Mon, 20 Dec 2004 12:02:21 +0100 From: "Knut St. Osmundsen" Subject: Re: postgreSQL progress Arg, must be a bug in the shared memory fork code. Have added it to the todo list. Sorry for the inconvenience. Kind Regards, knut lsunley at mb.sympatico.ca wrote: > Hi Again > > I tried the *Ex API for both semaphores and shared memory. > > The postgres server started using up 100% of CPU on both CPUs of my test > machine... > > I backed out the semaphore Ex API and still got the same 100% CPU. > > Backed out the shared memory Ex API and it works again > > Is there anything I can do to find out what is happening? > > Lorne > > In <41C5434F.2060200 at anduin.net>, on 12/19/04 > at 09:01 AM, "Knut St. Osmundsen" said: > > > >>Did you make use of the Dos API extensions for managing shared memory? >>If not: DosAllocSharedMemEx for alloc, DosGetSharedMemEx and >>DosGetNamedSharedMemEx for getting, and DosFreeMemEx for freeing. Must >>#define INCL_EXAPIS to get the prototypes from os2emx.h. >>See the bottom of os2emx.h for descriptions details and >>src/emx/src/lib/sys/Dos*Ex.c for implementation. > > >>Yes, I need to do the IPC framework when adding any shm, msg and sem >>implementation. And presently I don't really have any spare time for >>doing that. > > >>Kind Regards, >> knut > > > > **= Email 10 ==========================** Date: Mon, 20 Dec 2004 11:16:23 +0000 From: John Poltorak Subject: Re: postgreSQL v8.0 rc1 beta is released On Sun, Dec 19, 2004 at 07:41:59PM -0500, lsunley at mb.sympatico.ca wrote: > Hi All > > For anyone interested, I put a beta of postgreSQL v8.0 rc1 on Hobbes. Just gave it a quick try... initdb worked OK, but when running postmaster, I get:- [G:\pgsql\bin]postmaster LOG: select() failed in statistics collector: Invalid argument LOG: disabling statistics collector for lack of working socket Process terminated by SIGILL - pid=0x0b07 - tid=0x01 - G:\PGSQL\BIN\POSTMASTER.EXE What have I overlooked? > Lorne > > -- > ----------------------------------------------------------- > lsunley at mb.sympatico.ca > ----------------------------------------------------------- -- John **= Email 14 ==========================** Date: Sun, 19 Dec 2004 14:27:36 -0500 From: lsunley at mb.sympatico.ca Subject: Re: GCC 335 Problem with dlopen DLL init In <41C5DF26.3030505 at anecho.mb.ca>, on 12/19/04 at 02:05 PM, Jeff Robinson said: >Just out of curiosity, is there supposed to be a space in between >"/pgsql" and the "/lib" directories? That's an artifact of copying the message text out of a VIO window.. Lorne >Jeff >lsunley at mb.sympatico.ca wrote: >> Hi >> >> I got this error when postgres is attempting to install a language >> >> createlang: language installation failed: ERROR: could not load library >> "/pgsql /lib/plpgsql.dll": dlopen rc=295 >> >> DosLoadModule error 295 says that this is ERROR_INIT_ROUTINE_FAILED >> >> The library was originally built with INITGLOBAL, I changed it to >> INITINSTANCE and still got the same error. >> >> The postgres server is running with two fork()'ed processes. >> >> Build with gcc -Zomf -Zdll >> >> >> Does anyone have a clue? >> >> Lorne >> >> >> exehdr output >> >> Operating System/2 Executable File Header Utility >> >> Version 4.00.005 Oct 20 2000 >> >> Copyright (C) IBM Corporation 1988-2000 >> >> Copyright (C) Microsoft Corp. 1988-1992. >> >> All rights reserved. >> >> Library: PLPGSQL >> Description: plpgsql DLL for postgreSQL 8.0.0rc1 >> >> Module type: Dynamic link library >> Per-process initialization >> Per-process termination >> Number of memory pages: 00000016 (22) >> Initial CS:EIP: object 1 offset 00000000 >> Initial SS:ESP: object 0 offset 00000000 >> Automatic data object: 2 >> >> no. virtual virtual map map flags >> address size index size >> 0001 00010000 000149b0 00000001 00000015 EXECUTABLE, READABLE, 32-bit 0002 >> 00030000 00000370 00000016 00000001 READABLE, WRITEABLE, 32-bit >> >> >> Exports: >> ord obj offset name >> 1 1 0000b868 _plpgsql_parse_word exported >> 2 1 00012cd0 _plpgsql_dstring_get exported >> 3 1 00012cf4 _plpgsql_ns_setlocal exported >> 4 1 00006c20 _plpgsql_base_yylex exported >> 5 2 000002d0 _plpgsql_base_yyleng exported >> 6 2 000000d4 _plpgsql_base_yyout exported >> 7 1 00008e64 _plpgsql_call_handler exported >> 8 2 000002e0 _plpgsql_base_yytext exported >> 9 1 00008c0c _plpgsql_scanner_init exported >> 10 2 000000d8 _plpgsql_SpaceScanned exported >> 11 2 000002f0 _plpgsql_curr_compile exported >> 12 1 00012c54 _plpgsql_dstring_free exported >> 13 1 00012c20 _plpgsql_dstring_init exported >> 14 1 0000da0c _plpgsql_exec_trigger exported >> 15 2 00000230 _plpgsql_DumpExecTree exported >> 16 2 00000300 _plpgsql_error_lineno exported >> 17 1 0000d05c _plpgsql_HashTableInit exported >> 18 1 0001319c _plpgsql_convert_ident exported >> 19 1 0000ba14 _plpgsql_parse_dblword exported >> 20 1 0000d3f8 _plpgsql_exec_function exported >> 21 1 00013558 _plpgsql_stmt_typename exported >> 22 1 00008dc0 _plpgsql_init exported >> 23 1 0000856c _plpgsql_base_yy_switch_to_buffer exported >> 24 1 00008cfc _plpgsql_scanner_finish exported >> 25 1 0000cde4 _plpgsql_add_initdatums exported >> 26 1 00008bd8 _plpgsql_scanner_lineno exported >> 27 1 0000c9ec _plpgsql_parse_datatype exported >> 28 1 00012c68 _plpgsql_dstring_append exported >> 29 1 000085c4 _plpgsql_base_yy_load_buffer_state exported >> 30 1 0000bde4 _plpgsql_parse_wordtype exported >> 31 1 0000c5f4 _plpgsql_build_variable exported >> 32 1 0000ca28 _plpgsql_build_datatype exported >> 33 2 00000310 _plpgsql_error_funcname exported >> 34 1 0000bc60 _plpgsql_parse_tripword exported >> 35 1 00003910 _plpgsql_read_expression exported >> 36 1 00008520 _plpgsql_base_yyrestart exported >> 37 1 000089a0 _plpgsql_yylex exported >> 38 1 00008a64 _plpgsql_push_back_token exported >> 39 1 00008d1c _plpgsql_get_string_value exported >> 40 2 00000320 _plpgsql_Datums exported >> 41 1 00012bb8 _plpgsql_xact_cb exported >> 42 1 0000c3c0 _plpgsql_parse_wordrowtype exported >> 43 1 0000bf34 _plpgsql_parse_dblwordtype exported >> 44 1 0000a968 _plpgsql_compile exported >> 45 2 00000330 _plpgsql_nDatums exported >> 46 2 00000340 _plpgsql_yylval exported >> 47 1 00012d60 _plpgsql_ns_pop exported >> 48 2 00000350 _plpgsql_yychar exported >> 49 1 00012cdc _plpgsql_ns_init exported >> 50 1 0000cd80 _plpgsql_adddatum exported >> 51 1 00012d0c _plpgsql_ns_push exported >> 52 1 00001080 _plpgsql_yyparse exported >> 53 1 00008ae4 _plpgsql_yyerror exported >> 54 2 00000360 _plpgsql_yynerrs exported >> 55 1 0001462c _plpgsql_dumptree exported >> 56 1 00008fb8 _plpgsql_validator exported >> 57 1 00012fb0 _plpgsql_ns_rename exported >> 58 2 000000d0 _plpgsql_base_yyin exported >> 59 1 0000877c _plpgsql_base_yy_scan_buffer exported >> 60 1 0000c15c _plpgsql_parse_tripwordtype exported >> 61 1 00008884 _plpgsql_base_yy_scan_bytes exported >> 62 1 00012e5c _plpgsql_ns_lookup exported >> 63 1 000086e4 _plpgsql_base_yy_init_buffer exported >> 64 1 00008f28 _pg_finfo_plpgsql_validator exported >> 65 1 00008814 _plpgsql_base_yy_scan_string exported >> 66 1 0000cc84 _plpgsql_parse_err_condition exported >> 67 1 0000870c _plpgsql_base_yy_flush_buffer exported >> 68 1 0000c4c0 _plpgsql_parse_dblwordrowtype exported >> 69 1 00008694 _plpgsql_base_yy_delete_buffer exported >> 70 1 00008620 _plpgsql_base_yy_create_buffer exported >> 71 1 00012db0 _plpgsql_ns_additem exported >> 72 1 00008e08 _pg_finfo_plpgsql_call_handler exported >> >> exeinfo output >> >> Module name PLPGSQL >> Operating system OS/2 2.x >> CPU type 80386 >> exe level 0 >> version 0 >> Object Table 00014f75 (2 entries) >> Resource Table 00000080 (0 entries) >> Resident Name Table 00015055 (73 entries) >> Import Module Name Table 00019191 (2 entries) >> Import Proc Name Table 000191a3 >> Nonresident Name Table 00014c40 (39 bytes) >> Debug Information 00019a7e (23463 bytes) >> >> Imported Modules: >> 0 POSTGRES >> 1 libc06b2 >> >> Object Information : >> 1 : ( 84400) READABLE EXECUTABLE >> 2 : ( 880) READABLE WRITEABLE >> >> Total Code 84400 bytes >> Total Data 880 bytes >> Total Res 0 bytes >> >> Resource Information : >> -- ----------------------------------------------------------- lsunley at mb.sympatico.ca ----------------------------------------------------------- **= Email 10 ==========================** Date: Sun, 19 Dec 2004 14:27:36 -0500 From: lsunley at mb.sympatico.ca Subject: Re: GCC 335 Problem with dlopen DLL init In <41C5DF26.3030505 at anecho.mb.ca>, on 12/19/04 at 02:05 PM, Jeff Robinson said: >Just out of curiosity, is there supposed to be a space in between >"/pgsql" and the "/lib" directories? That's an artifact of copying the message text out of a VIO window.. Lorne >Jeff >lsunley at mb.sympatico.ca wrote: >> Hi >> >> I got this error when postgres is attempting to install a language >> >> createlang: language installation failed: ERROR: could not load library >> "/pgsql /lib/plpgsql.dll": dlopen rc=295 >> >> DosLoadModule error 295 says that this is ERROR_INIT_ROUTINE_FAILED >> >> The library was originally built with INITGLOBAL, I changed it to >> INITINSTANCE and still got the same error. >> >> The postgres server is running with two fork()'ed processes. >> >> Build with gcc -Zomf -Zdll >> >> >> Does anyone have a clue? >> >> Lorne >> >> >> exehdr output >> >> Operating System/2 Executable File Header Utility >> >> Version 4.00.005 Oct 20 2000 >> >> Copyright (C) IBM Corporation 1988-2000 >> >> Copyright (C) Microsoft Corp. 1988-1992. >> >> All rights reserved. >> >> Library: PLPGSQL >> Description: plpgsql DLL for postgreSQL 8.0.0rc1 >> >> Module type: Dynamic link library >> Per-process initialization >> Per-process termination >> Number of memory pages: 00000016 (22) >> Initial CS:EIP: object 1 offset 00000000 >> Initial SS:ESP: object 0 offset 00000000 >> Automatic data object: 2 >> >> no. virtual virtual map map flags >> address size index size >> 0001 00010000 000149b0 00000001 00000015 EXECUTABLE, READABLE, 32-bit 0002 >> 00030000 00000370 00000016 00000001 READABLE, WRITEABLE, 32-bit >> >> >> Exports: >> ord obj offset name >> 1 1 0000b868 _plpgsql_parse_word exported >> 2 1 00012cd0 _plpgsql_dstring_get exported >> 3 1 00012cf4 _plpgsql_ns_setlocal exported >> 4 1 00006c20 _plpgsql_base_yylex exported >> 5 2 000002d0 _plpgsql_base_yyleng exported >> 6 2 000000d4 _plpgsql_base_yyout exported >> 7 1 00008e64 _plpgsql_call_handler exported >> 8 2 000002e0 _plpgsql_base_yytext exported >> 9 1 00008c0c _plpgsql_scanner_init exported >> 10 2 000000d8 _plpgsql_SpaceScanned exported >> 11 2 000002f0 _plpgsql_curr_compile exported >> 12 1 00012c54 _plpgsql_dstring_free exported >> 13 1 00012c20 _plpgsql_dstring_init exported >> 14 1 0000da0c _plpgsql_exec_trigger exported >> 15 2 00000230 _plpgsql_DumpExecTree exported >> 16 2 00000300 _plpgsql_error_lineno exported >> 17 1 0000d05c _plpgsql_HashTableInit exported >> 18 1 0001319c _plpgsql_convert_ident exported >> 19 1 0000ba14 _plpgsql_parse_dblword exported >> 20 1 0000d3f8 _plpgsql_exec_function exported >> 21 1 00013558 _plpgsql_stmt_typename exported >> 22 1 00008dc0 _plpgsql_init exported >> 23 1 0000856c _plpgsql_base_yy_switch_to_buffer exported >> 24 1 00008cfc _plpgsql_scanner_finish exported >> 25 1 0000cde4 _plpgsql_add_initdatums exported >> 26 1 00008bd8 _plpgsql_scanner_lineno exported >> 27 1 0000c9ec _plpgsql_parse_datatype exported >> 28 1 00012c68 _plpgsql_dstring_append exported >> 29 1 000085c4 _plpgsql_base_yy_load_buffer_state exported >> 30 1 0000bde4 _plpgsql_parse_wordtype exported >> 31 1 0000c5f4 _plpgsql_build_variable exported >> 32 1 0000ca28 _plpgsql_build_datatype exported >> 33 2 00000310 _plpgsql_error_funcname exported >> 34 1 0000bc60 _plpgsql_parse_tripword exported >> 35 1 00003910 _plpgsql_read_expression exported >> 36 1 00008520 _plpgsql_base_yyrestart exported >> 37 1 000089a0 _plpgsql_yylex exported >> 38 1 00008a64 _plpgsql_push_back_token exported >> 39 1 00008d1c _plpgsql_get_string_value exported >> 40 2 00000320 _plpgsql_Datums exported >> 41 1 00012bb8 _plpgsql_xact_cb exported >> 42 1 0000c3c0 _plpgsql_parse_wordrowtype exported >> 43 1 0000bf34 _plpgsql_parse_dblwordtype exported >> 44 1 0000a968 _plpgsql_compile exported >> 45 2 00000330 _plpgsql_nDatums exported >> 46 2 00000340 _plpgsql_yylval exported >> 47 1 00012d60 _plpgsql_ns_pop exported >> 48 2 00000350 _plpgsql_yychar exported >> 49 1 00012cdc _plpgsql_ns_init exported >> 50 1 0000cd80 _plpgsql_adddatum exported >> 51 1 00012d0c _plpgsql_ns_push exported >> 52 1 00001080 _plpgsql_yyparse exported >> 53 1 00008ae4 _plpgsql_yyerror exported >> 54 2 00000360 _plpgsql_yynerrs exported >> 55 1 0001462c _plpgsql_dumptree exported >> 56 1 00008fb8 _plpgsql_validator exported >> 57 1 00012fb0 _plpgsql_ns_rename exported >> 58 2 000000d0 _plpgsql_base_yyin exported >> 59 1 0000877c _plpgsql_base_yy_scan_buffer exported >> 60 1 0000c15c _plpgsql_parse_tripwordtype exported >> 61 1 00008884 _plpgsql_base_yy_scan_bytes exported >> 62 1 00012e5c _plpgsql_ns_lookup exported >> 63 1 000086e4 _plpgsql_base_yy_init_buffer exported >> 64 1 00008f28 _pg_finfo_plpgsql_validator exported >> 65 1 00008814 _plpgsql_base_yy_scan_string exported >> 66 1 0000cc84 _plpgsql_parse_err_condition exported >> 67 1 0000870c _plpgsql_base_yy_flush_buffer exported >> 68 1 0000c4c0 _plpgsql_parse_dblwordrowtype exported >> 69 1 00008694 _plpgsql_base_yy_delete_buffer exported >> 70 1 00008620 _plpgsql_base_yy_create_buffer exported >> 71 1 00012db0 _plpgsql_ns_additem exported >> 72 1 00008e08 _pg_finfo_plpgsql_call_handler exported >> >> exeinfo output >> >> Module name PLPGSQL >> Operating system OS/2 2.x >> CPU type 80386 >> exe level 0 >> version 0 >> Object Table 00014f75 (2 entries) >> Resource Table 00000080 (0 entries) >> Resident Name Table 00015055 (73 entries) >> Import Module Name Table 00019191 (2 entries) >> Import Proc Name Table 000191a3 >> Nonresident Name Table 00014c40 (39 bytes) >> Debug Information 00019a7e (23463 bytes) >> >> Imported Modules: >> 0 POSTGRES >> 1 libc06b2 >> >> Object Information : >> 1 : ( 84400) READABLE EXECUTABLE >> 2 : ( 880) READABLE WRITEABLE >> >> Total Code 84400 bytes >> Total Data 880 bytes >> Total Res 0 bytes >> >> Resource Information : >> -- ----------------------------------------------------------- lsunley at mb.sympatico.ca -----------------------------------------------------------