From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Thu, 20 Nov 2003 14:15:52 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 246 ************************************************** Wednesday 19 November 2003 Number 246 ************************************************** Subjects for today 1 Re: creating intl/Makefile : John Poltorak 2 wxWindows OS/2 support : John Poltorak 3 wxWindows build errors : John Poltorak 4 Re: wxWindows OS/2 support : Stefan Neis 5 Re: wxWindows build errors : John Poltorak 6 Re: wxWindows build errors : Stefan Neis 7 Re: wxWindows build errors : John Poltorak 8 Re: wxWindows build errors : Stefan Neis 9 Bogofilter : John Poltorak **= Email 1 ==========================** Date: Thu, 20 Nov 2003 10:01:11 +0000 From: John Poltorak Subject: Re: creating intl/Makefile On Wed, Nov 19, 2003 at 05:16:40PM -0500, Henry Sobotka wrote: > John Poltorak wrote: > > > [SNIP] > > > > "libintl_bindtextdomain" > > "libintl_gettext" > > This missing symbols are obviously there. Try renaming intl.a and run > > emximp -o intl.a intl.def > > If the resulting intl.a is the same size as the original, then ld may be > using another one elsewhere on your machine. If the sizes differ, the > failure should go away with the new one. I guess what this really needs is someone who understands these things to try building GETTEXT using UX2BS and seeing what, if anything, is going wrong... > h~ > -- John **= Email 2 ==========================** Date: Thu, 20 Nov 2003 16:09:28 +0000 From: John Poltorak Subject: wxWindows OS/2 support Is there a recommended place for OS/2 support for wxWindows? Or is this list as good as anywhere? Someone on USENET was asking... -- John **= Email 3 ==========================** Date: Thu, 20 Nov 2003 17:42:03 +0000 From: John Poltorak Subject: wxWindows build errors My first attempt to build wxWindows resulted in:- gcc -c -I./lib/wx/include/base-2.4-i386-pc-os2-emx -I./include -I./src/zlib -O2 -MMD -Wall -o mimetype.o ./src/unix/mimetype.cpp gcc -c -I./lib/wx/include/base-2.4-i386-pc-os2-emx -I./include -I./src/zlib -O2 -MMD -Wall -o snglinst.o ./src/unix/snglinst.cpp ./src/unix/snglinst.cpp: In function `int wxLockFile(int, enum LockOperation)': ./src/unix/snglinst.cpp:88: aggregate `struct flock fl' has incomplete type and cannot be initialized ./src/unix/snglinst.cpp:89: `F_WRLCK' undeclared (first use this function) ./src/unix/snglinst.cpp:89: (Each undeclared identifier is reported only once ./src/unix/snglinst.cpp:89: for each function it appears in.) ./src/unix/snglinst.cpp:89: `F_UNLCK' undeclared (first use this function) ./src/unix/snglinst.cpp:99: `F_SETLK' undeclared (first use this function) ./src/unix/snglinst.cpp:99: confused by earlier errors, bailing out make: *** [snglinst.o] Error 1 gcc -c -I./lib/wx/include/base-2.4-i386-pc-os2-emx -I./include -I./src/zlib -O2 -MMD -Wall -o snglinst.o ./src/unix/snglinst.cpp ./src/unix/snglinst.cpp: In function `int wxLockFile(int, enum LockOperation)': ./src/unix/snglinst.cpp:88: aggregate `struct flock fl' has incomplete type and cannot be initialized ./src/unix/snglinst.cpp:89: `F_WRLCK' undeclared (first use this function) ./src/unix/snglinst.cpp:89: (Each undeclared identifier is reported only once ./src/unix/snglinst.cpp:89: for each function it appears in.) ./src/unix/snglinst.cpp:89: `F_UNLCK' undeclared (first use this function) ./src/unix/snglinst.cpp:99: `F_SETLK' undeclared (first use this function) ./src/unix/snglinst.cpp:99: confused by earlier errors, bailing out make: *** [snglinst.o] Error 1 Any clues as to what I have done wrong? I have just run configure & Make. -- John **= Email 4 ==========================** Date: Thu, 20 Nov 2003 17:57:52 +0100 (CET) From: Stefan Neis Subject: Re: wxWindows OS/2 support On Thu, 20 Nov 2003, John Poltorak wrote: > Is there a recommended place for OS/2 support for wxWindows? Well, there are various mailing lists (see http://wxwindows.org/maillst2.htm). The most relevants are probably: - wx-users at lists.wxwindows.org For the general "How can I do (whatever) with wxWindows" questions. - wx-dev at lists.wxwindows.org For stuff like "I want to help with the OS/2 port (or any other part) of wxWindows, how can I do that" - note: there's also the Patch Manager and the Bug Manager reachable via www.wxWindows.org Finally, there's - wxwindows-os2pm at lists.sourceforge.net For the really OS/2 specific questions; however, relatively few people are reading and answering there, so whenever there's a chance that it might not be that OS/2 specific, it's a good idea to use one of the other lists [Typically answers on wxWindows-os2pm come from either David Webster or myself and for both of us, wxWindows is essentially limited to a couple of hours at weekends - and I also want to write some code or fix some bugs in that time...] Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 5 ==========================** Date: Thu, 20 Nov 2003 19:04:26 +0000 From: John Poltorak Subject: Re: wxWindows build errors On Thu, Nov 20, 2003 at 07:39:53PM +0100, Stefan Neis wrote: > On Thu, 20 Nov 2003, John Poltorak wrote: > > > > > My first attempt to build wxWindows resulted in:- > (snipp) > > ./src/unix/snglinst.cpp:99: `F_SETLK' undeclared (first use this function) > > ./src/unix/snglinst.cpp:99: confused by earlier errors, bailing out > > make: *** [snglinst.o] Error 1 > For fixing the problem either use Posix/2 or do > "configure --disable-snglinst". I was already using Posix/2. It gets used by default. And I've just added the configure parameter but the output is identical. BTW I deleted the wxWindows work directory before the second test so nothing was left over from the first test. > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 6 ==========================** Date: Thu, 20 Nov 2003 19:39:53 +0100 (CET) From: Stefan Neis Subject: Re: wxWindows build errors On Thu, 20 Nov 2003, John Poltorak wrote: > > My first attempt to build wxWindows resulted in:- (snipp) > ./src/unix/snglinst.cpp:99: `F_SETLK' undeclared (first use this function) > ./src/unix/snglinst.cpp:99: confused by earlier errors, bailing out > make: *** [snglinst.o] Error 1 > > Any clues as to what I have done wrong? Nothing, it's my error. I just noticed the same problem on that other box where I had problems with configure (For the record: I had installed "antique" versions of diff and GNU shell utilities, which both came with GNUREGEX.DLL (different versions, "of course") and ended up with the wrong DLL being installed). I will have to check if I added some workaround to the code and forget to commit it, or if I just fixed the symptoms and forgot to add that to the installation instructions. For fixing the problem either use Posix/2 or do "configure --disable-snglinst". (Note: wxWindows' configure script stores its arguments in configarg.cache, so once you've passed an argument, it will be implicitly used in the future, if you run configure in the same directory. The drawback of that comfortable approach is that "we" tend to forget to mention needed arguments in installation instructions...). Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 7 ==========================** Date: Thu, 20 Nov 2003 20:29:27 +0000 From: John Poltorak Subject: Re: wxWindows build errors On Thu, Nov 20, 2003 at 08:33:01PM +0100, Stefan Neis wrote: > On Thu, 20 Nov 2003, John Poltorak wrote: > > > > For fixing the problem either use Posix/2 or do > > > "configure --disable-snglinst". > > > > I was already using Posix/2. It gets used by default. > > Strange... > > > And I've just added the configure parameter but the output is identical. > > In case you have a "yes" in that second line, there must have been a typo Indeed it was a typo, sorry about that. This time it gets as far as:- gcc -c -I./lib/wx/include/base-2.4-i386-pc-os2-emx -I./include -I./src/zlib -O2 -MMD -Wall -o threadpsx.o ./src/unix/threadpsx.cpp gcc -c -I./lib/wx/include/base-2.4-i386-pc-os2-emx -I./include -I./src/zlib -O2 -MMD -Wall -o utilsunx.o ./src/unix/utilsunx.cpp ./src/unix/utilsunx.cpp:41: warning: No include path in which to find sys/vfs.h ./src/unix/utilsunx.cpp: In method `bool wxPipeInputStream::CanRead() const': ./src/unix/utilsunx.cpp:389: warning: implicit declaration of function `int select(...)' ./src/unix/utilsunx.cpp: In function `bool wxGetDiskSpace(const class wxString &, class wxLongLongWx * = 0, class wxLongLongWx * = 0)': ./src/unix/utilsunx.cpp:1042: aggregate `struct statfs fs' has incomplete type and cannot be initialized ./src/unix/utilsunx.cpp:1043: confused by earlier errors, bailing out make: *** [utilsunx.o] Error 1 gcc -c -I./lib/wx/include/base-2.4-i386-pc-os2-emx -I./include -I./src/zlib -O2 -MMD -Wall -o utilsunx.o ./src/unix/utilsunx.cpp ./src/unix/utilsunx.cpp:41: warning: No include path in which to find sys/vfs.h ./src/unix/utilsunx.cpp: In method `bool wxPipeInputStream::CanRead() const': ./src/unix/utilsunx.cpp:389: warning: implicit declaration of function `int select(...)' ./src/unix/utilsunx.cpp: In function `bool wxGetDiskSpace(const class wxString &, class wxLongLongWx * = 0, class wxLongLongWx * = 0)': ./src/unix/utilsunx.cpp:1042: aggregate `struct statfs fs' has incomplete type and cannot be initialized ./src/unix/utilsunx.cpp:1043: confused by earlier errors, bailing out make: *** [utilsunx.o] Error 1 > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 8 ==========================** Date: Thu, 20 Nov 2003 20:33:01 +0100 (CET) From: Stefan Neis Subject: Re: wxWindows build errors On Thu, 20 Nov 2003, John Poltorak wrote: > > For fixing the problem either use Posix/2 or do > > "configure --disable-snglinst". > > I was already using Posix/2. It gets used by default. Strange... > And I've just added the configure parameter but the output is identical. That's even stranger - it worked for me just two hours ago ... Could you grep for sngl in config.log? Over here, I get: > configure:5291: checking for --enable-snglinst > ac_cv_use_snglinst='wxUSE_SNGLINST_CHECKER=no' In case you have a "yes" in that second line, there must have been a typo in your argument to configure, in case you have a "no" in there, it really just can't give that error. ;-) Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 9 ==========================** Date: Thu, 20 Nov 2003 22:35:33 +0000 From: John Poltorak Subject: Bogofilter How easy is it to build Bogofilter? Does it need any OS/2 patches? -- John