From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Wed, 25 Sep 2002 04:37:13 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 328 ************************************************** Tuesday 24 September 2002 Number 328 ************************************************** Subjects for today 1 Re: PostNuke : John Poltorak 2 Some news : Andreas Buening 3 Re: PostNuke : Voytek Eymont 4 Re: Some news : Stefan Neis 5 Latest gdb : Yuri Prokushev" 6 gcc 3.0.3: compiler / linker crash : Thomas Hoffmann **= Email 1 ==========================** Date: Wed, 25 Sep 2002 09:24:49 +0100 From: John Poltorak Subject: Re: PostNuke On Wed, Sep 25, 2002 at 02:01:53PM +0000, Voytek Eymont wrote: > ** Reply to note from Steve Wendt Tue, 24 Sep 2002 18:07:55 -0700 (PDT) > > > > > Has anyone successfully installed PostNuke? > > I have, it just worked Which version of PostNuke and PHP? Is it possible to edit the config file rather than using admin.php to configure it? > all I need to know, how to config it's mailing with Hethmon's hmailer.. > then I could use it... How about Sendmail? > Voytek Eymont > SBT Information Systems Pty Ltd > http://www.sbt.net.au/links/ > phone +61-2 9310-1144 fax +61-2 9310-1118 -- John **= Email 2 ==========================** Date: Wed, 25 Sep 2002 11:29:31 +0200 From: Andreas Buening Subject: Some news Hello! I've uploaded some packages that comply with our new file system structure: iconv/2 0.1.2 a native replacement for GNU iconv libunixos2 0.1.1 It contains GNU regex and I've also added the new posix_spawn interface (originally from glibc). It's basically an alternative way to start processes without fork(). There are some GNU frontends to use either posix_spawn or fork() and the new gettext requires one of them, so I've implemented posix_spawn. However, it might still buggy (not really tested). m4 1.4 Recompiled with libunixos2. gettext 0.11.2 beta Uses iconv2 (statically linked) and libunixos2. It's more a proof of concept than a fully featured package. :-) For the next weeks I'll have no time, so I have the following schedule: 14 Oct: newest gettext 21 Oct: recompilation of several packages (grep, sed, textutils, ...) 28 Oct: autoconf, automake, (libtool?) However, everybody here is appealed for contacting Ian to get ftp access on unixos2.com to upload his own packages. :-) bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie. **= Email 3 ==========================** Date: Wed, 25 Sep 2002 14:01:53 From: Voytek Eymont Subject: Re: PostNuke ** Reply to note from Steve Wendt Tue, 24 Sep 2002 18:07:55 -0700 (PDT) > > Has anyone successfully installed PostNuke? I have, it just worked all I need to know, how to config it's mailing with Hethmon's hmailer.. then I could use it... Voytek Eymont SBT Information Systems Pty Ltd http://www.sbt.net.au/links/ phone +61-2 9310-1144 fax +61-2 9310-1118 **= Email 4 ==========================** Date: Wed, 25 Sep 2002 18:55:58 +0200 (CEST) From: Stefan Neis Subject: Re: Some news On Wed, 25 Sep 2002, Andreas Buening wrote: > posix_spawn or fork() and the new gettext > requires one of them, so I've implemented posix_spawn. That's the first time I hear something about posix_spawn. What's the difference between posix_spawn and "normal" spawn? BTW, is there a way to efficiently start a new process from a shared/object, DLL under OS/2? Under Unix I can use fork, under Windows I can spawn "rundll32 my_dll,startup_function_of_child" but I have no idea what to do under OS/2 (well, fork will work for my purposes, but it's not exactly efficient under OS/2 ...) Regards, Stefan **= Email 5 ==========================** Date: Wed, 25 Sep 2002 20:37:55 +0400 (EDT) From: "Yuri Prokushev" Subject: Latest gdb Hello, *. Which version of gdb/2 latest for now? Bye. **= Email 6 ==========================** Date: Wed, 25 Sep 2002 23:24:01 +0100 From: Thomas Hoffmann Subject: gcc 3.0.3: compiler / linker crash The "weak*" programs from emx's test directory are possibly of some interest to the gcc 3.03 porters: I got gcc / ld crashes which should not happen even with defective code, this is the story: Makefile: ========= gcc -g -Wall -c weak1.c gcc -g -Wall -c weak2.s gcc -g -Wall -o weak01.exe weak1.o weak2.o gcc -g -Wall -o weak02.exe weak2.o weak1.o gcc -g -Wall -c weak3.c gcc -g -Wall -o weak11.exe weak1.o weak2.o weak3.o gcc -g -Wall -o weak12.exe weak1.o weak3.o weak2.o gcc -g -Wall -o weak13.exe weak2.o weak1.o weak3.o gcc -g -Wall -o weak14.exe weak2.o weak3.o weak1.o gcc -g -Wall -o weak15.exe weak3.o weak1.o weak2.o gcc -g -Wall -o weak16.exe weak3.o weak2.o weak1.o weak01 weak weak02 weak weak11 strong weak12 strong weak13 strong weak14 strong weak15 strong weak16 strong Sources: ======== weak1.c: /* weak1.c (emx+gcc) */ #include #include extern const char *weak (void); int main (int argc, char *argv[]) { const char *t; if (argc != 2) { puts ("Incorrect command line"); return 1; } t = weak (); puts (t); return strcmp (t, argv[1]) != 0 ? 1 : 0; } weak2.s: / weak2.s (emx+gcc) .weak _strong .text .global _weak _weak: leal _strong, %eax testl %eax, %eax jnz _strong lea L1, %eax ret L1: .ascii "weak" .byte 0 weak3.c: /* weak3.c (emx+gcc) */ const char *strong (void) { return "strong"; } Results: ======== gcc -g -Wall -c weak1.c gcc -g -Wall -c weak2.s gcc -g -Wall -o weak01.exe weak1.o weak2.o weak2.o: Undefined symbol _strong referenced from text segment weak2.o: Undefined symbol _strong referenced from text segment make.exe: *** [weak01.exe] Fehler 1 gcc -g -Wall -o weak02.exe weak2.o weak1.o weak2.o: Undefined symbol _strong referenced from text segment weak2.o: Undefined symbol _strong referenced from text segment make.exe: *** [weak02.exe] Fehler 1 gcc -g -Wall -c weak3.c gcc -g -Wall -o weak11.exe weak1.o weak2.o weak3.o gcc -g -Wall -o weak12.exe weak1.o weak3.o weak2.o Process terminated by SIGSEGV gcc: Internal error: Segmentation fault (program ld) Please submit a full bug report. See for instructions. make.exe: *** [weak12.exe] Fehler 1 gcc -g -Wall -o weak13.exe weak2.o weak1.o weak3.o gcc -g -Wall -o weak14.exe weak2.o weak3.o weak1.o gcc -g -Wall -o weak15.exe weak3.o weak1.o weak2.o Process terminated by SIGSEGV gcc: Internal error: Segmentation fault (program ld) Please submit a full bug report. See for instructions. make.exe: *** [weak15.exe] Fehler 1 gcc -g -Wall -o weak16.exe weak3.o weak2.o weak1.o Process terminated by SIGSEGV gcc: Internal error: Segmentation fault (program ld) Please submit a full bug report. See for instructions. make.exe: *** [weak16.exe] Fehler 1 -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ...