Date: Thu, 29 Apr 2004 00:04:21 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 363 ************************************************** Wednesday 28 April 2004 Number 363 ************************************************** Subjects for today 1 Re: AM_GNU_GETTEXT not found in library : John Poltorak 2 Re: Installing emTeX : Pete Milne 3 Re: eval : John Poltorak 4 Re: eval : Sebastian Wittmeier" 5 Re: eval : John Poltorak 6 Re: AM_GNU_GETTEXT not found in library : Thomas Dickey 7 Re: Installing emTeX : John Poltorak 8 Re: eval : Stefan.Neis at t-online.de 9 Re: AM_GNU_GETTEXT not found in library : Andreas Buening 10 Re: Makefile.am for PATCH : Andreas Buening 11 Re: TeX : Andreas Buening 12 Re: The system cannot find the command process in the path : Andreas Buening 13 Re: eval : Andreas Buening 14 Re: DLL for GNU text utils : Andreas Buening 15 Re: Bug report: INSTALLPKG.CMD : Michael Zolk 16 Re: _lstat : Andreas Buening 17 Re: AM_GNU_GETTEXT not found in library : Thomas Dickey 18 Re: TeX : arnstein.prytz at jcu.edu.au 19 Re: Installing emTeX : John Poltorak 20 Re: TeX : John Poltorak 21 Re: DLL for GNU text utils : John Poltorak 22 Re: Emacs : Stefan.Neis at t-online.de 23 Re: TeX : Stefan.Neis at t-online.de 24 Re: Installing emTeX : Stefan.Neis at t-online.de **= Email 1 ==========================** Date: Tue, 27 Apr 2004 15:40:05 +0100 From: John Poltorak Subject: Re: AM_GNU_GETTEXT not found in library On Tue, Apr 27, 2004 at 07:57:46AM -0400, Thomas Dickey wrote: > On Tue, 27 Apr 2004, John Poltorak wrote: > > > On Tue, Apr 27, 2004 at 11:44:08AM +0100, John Poltorak wrote: > > > > > The configure.ac file contains:- > > > > > > AM_GNU_GETTEXT > > "AM" is automake. It includes a number of macros that belong in autoconf. How do any of the auto* tools establish a search path fot their macros? And are those macros added to by other applications? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 2 ==========================** Date: Tue, 27 Apr 2004 15:37:22 +0100 From: Pete Milne Subject: Re: Installing emTeX John Poltorak wrote: >Having read through the INSTALL.ENG doc which comes with emTeX I've put >together this batch file which should be able to install emTeX assuming >that all the required files from here:- > >http://www.tug.org/tex-archive/systems/os2/emtex/ > >are in the current directory. > >Can anyone point out any flaws in this file:- ? > > >set path=\emtex\bin;%path% >set emtexdir=\emtex >rem ------------------------------------------ >rem FIRST >rem ------------------------------------------ >unzip first -d / >rem ------------------------------------------ >rem TeX Compiler >rem ------------------------------------------ >unzip tex4b -d / >unzip l2input -d / >unzip latex209 -d / >unzip fontltx -d / >setlocal >cd \emtex\btexfmts >makefmt 386 plain US >makefmt 386 latex2e US 8bit -b \emtex\bin\latex2e >cd \emtex\dist\latex\packages\tools >latex2e tools.ins >copy *.tex \emtex\texinput\latex2e >copy *.sty \emtex\texinput\latex2e >endlocal >unzip texware -d / >rem ------------------------------------------ >rem METAFONT >rem ------------------------------------------ >unzip mf4b -d / >unzip mfjob12d -d / >unzip fontcm -d / >unzip fontec -d / >unzip fontltx -d / >unzip fontams -d / >unzip fontemsy -d / >setlocal >cd \emtex\bmfbases >makebas 386 plain >endlocal >rem ------------------------------------------ >rem print drivers, screen previewers, fonts >rem ------------------------------------------ >md \texfonts >copy bj_base.fli \texfonts >copy dj_base.fli \texfonts >copy fax_base.fli \texfonts >copy fx_base.fli \texfonts >copy ito_base.fli \texfonts >copy ljh_base.fli \texfonts >copy lj_base.fli \texfonts >copy p6h_base.fli \texfonts >copy p6l_base.fli \texfonts >copy p6m_base.fli \texfonts >copy qj_base.fli \texfonts >copy sty_base.fli \texfonts >rem ------------------------------------------ >rem MakeIndex >rem ------------------------------------------ >unzip makeindx -d / >rem ------------------------------------------ >rem BibTeX >rem ------------------------------------------ >unzip bibtex4b -d / >rem ------------------------------------------ >rem TeXcad >rem ------------------------------------------ >unzip makeindx -d / >rem ------------------------------------------ >rem dvispell >rem ------------------------------------------ >unzip dvisp10b -d / >setlocal >dvisprep \emtex\data\plain.dsi >endlocal >rem ------------------------------------------ >rem PiCTeX >rem ------------------------------------------ >unzip pictex -d / >rem ------------------------------------------ >rem WEB >rem ------------------------------------------ >unzip web -d / > > > >This doesn't work, BTW. It ends with some indecipherable error msg here:- > >setlocal >cd \emtex\btexfmts >makefmt 386 plain US >makefmt -- Version 1.0c -- Copyright (c) 1995-1997 by Eberhard Mattes >This is emTeX (tex386), Version 3.14159 [4b] (INITEX) >**plain.ini \dump >(plain.ini (/emtex/texinput/etc/plain.tex Preloading the plain format: >codes, >registers, parameters, fonts, >! Font \tenrm=cmr10 not loadable: Metric (TFM) file not found. > > \font >l.396 \font > \preloaded=cmr9 >? > > > > > > From install.eng: To use TeX, unpack tex4b.zip. tex386 and htex386 require emxrsx.zip, see above. In addition to TeX, you need font metric files (TFM files) which are contained in fontcm.zip. hth Pete **= Email 3 ==========================** Date: Tue, 27 Apr 2004 15:57:50 +0100 From: John Poltorak Subject: Re: eval On Tue, Apr 27, 2004 at 11:29:01AM +0200, Stefan.Neis at t-online.de wrote: > John Poltorak schrieb: > > > If anyone is familiar with the use of eval in shell > > scripts, could you > > explain what is meant by eval F$i="missing" here :- > > > > > > > > for i in more less cmp cat gawk > > do > > eval F$i="missing" > > It's initializing the variables Fmore, Fless, > Fcmp, Fcat, Fgawk with "missing". > > > for j in $DEFPATH > > do > > if test -f $j/$i > > then > > eval F$i=$j/$i > > ... and here it's setting F{programname} to > the correct path. I guess I would be able to follow that if I could understand how $DEFPATH get assigned here:- PREPATH=/bin:/usr/bin:/usr/ucb:/usr/local/bin:$PATH IFS0="$IFS" IFS=":$IFS" for i in $PREPATH do case $i in /*) DEFPATH="$DEFPATH $i" ;; esac done .... but I just can't work out how case works here - I can't $DEFPATH getting any value assigned to it. > Regards, > Stefan -- John **= Email 4 ==========================** Date: Tue, 27 Apr 2004 17:19:33 +0200 (CEST) From: "Sebastian Wittmeier" Subject: Re: eval On Tue, 27 Apr 2004 15:57:50 +0100, John Poltorak wrote: >I guess I would be able to follow that if I could understand how $DEFPATH >get assigned here:- > > >PREPATH=/bin:/usr/bin:/usr/ucb:/usr/local/bin:$PATH >IFS0="$IFS" >IFS=":$IFS" >for i in $PREPATH >do > case $i in > /*) > DEFPATH="$DEFPATH $i" > ;; > esac >done > >... but I just can't work out how case works here - I can't $DEFPATH >getting any value assigned to it. Can it be that each OS/2 path begins with drive names, and those are not recognized by "/*"? Or is the problem that PATH uses backslashes? Sebastian **= Email 5 ==========================** Date: Tue, 27 Apr 2004 16:34:38 +0100 From: John Poltorak Subject: Re: eval On Tue, Apr 27, 2004 at 05:19:33PM +0200, Sebastian Wittmeier wrote: > On Tue, 27 Apr 2004 15:57:50 +0100, John Poltorak wrote: > > >I guess I would be able to follow that if I could understand how $DEFPATH > >get assigned here:- > > > > > >PREPATH=/bin:/usr/bin:/usr/ucb:/usr/local/bin:$PATH > >IFS0="$IFS" > >IFS=":$IFS" > >for i in $PREPATH > >do > > case $i in > > /*) > > DEFPATH="$DEFPATH $i" > > ;; > > esac > >done > > > >... but I just can't work out how case works here - I can't $DEFPATH > >getting any value assigned to it. > > Can it be that each OS/2 path begins with drive names, and those are > not recognized by "/*"? That must be the problem - I changed the defined PATH by removing all references to drive letters and now DEFPATH does get a value. What does '/*)' actually signify and what should it be changed to so that drive letters in the path can be accomodated? > Or is the problem that PATH uses backslashes? '\' in PATH get converted to '/' by the time this script runs. > Sebastian -- John **= Email 6 ==========================** Date: Tue, 27 Apr 2004 12:07:59 -0400 (EDT) From: Thomas Dickey Subject: Re: AM_GNU_GETTEXT not found in library On Tue, 27 Apr 2004, John Poltorak wrote: > On Tue, Apr 27, 2004 at 07:57:46AM -0400, Thomas Dickey wrote: > > On Tue, 27 Apr 2004, John Poltorak wrote: > > > > > On Tue, Apr 27, 2004 at 11:44:08AM +0100, John Poltorak wrote: > > > > > > > The configure.ac file contains:- > > > > > > > > AM_GNU_GETTEXT > > > > "AM" is automake. It includes a number of macros that belong in autoconf. > > How do any of the auto* tools establish a search path fot their macros? Generally that's decided at configure/install time. The last time I was looking at how newer autoconf handles includes, I did notice an include-option but it was broken - I don't recall the details (was comparing successive autoconf releases), but essentially there was an include-path supported briefly, then discarded (partly removed) and leaving only some debris in the source code. Probably some people use it though. The so-called documentation on this is worthless (you're better off reading the source code). > And are those macros added to by other applications? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 7 ==========================** Date: Tue, 27 Apr 2004 17:03:57 +0100 From: John Poltorak Subject: Re: Installing emTeX On Tue, Apr 27, 2004 at 03:37:22PM +0100, Pete Milne wrote: > John Poltorak wrote: > > >This doesn't work, BTW. It ends with some indecipherable error msg here:- > > > >setlocal > >cd \emtex\btexfmts > >makefmt 386 plain US > >makefmt -- Version 1.0c -- Copyright (c) 1995-1997 by Eberhard Mattes > >This is emTeX (tex386), Version 3.14159 [4b] (INITEX) > >**plain.ini \dump > >(plain.ini (/emtex/texinput/etc/plain.tex Preloading the plain format: > >codes, > >registers, parameters, fonts, > >! Font \tenrm=cmr10 not loadable: Metric (TFM) file not found. > > > > \font > >l.396 \font > > \preloaded=cmr9 > >? > > > > > > > > > > > > > From install.eng: > > To use TeX, unpack tex4b.zip. tex386 and htex386 require emxrsx.zip, > see above. In addition to TeX, you need font metric files (TFM files) > which are contained in fontcm.zip. Thanks for that - I obviously didn't understand it correctly. Moving the extraction of fontcm.zip to an earlier step, along with the addition of 'call' where I found I was running a cmd file has got this working, although a couple of manual interventions are still required... I need to press ENTER at this point:- makefmt -- Version 1.0c -- Copyright (c) 1995-1997 by Eberhard Mattes This is emTeX (tex386), Version 3.14159 [4b] (INITEX) **latex.ini \dump (latex.ini (/emtex/texinput/latex2e/latex.ltx (/emtex/texinput/latex2e/texsys.cfg) ../texsys.aux found \ at currdir set to: ./. Assuming \openin and \input have the same search path. Defining UNIX/DOS style filename parser. catcodes, registers, compatibility for TeX 2, parameters, !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! You are attempting to make a LaTeX format from a source file ! That is more than one year old. ! ! If you enter to scroll past this message then the format ! will be built, but please consider obtaining newer source files ! before continuing to build LaTeX. ! ! LaTeX is re-issued every 6 months, in June and December. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! LaTeX source files more than 1 year old!. l.573 ...urce files more than 1 year old!} ? Is there any way around this? I also need to confirm unzip processing a number of times:- Archive: fontltx.zip *********************************************** * emTeX distribution of 25-Jun-95 * *********************************************** * IMPORTANT: Read README.ENG and INSTALL.ENG! * * If you need help, read HELP.ENG * *********************************************** replace /emtex/remove/fontltx.rem? [y]es, [n]o, [A]ll, [N]one, [r]ename: inflating: /emtex/remove/fontltx.rem I guess I must be extracting the same archive twice... There are also a couple of errors involved when running 'latex2e tools.ini' which I need to figure out:- \font\OMS/cmsy/m/n/10=cmsy10 3633 words of font info for 14 preloaded fonts 14 hyphenation exceptions Hyphenation trie of length 6075 has 181 ops out of 750 181 for language 0 No pages of output. Transcript written on latex.log. Cannot find transcript file latex.log SYS0002: The system cannot find the file specified. SYS0002: The system cannot find the file specified. SYS0002: The system cannot find the file specified. SYS0003: The system cannot find the path specified. SYS1041: The name latex2e is not recognized as an internal or external command, operable program or batch file. *.tex SYS0002: The system cannot find the file specified. 0 file(s) copied. *.sty SYS0002: The system cannot find the file specified. 0 file(s) copied. So it looks as though it is largely installed. How do I go about formatting testpage.tex to ensure it works? > hth > > Pete > -- John **= Email 8 ==========================** Date: Tue, 27 Apr 2004 18:10:19 +0200 (CEST) From: Stefan.Neis at t-online.de Subject: Re: eval John Poltorak schrieb: > What does '/*)' actually signify and what "/*" signifies any string starting with "/". "*" and "?" are used just like wildcards in filenames. ")" is part of the case syntax. should it be > changed to so that > drive letters in the path can be accomodated? Maybe something like /* | ?:/* Stefan **= Email 9 ==========================** Date: Tue, 27 Apr 2004 20:48:51 +0200 From: Andreas Buening Subject: Re: AM_GNU_GETTEXT not found in library John Poltorak wrote: > > On Tue, Apr 27, 2004 at 07:57:46AM -0400, Thomas Dickey wrote: > > On Tue, 27 Apr 2004, John Poltorak wrote: > > > > AM_GNU_GETTEXT It's a set of .m4 files that is installed by _gettext_ into prefix/share/aclocal/ For a selfconsisting source package these files should be somewhere in the source package. They can (could) be installed by the autopoint script. > > "AM" is automake. It includes a number of macros that belong in autoconf. > > How do any of the auto* tools establish a search path fot their macros? > > And are those macros added to by other applications? Default search path is prefix/share/aclocal-x.y and prefix/share/aclocal where x.y is the version of your automake. Bye, Andreas **= Email 10 ==========================** Date: Tue, 27 Apr 2004 20:49:06 +0200 From: Andreas Buening Subject: Re: Makefile.am for PATCH John Poltorak wrote: > > I'm attempting to retrofit a Makefile.am into PATCH as I think it would be > easier to maintain than patching Makefile.in. Since I don't anything about > putting together a Makefile.am from scratch, this could take some time... > > AIUI the first two things you need in the file are:- > > bin_PROGRAMS = foo > foo_SOURCES = foo.c foo.h xxx.c yyy.c zzz.c > > For PATCH, I guess the first line should be:- > > bin_PROGRAMS = patch > > but I'm not sure about the second... Looking through Makefile.in, these > variable are set up:- [snip] This looks like a system-dependent source file selection procedure. Not that easy to implement. And, don't forget to set a link to every file in Makefile.am so that "make dist" will store all source and text files. > so I'm tempted to add $SRCS and $HDRS to patch_sources. Sounds reasonably. > If anyone follows any of this, please feel free to jump in any time and > point out the error of my ways. Bye, Andreas **= Email 11 ==========================** Date: Tue, 27 Apr 2004 20:49:21 +0200 From: Andreas Buening Subject: Re: TeX John Poltorak wrote: > Are you familiar with emTeX? I've dabbled a few times but haven't really > known what I was doing with it. > > I get the feeling that TeX normally comes as a standard package on most > Unix distros so it might be an idea to put together a TeX package for > UnixOS/2... If you want to keep a TeX distribution up to date, that's a full time job. We're talking of hundreds of packages you have to install, not just a few dozens. Bye, Andreas **= Email 12 ==========================** Date: Tue, 27 Apr 2004 20:48:57 +0200 From: Andreas Buening Subject: Re: The system cannot find the command process in the path John Poltorak wrote: > > Here's another one for the FAQ:- > > The system cannot find the command process in the path. > > This sometimes arises when MAKESHELL is not set prior to running Make. > If it does occur set MAKESHELL=/bin/sh. Should be fixed in the latest make version. Bye, Andreas **= Email 13 ==========================** Date: Tue, 27 Apr 2004 20:49:16 +0200 From: Andreas Buening Subject: Re: eval Stefan.Neis at t-online.de wrote: > > John Poltorak schrieb: > Maybe something like /* | ?:/* Maybe /* | \* | [A-Za-z]:/* | [A-Za-z]:\* and IFS=";$IFS" (';' instead of ':') Bye, Andreas **= Email 14 ==========================** Date: Tue, 27 Apr 2004 20:49:29 +0200 From: Andreas Buening Subject: Re: DLL for GNU text utils John Poltorak wrote: > > Whilst building the GNU text utils a static lib libtu.a is built. > > How would I go about creating a DLL instead? Would this require libtool? Yes. Bye, Andreas **= Email 15 ==========================** Date: Tue, 27 Apr 2004 23:01:28 +0200 From: Michael Zolk Subject: Re: Bug report: INSTALLPKG.CMD On Fri, Apr 23, 2004 at 03:14:44PM -0500, Anton Monroe wrote: > Somewhere around line 298 of installpkg.cmd, depending on the version, there is: > if simul="no" then call UX2Mknod(unixroot"\"devname,type,major,minor) > I think it should be: > if simul="no" then call UX2Mknod unixroot"\"devname,type,major,minor You're right. I have changed it and will upload the updated version. Thanks Michael -- **= Email 16 ==========================** Date: Tue, 27 Apr 2004 21:51:04 +0200 From: Andreas Buening Subject: Re: _lstat 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?): 1) CPPFLAGS="-Dlstat" 2) Somewhere in the source #define lstat stat 3) configure.ac: AC_CHECK_FUNC([lstat], , [AC_DEFINE([lstat], [stat], [Define to 'stat' if you do not have the 'lstat' function.]) ] ) From my point of view it's much more preferable to leave source code > > >alone if possible and am pleased that just running autoheader does the > > >trick, automagically, in this case. > > > > > There must be code in there to handle systems without lstat. INteresting that you have to rerun autoheader for it to work. > > As I say, it works auto*magically*. Don't ask me how. > > Also it doesn't appear to work in recent Autoconfs. I used v2.50-r5 for OS/2. > > > Where is the MKTEMP archive available? Bye, Andreas **= Email 17 ==========================** Date: Tue, 27 Apr 2004 15:20:58 -0400 (EDT) From: Thomas Dickey Subject: Re: AM_GNU_GETTEXT not found in library On Tue, 27 Apr 2004, Andreas Buening wrote: > John Poltorak wrote: > > > > On Tue, Apr 27, 2004 at 07:57:46AM -0400, Thomas Dickey wrote: > > > On Tue, 27 Apr 2004, John Poltorak wrote: > > > > > > AM_GNU_GETTEXT > > It's a set of .m4 files that is installed by _gettext_ into > prefix/share/aclocal/ hmm - a grep through various versions of automake mentions it in the documentation, but I don't see it installed by any of those versions. The aclocal directory is a feature of automake. But the comment about "AM" is correct: for several years there were people contributing code to automake that should have been incorporated into autoconf. (I probably should have recalled this particular case since I've a fixed-up version in lynx). This particular macro (reading it now) doesn't belong in automake. > For a selfconsisting source package these files should be > somewhere in the source package. They can (could) be installed > by the autopoint script. > > > > > "AM" is automake. It includes a number of macros that belong in autoconf. > > > > How do any of the auto* tools establish a search path fot their macros? > > > > And are those macros added to by other applications? > > Default search path is > prefix/share/aclocal-x.y > and > prefix/share/aclocal > where x.y is the version of your automake. configure/install, as noted. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 18 ==========================** Date: Wed, 28 Apr 2004 08:56:20 +1000 From: arnstein.prytz at jcu.edu.au Subject: Re: TeX Andreas Buening wrote: > If you want to keep a TeX distribution up to date, that's a full > time job. We're talking of hundreds of packages you have to install, > not just a few dozens. Yes, and No. The basic TeX/MetaFont distribution comes with a set of base packages that are always needed. This is a very small set that is easily kept up to date. When you use additional packages, of which you are unlikely to be using more than a few dozen routinely, then you have to keep each one up to date from the ctan archive yourself. However, this is rarely needed unless there is a bug/feature that is a show stopper. If the version you have works satisfactorally just leave it alone. Personally, I keep an eye for updates to packages I use about every year or so (I've been using TeX/LaTeX since 1980). So, John, it make little difference whether you use emTeX or the TDS version or vTeX. I use all three. You'll likely have distribution issues with vTeX but emTeX and emTeXTDS are now obsolete. Not that it matters because they both work very well. I'd pick emTeXTDS. Ok. Let me ask this again. Does anyone have a working up to date emacs that is in a distributable form? I'm probably dense as a brown dwarf, but I have been singularly unsuccessful following the instructions to compile 20.7. Regards, Arnstein ---------------------------------------------------------------------------- Arnstein Prytz Arnstein.Prytz at jcu.edu.au School of Maths and Physics ph: 61-7-47815183 James Cook University fax: 61-7-47815880 Townsville, Queensland 4811, Australia ---------------------------------------------------------------------------- **= Email 19 ==========================** Date: Wed, 28 Apr 2004 09:57:19 +0100 From: John Poltorak Subject: Re: Installing emTeX After considerable testing I've managed to create a cmd file to install emTeX from the archives but have had a bit of difficulty getting it to carry on when using some included batch files because they would not return to the directory they were called from. Even the use of setlocal and endlocal did not corret matters, so I had to include a couple of instances of having to CD back to the source directory to carry on the install, and these have had to be hard coded. I'd appreciate it if someone could suggest a better method. Here is the fist part of the install script which assumes all the required archived files are in the current directory which is \in\tex\os2\emtex:- set path=\emtex\bin;%path% set emtexdir=\emtex rem ------------------------------------------ rem FIRST rem ------------------------------------------ unzip first -d / rem ------------------------------------------ rem TeX Compiler rem ------------------------------------------ unzip tex4b -d / unzip l2input -d / unzip latex209 -d / unzip fontltx -d / unzip fontcm -d / cd \emtex\btexfmts call makefmt 386 plain US cd \emtex\btexfmts call makefmt 386 latex2e US 8bit -b \emtex\bin\latex2e rem ********************** need to restore directory here ************** cd \in\tex\os2\emtex rem ********************** need to restore directory here ************** unzip l2tools -d / cd \emtex\dist\latex\packages\tools call latex2e tools.ins cd \emtex\dist\latex\packages\tools copy *.tex \emtex\texinput\latex2e copy *.sty \emtex\texinput\latex2e rem ********************** need to restore directory here ************** cd \in\tex\os2\emtex rem ********************** need to restore directory here ************** unzip texware -d / rem ------------------------------------------ -- John **= Email 20 ==========================** Date: Wed, 28 Apr 2004 10:05:21 +0100 From: John Poltorak Subject: Re: TeX On Wed, Apr 28, 2004 at 08:56:20AM +1000, arnstein.prytz at jcu.edu.au wrote: > Personally, I keep an eye for updates > to packages I use about every year or so (I've been using TeX/LaTeX since > 1980). I guess that must qualify you as our resident TeXpert ;-)... > So, John, it make little difference whether you use emTeX or the TDS version > or vTeX. I use all three. You'll likely have distribution issues with vTeX > but emTeX and emTeXTDS are now obsolete. Not that it matters because they > both work very well. I'd pick emTeXTDS. I'll probably go with that. I wonder if EM has ever released the source for emTeX... > Ok. Let me ask this again. Does anyone have a working up to date emacs > that is in a distributable form? I'm probably dense as a brown dwarf, but > I have been singularly unsuccessful following the instructions to compile > 20.7. I did have some instructions to compile 20.7 and managed to get it to build, but it did involve quite a bit of manual intervention, with lots of potential for errors. I'll see if I can find any way to fully automate it but I don't expect to create it in a distributable format, although you can have a script for building it, if I can manage to ome up with one. > Regards, Arnstein > ---------------------------------------------------------------------------- > Arnstein Prytz Arnstein.Prytz at jcu.edu.au > School of Maths and Physics ph: 61-7-47815183 > James Cook University fax: 61-7-47815880 > Townsville, Queensland 4811, Australia > ---------------------------------------------------------------------------- > -- John **= Email 21 ==========================** Date: Wed, 28 Apr 2004 10:11:57 +0100 From: John Poltorak Subject: Re: DLL for GNU text utils On Tue, Apr 27, 2004 at 08:49:29PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > > Whilst building the GNU text utils a static lib libtu.a is built. > > > > How would I go about creating a DLL instead? Would this require libtool? > > Yes. 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? > Bye, > Andreas -- John **= Email 22 ==========================** Date: Wed, 28 Apr 2004 11:27:40 +0200 (CEST) From: Stefan.Neis at t-online.de Subject: Re: Emacs arnstein.prytz at jcu.edu.au schrieb: > Ok. Let me ask this again. Does anyone have a working > up to date emacs > that is in a distributable form? I'm probably dense as a > brown dwarf, but > I have been singularly unsuccessful following the > instructions to compile > 20.7. Personally, I'm using 20.6 on one (test) box, but I keep having problems (hexl-mode crashes it rather easily plus various more mysterious crashes), so I'm mostly using 19.33 for real work. Regards, Stefan **= Email 23 ==========================** Date: Wed, 28 Apr 2004 11:29:21 +0200 (CEST) From: Stefan.Neis at t-online.de Subject: Re: TeX John Poltorak schrieb: > I'll probably go with that. I wonder if EM has ever > released the source > for emTeX... No. Stefan **= Email 24 ==========================** Date: Wed, 28 Apr 2004 11:35:21 +0200 (CEST) From: Stefan.Neis at t-online.de Subject: Re: Installing emTeX John Poltorak schrieb: > they would not > return to the directory they were called from. Even the > use of setlocal and > endlocal did not corret matters, so I had to include a > couple of instances > of having to CD back to the source directory to carry on > the install, Using a sub-Prozess executed by a separate cmd could help > call makefmt 386 latex2e US 8bit -b \emtex\bin\latex2e > rem ********************** need to restore directory here > ************** > cd \in\tex\os2\emtex i.e. something like cmd /c "makefmt 386 latex2e US 8bit -b \emtex\bin\latex2e" Regards, Stefan