Date: Sat, 1 May 2004 00:04:20 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 365 ************************************************** Friday 30 April 2004 Number 365 ************************************************** Subjects for today 1 Re: Makefile.am for PATCH : John Poltorak 2 Re: Makefile.am for PATCH : John Poltorak 3 Re: Makefile.am for PATCH : Pete Milne 4 EMACS : John Poltorak 5 Re: TeX Directory Structure : Michael Zolk 6 Re: EMACS : Henry Sobotka 7 Re: EMACS : John Poltorak 8 Re: EMACS : Christian Hennecke" 9 Re: EMACS : John Poltorak 10 Re: INFO files : John Poltorak 11 Re: INFO files : Henry Sobotka 12 Building EMACS v20.7 : John Poltorak 13 Re: EMACS : Christian Hennecke" 14 Re: EMACS : John Poltorak 15 Re: EMACS : Christian Hennecke" 16 Re: DLL for GNU text utils : Andreas Buening 17 Re: _lstat : Andreas Buening 18 Re: DLL for GNU text utils : John Poltorak 19 Re: EMACS : John Poltorak **= Email 1 ==========================** Date: Thu, 29 Apr 2004 14:53:43 +0100 From: John Poltorak Subject: Re: Makefile.am for PATCH On Thu, Apr 29, 2004 at 02:33:02PM +0100, John Poltorak wrote: > On Thu, Apr 29, 2004 at 03:00:03PM +0200, Sebastian Wittmeier wrote: > > On Wed, 28 Apr 2004 22:43:31 +0100, John Poltorak wrote: > > > > >gcc -DHAVE_CONFIG_H -I. -I. -I. -c error.c > > >error.c: In function `error': > > >error.c:125: argument `message' doesn't match prototype > > >error.h:50: prototype declaration > > > > > > > > >Any ideas? > > > > I experimented a bit - what helped was to define one of those: > > > > /* Define if you don't have vprintf but do have _doprnt. */ > > #define HAVE_DOPRNT > > > > /* Define if you have the vprintf function. */ > > #define HAVE_VPRINTF > > Are they defined in config.h ? > > AIUI config.h is generated through entries in configure.in, so what would > you need to add to configure.in? Just to answer my own question... In order to add these lines to config.hin:- /* config.hin. Generated from configure.in by autoheader. */ /* Define to 1 if you don't have `vprintf' but do have `_doprnt.' */ #undef HAVE_DOPRNT /* Define to 1 if you have the `vprintf' function. */ #undef HAVE_VPRINTF You need to add this line to configure.in:- AC_FUNC_VPRINTF But when configure runs, this error occurs:- config.status:685: creating Makefile config.status:789: creating config.h config.status:1055: executing depfiles commands configure:4229: checking for vprintf configure:4286: gcc -o conftest.exe conftest.c >&5 configure:4292: $? = 0 configure:4296: test -z || test ! -s conftest.err configure:4299: $? = 0 configure:4302: test -s conftest.exe configure:4305: $? = 0 configure:4317: result: yes configure:4324: checking for _doprnt configure:4381: gcc -o conftest.exe conftest.c >&5 c:\tmp\ccc10446: Undefined symbol __doprnt referenced from text segment c:\tmp\ccc10446: Undefined symbol __doprnt referenced from data segment configure:4387: $? = 1 So HAVE_VPRINT stays as #undef -- John **= Email 2 ==========================** Date: Thu, 29 Apr 2004 15:15:50 +0100 From: John Poltorak Subject: Re: Makefile.am for PATCH On Wed, Apr 28, 2004 at 10:43:31PM +0100, John Poltorak wrote: > On Tue, Apr 27, 2004 at 08:49:06PM +0200, Andreas Buening wrote: > > John Poltorak wrote: > > Well all I have in Makefile.am at the moment is:- > > > > bin_PROGRAMS = patch > patch_SOURCES = addext.c argmatch.c backupfile.c basename.c error.c inp.c maketime.c mkdir.c partime.c patch.c pch.c quotearg.c quotesys.c rmdir.c util.c version.c xmalloc.c argmatch.h backupfile.h basename.h common.h error.h getopt.h inp.h maketime.h partime.h patchlevel.h pch.h quotearg.h quotesys.h util.h version.h xalloc.h > > which appears to help produce a Makefile that does start compiling some of > these files but ends with:- > > gcc -DHAVE_CONFIG_H -I. -I. -I. -c backupfile.c > source='basename.c' object='basename.o' libtool=no \ > depfile='.deps/basename.Po' tmpdepfile='.deps/basename.TPo' \ > depmode=gcc c:/bin/sh ./depcomp \ > gcc -DHAVE_CONFIG_H -I. -I. -I. -c basename.c > source='error.c' object='error.o' libtool=no \ > depfile='.deps/error.Po' tmpdepfile='.deps/error.TPo' \ > depmode=gcc c:/bin/sh ./depcomp \ > gcc -DHAVE_CONFIG_H -I. -I. -I. -c error.c > error.c: In function `error': > error.c:125: argument `message' doesn't match prototype > error.h:50: prototype declaration > > > Any ideas? Some progress at last after adding these lines to configure.in:- AC_PROG_INSTALL AC_PROG_MAKE_SET # Use ed_PROGRAM, not ED_PROGRAM, # because reserves symbols starting with `E'. AC_PATH_PROG(ed_PROGRAM, ed, ed) Hopefully, one day all this will start to make sense... Next error:- gcc -DHAVE_CONFIG_H -I. -I. -I. -c mkdir.c mkdir.c:62: conflicting types for `mkdir' c:\ux2bs\emx\include\sys/stat.h:73: previous declaration of `mkdir' mkdir.c: In function `mkdir': mkdir.c:83: `P_WAIT' undeclared (first use in this function) mkdir.c:83: (Each undeclared identifier is reported only once mkdir.c:83: for each function it appears in.) make[1]: *** [mkdir.o] Error 1 -- John **= Email 3 ==========================** Date: Thu, 29 Apr 2004 17:25:40 +0100 From: Pete Milne Subject: Re: Makefile.am for PATCH Sebastian Wittmeier wrote: >On Wed, 28 Apr 2004 22:43:31 +0100, John Poltorak wrote: > > > >>gcc -DHAVE_CONFIG_H -I. -I. -I. -c error.c >>error.c: In function `error': >>error.c:125: argument `message' doesn't match prototype >>error.h:50: prototype declaration >> >> >>Any ideas? >> >> > >I experimented a bit - what helped was to define one of those: > >/* Define if you don't have vprintf but do have _doprnt. */ >#define HAVE_DOPRNT > >/* Define if you have the vprintf function. */ >#define HAVE_VPRINTF > >Does anybody know, what the difference is, and if they exist on OS/2? > >Sebastian > > > > > > vprintf is printf with a va_list argument instead of a variable number of arguments. It's implemented in EMX. _doprnt is a low-level function; I'm not sure whether it exists in EMX, but it's probably better to use vprintf anyway. hth, Pete **= Email 4 ==========================** Date: Thu, 29 Apr 2004 20:10:48 +0100 From: John Poltorak Subject: EMACS I've just managed to build EMACS v20.7 using some instructions I had, and it wasn't too tricky at all. What I'd like to know is how do I bring the app up as a PM app. It comes up as a text mode app when I run 'emacs -nw'. Where would I find a list of the available command line options? -- John **= Email 5 ==========================** Date: Thu, 29 Apr 2004 21:22:41 +0200 From: Michael Zolk Subject: Re: TeX Directory Structure On Thu, Apr 29, 2004 at 10:58:01AM +0100, John Poltorak wrote: > On Wed, Apr 28, 2004 at 10:29:10PM +0200, Michael Zolk wrote: > > > If this was to be used in UnixOS/2, where should texmf go? > > > > > > Should we have /usr/local/share/texmf ? > > > > > > Anyone have a handy Unix system with TeX installed? > > > > On my Debian system, it's /usr/share/texmf. > > Where do the binaries go? /usr/bin ? Yes. > Do they have the same names as they do in emTeX? AFAICS I have these TeX-related files in /usr/bin (from tetex 2.0.2): lrwxrwxrwx 1 root root 3 Mar 21 23:17 /usr/bin/amstex -> tex -rwxr-xr-x 1 root root 86552 Mar 5 00:36 /usr/bin/bibtex lrwxrwxrwx 1 root root 4 Mar 21 22:54 /usr/bin/einitex -> etex lrwxrwxrwx 1 root root 4 Mar 21 23:17 /usr/bin/elatex -> etex -rwxr-xr-x 1 root root 272824 Mar 5 00:36 /usr/bin/etex lrwxrwxrwx 1 root root 4 Mar 21 22:54 /usr/bin/evirtex -> etex lrwxrwxrwx 1 root root 3 Mar 21 22:54 /usr/bin/initex -> tex lrwxrwxrwx 1 root root 3 Mar 21 23:17 /usr/bin/latex -> tex lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/mktexfmt -> fmtutil -rwxr-xr-x 1 root root 4484 Mar 5 00:35 /usr/bin/mktexlsr -rwxr-xr-x 1 root root 3795 Mar 5 00:35 /usr/bin/mktexmf -rwxr-xr-x 1 root root 8759 Mar 5 00:35 /usr/bin/mktexpk -rwxr-xr-x 1 root root 4325 Mar 5 00:35 /usr/bin/mktextfm lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/pdfeinitex -> pdfetex lrwxrwxrwx 1 root root 7 Mar 21 23:17 /usr/bin/pdfelatex -> pdfetex -rwxr-xr-x 1 root root 828584 Mar 5 00:36 /usr/bin/pdfetex lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/pdfevirtex -> pdfetex lrwxrwxrwx 1 root root 6 Mar 21 22:54 /usr/bin/pdfinitex -> pdftex lrwxrwxrwx 1 root root 6 Mar 21 23:17 /usr/bin/pdflatex -> pdftex -rwxr-xr-x 1 root root 787624 Mar 5 00:36 /usr/bin/pdftex lrwxrwxrwx 1 root root 6 Mar 21 22:54 /usr/bin/pdfvirtex -> pdftex -rwxr-xr-x 1 root root 980 Mar 5 00:35 /usr/bin/pslatex -rwxr-xr-x 1 root root 1627 Mar 5 00:35 /usr/bin/rubibtex -rwxr-xr-x 1 root root 235768 Mar 5 00:36 /usr/bin/tex -rwxr-xr-x 1 root root 54660 Mar 5 00:35 /usr/bin/texconfig -rwxr-xr-x 1 root root 4531 Mar 5 00:35 /usr/bin/texdoc -rwxr-xr-x 1 root root 54632 Mar 5 00:35 /usr/bin/texdoctk -rwxr-xr-x 1 root root 718 Mar 5 00:35 /usr/bin/texexec lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/texfind -> texexec lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/texfont -> texexec lrwxrwxrwx 1 root root 8 Mar 21 22:54 /usr/bin/texhash -> mktexlsr -rwxr-xr-x 1 root root 14616 Jul 12 2003 /usr/bin/texindex -rwxr-xr-x 1 root root 8779 Mar 5 00:35 /usr/bin/texlinks lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/texshow -> texexec lrwxrwxrwx 1 root root 7 Mar 21 22:54 /usr/bin/texutil -> texexec lrwxrwxrwx 1 root root 3 Mar 21 22:54 /usr/bin/virtex -> tex lrwxrwxrwx 1 root root 3 Mar 21 23:17 /usr/bin/mf -> mfw -rwxr-xr-x 1 root root 207000 Mar 5 00:36 /usr/bin/mf-nowin -rwxr-xr-x 1 root root 44440 Mar 5 00:36 /usr/bin/mft -rwxr-xr-x 1 root root 208184 Mar 5 00:36 /usr/bin/mfw Michael -- **= Email 6 ==========================** Date: Thu, 29 Apr 2004 16:18:35 -0400 From: Henry Sobotka Subject: Re: EMACS John Poltorak wrote: > > What I'd like to know is how do I bring the app up as a PM app. It comes > up as a text mode app when I run 'emacs -nw'. emacs -pm > Where would I find a list of the available command line options? emacs --help h~ **= Email 7 ==========================** Date: Thu, 29 Apr 2004 21:38:14 +0100 From: John Poltorak Subject: Re: EMACS On Thu, Apr 29, 2004 at 04:18:35PM -0400, Henry Sobotka wrote: > John Poltorak wrote: > > > > What I'd like to know is how do I bring the app up as a PM app. It comes > > up as a text mode app when I run 'emacs -nw'. Actually, I've found that it comes up in PM without any options. > emacs -pm That doesn't work in 20.7. > > Where would I find a list of the available command line options? > > emacs --help Any idea on how I can use a different font? I have a large courier font and would prefer a small System Vio font if I can have one - I like to get as much on the screen as possible. > h~ -- John **= Email 8 ==========================** Date: Thu, 29 Apr 2004 23:25:40 +0200 (CEST) From: "Christian Hennecke" Subject: Re: EMACS On Thu, 29 Apr 2004 21:38:14 +0100, John Poltorak wrote: >Any idea on how I can use a different font? > >I have a large courier font and would prefer a small System Vio font if I >can have one - I like to get as much on the screen as possible. You need to adapt site-start.el or something like that. Let's see... I have the following in there: (if (eq window-system 'pm) (setq default-frame-alist (append '((altgr-modifier . meta) ; AltGr (and AltCar) generate M- (shortcuts . (alt-f4)) ; Disable all shortcuts but Alt+F4 ;; (alt-modifier . alt) (alt-modifier . meta) (width . 100) (height . 40) ;; (bottom . 10) (left . 140) (font . "5.System VIO") ;; (menu-font . "2.System VIO") (menu-font . "9.WarpSans")) ; Use small font for menus default-frame-alist))) The second last line changes the menu font to a 9 pt WarpSans font. Christian Hennecke **= Email 9 ==========================** Date: Thu, 29 Apr 2004 22:47:02 +0100 From: John Poltorak Subject: Re: EMACS On Thu, Apr 29, 2004 at 11:25:40PM +0200, Christian Hennecke wrote: > On Thu, 29 Apr 2004 21:38:14 +0100, John Poltorak wrote: > > >Any idea on how I can use a different font? > > > >I have a large courier font and would prefer a small System Vio font if I > >can have one - I like to get as much on the screen as possible. > > You need to adapt site-start.el or something like that. Should I expect to find a site-start.el in my build? > Let's see... I > have the following in there: > > (if (eq window-system 'pm) > (setq default-frame-alist > (append '((altgr-modifier . meta) ; AltGr (and AltCar) > generate M- > (shortcuts . (alt-f4)) ; Disable all shortcuts but > Alt+F4 > ;; (alt-modifier . alt) > (alt-modifier . meta) > (width . 100) (height . 40) > ;; (bottom . 10) (left . 140) > (font . "5.System VIO") > ;; (menu-font . "2.System VIO") > (menu-font . "9.WarpSans")) ; Use small font for > menus > default-frame-alist))) > > The second last line changes the menu font to a 9 pt WarpSans font. Is there a way to change the font of the editor? > Christian Hennecke -- John **= Email 10 ==========================** Date: Thu, 29 Apr 2004 23:24:10 +0100 From: John Poltorak Subject: Re: INFO files On Thu, Apr 08, 2004 at 07:09:27AM -0400, Henry Sobotka wrote: > John Poltorak wrote: > > > > Is there a PM Info viewer available? > > > > Or maybe an INFO to INF converter? > > > > I find INFO files to be quite useful but the text mode viewer is a little > > awkward to use. > > Emacs works nicely. Add any directory with INFO files to INFOPATH, > create an entry for it in emx/info/dir and you can then view them from > Help->Browse Manuals. I've just managed to get this working, and it certainly beats INFO! I'm still trying to find the easiest way of navigating the system, but I think I might be able to read something about the commands I've bee using now :-)... > h~ > -- > Free software, free minds. -- John **= Email 11 ==========================** Date: Thu, 29 Apr 2004 19:53:27 -0400 From: Henry Sobotka Subject: Re: INFO files John Poltorak wrote: > > I've just managed to get this working, and it certainly beats INFO! > > I'm still trying to find the easiest way of navigating the system, but I > think I might be able to read something about the commands I've bee using > now :-)... When the cursor is over a link, it becomes highlighted and a right mouseclick opens it. The same applies to the navigation bar at the top of each page. h~ **= Email 12 ==========================** Date: Fri, 30 Apr 2004 10:12:19 +0100 From: John Poltorak Subject: Building EMACS v20.7 If anyone has a few spare minutes could you try running this batch file and seeing how far it gets in building EMACS? 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 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. call configure.cmd --with-bsd-socket --with-xf86sup-pty SET INCLUDE=%C_INCLUDE_PATH% make You do need the standard GNU set of apps and gcc in your environment, as well as RC - IBM Resource Compiler. You also need to provide the name of the GNU Patch program you are using when asked. -- John **= Email 13 ==========================** Date: Fri, 30 Apr 2004 12:06:46 +0200 (CEST) From: "Christian Hennecke" Subject: Re: EMACS On Thu, 29 Apr 2004 22:47:02 +0100, John Poltorak wrote: >> You need to adapt site-start.el or something like that. > >Should I expect to find a site-start.el in my build? I think so. If it's not there, create one. >Is there a way to change the font of the editor? See (font . "5.System VIO") in the section I mentioned before. Christian Hennecke **= Email 14 ==========================** Date: Fri, 30 Apr 2004 11:17:48 +0100 From: John Poltorak Subject: Re: EMACS On Fri, Apr 30, 2004 at 12:06:46PM +0200, Christian Hennecke wrote: > On Thu, 29 Apr 2004 22:47:02 +0100, John Poltorak wrote: > > >> You need to adapt site-start.el or something like that. > > > >Should I expect to find a site-start.el in my build? > > I think so. If it's not there, create one. Where do I put it? > >Is there a way to change the font of the editor? > > See > > (font . "5.System VIO") > > in the section I mentioned before. Was the formatting OK in your msg? It didn't look right to me - maybe it got line-wrapped or somesuch... Is there an explanation of the format or any other documentation about site-start.el? I have a couple of books on EMACS and neither mentions it, and I'm not familiar enough with EMACS itself to know where to find such info. > > Christian Hennecke -- John **= Email 15 ==========================** Date: Fri, 30 Apr 2004 13:17:05 +0200 (CEST) From: "Christian Hennecke" Subject: Re: EMACS On Fri, 30 Apr 2004 11:17:48 +0100, John Poltorak wrote: >> >Should I expect to find a site-start.el in my build? >> >> I think so. If it's not there, create one. > >Where do I put it? In the "lisp" subdirectory. >> >Is there a way to change the font of the editor? >> >> See >> >> (font . "5.System VIO") >> >> in the section I mentioned before. > >Was the formatting OK in your msg? > >It didn't look right to me - maybe it got line-wrapped or somesuch... Yes, the formatting got mixed up. Take a look at README.OS2 from Emacs 20.6 for OS/2, chapters "Customizing GNU Emacs" and "Choosing a PM font". This file contains a wealth of information. >Is there an explanation of the format or any other documentation about >site-start.el? I have a couple of books on EMACS and neither mentions it, >and I'm not familiar enough with EMACS itself to know where to find such >info. To my knowledge, all those things can also be placed in .emacs. Site-start.el was intended to contain system-wide customizations, while ..emacs is for a specific user and resides in his/her home directory. As for documentation of the format, it's all written in ELISP. The Emacs documentation deals with that. Christian Hennecke **= Email 16 ==========================** Date: Wed, 28 Apr 2004 20:34:38 +0200 From: Andreas Buening Subject: Re: DLL for GNU text utils John Poltorak wrote: > I assumed the procedure was to run libtoolize before any of the auto* > tools, but that didn't have the desired affect, so I guess there is some > additional procedure required. > > Do I also need to add AC_PROG_LIBTOOL to configure.in? FAQ: AC_LIBTOOL_WIN32_DLL AC_PROG_LIBTOOL in exactly that order. And, whatever you're going to do, it will never be incorporated into the main source. libtu is just for internal use to make the build easier. Bye, Andreas **= Email 17 ==========================** Date: Wed, 28 Apr 2004 20:34:17 +0200 From: Andreas Buening Subject: Re: _lstat John Poltorak wrote: > > On Tue, Apr 27, 2004 at 09:51:04PM +0200, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > On Sat, Apr 24, 2004 at 08:16:38AM -0800, Dave Yeo wrote: > > > > On Sat, 24 Apr 2004 10:13:50 +0100, John Poltorak wrote: > > > > > > > > >Actually, after digging through my archives I found the solution suggested > > > > >by Andreas the last time it happened - that was to run autoheader after > > > > >autoconf. This solution worked perfectly well with MKTEMP v1.4 when I last > > > > >tried it and also with the newer version (1.5) when I tried it yesterday. > > > > >The thing is it only works using the OS/2 version of Autoconf v2.50, not > > > > >the latest version. Maybe some experimental code was put in and then taken > > > > >out. > > > > Exactly. I put it out because automagical stuff tends to cause > > problems sometimes. > > > > Solutions (FAQ candidate?): > > Possibly, but only after it works ;-)... > > > > 1) CPPFLAGS="-Dlstat" > > This seemed like the easiest option, but I got these compile errors:- Ok. CPPFLAGS="-Dlstat=stat" Bye, Andreas **= Email 18 ==========================** Date: Fri, 30 Apr 2004 12:52:23 +0100 From: John Poltorak Subject: Re: DLL for GNU text utils On Wed, Apr 28, 2004 at 08:34:38PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > I assumed the procedure was to run libtoolize before any of the auto* > > tools, but that didn't have the desired affect, so I guess there is some > > additional procedure required. > > > > Do I also need to add AC_PROG_LIBTOOL to configure.in? > > FAQ: > > AC_LIBTOOL_WIN32_DLL > AC_PROG_LIBTOOL > > in exactly that order. Which version of Autoconf accepts these macros? I'm building the GNU Textutils with v2.50 > And, whatever you're going to do, > it will never be incorporated into the main source. libtu > is just for internal use to make the build easier. This is only for my use in an attempt to replicate what we have had on OS/2 for many years with gnutu.dll. > Bye, > Andreas -- John **= Email 19 ==========================** Date: Fri, 30 Apr 2004 14:44:28 +0100 From: John Poltorak Subject: Re: EMACS On Fri, Apr 30, 2004 at 01:17:05PM +0200, Christian Hennecke wrote: > >Was the formatting OK in your msg? > > > >It didn't look right to me - maybe it got line-wrapped or somesuch... > > Yes, the formatting got mixed up. Take a look at README.OS2 from Emacs > 20.6 for OS/2, chapters "Customizing GNU Emacs" and "Choosing a PM > font". This file contains a wealth of information. It looks as though it doesn't work in 20.7 :-(... The ports seem to have developed seperately. It would be nice to try and consolidate them, but I don't know if either porting is still using OS/2. > Christian Hennecke -- John