From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 22 Feb 2002 04:16:18 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 143 ************************************************** Thursday 21 February 2002 Number 143 ************************************************** Subjects for today 1 Re: make 3.79.1 : Andreas Buening 2 Re: UnixOS/2 distro : Marty" 3 Re: UnixOS/2 distro : Thomas Dickey 4 Re: EMACS build error : Holger Veit 5 Re: UnixOS/2 distro : John Poltorak 6 Re: Has anyone ported nmap? : Adrian Gschwend" 7 Re: make 3.79.1 : John Poltorak 8 Re: (un)protoize : John Poltorak 9 db.a : John Poltorak 10 Re: db.a : Lyn St George" 11 Re: Identifying sh.exe : Thomas E. Dickey" 12 Emacs customisation : John Poltorak 13 Re: Re: Emacs customisation : John Poltorak 14 Identifying sh.exe : John Poltorak 15 GNAT 3.14p : John Poltorak 16 Re: GNAT 3.14p : Vincent Marciante 17 Re: Identifying sh.exe : Thomas Dickey 18 Re: make 3.79.1 : Andreas Buening 19 Re: EMACS build error : Andreas Buening 20 Re: make 3.79.1 : John Poltorak 21 Re: Emacs customisation : Masaru Nomiya 22 Re: make 3.79.1 : Andreas Buening **= Email 1 ==========================** Date: Fri, 22 Feb 2002 00:22:27 +0100 From: Andreas Buening Subject: Re: make 3.79.1 John Poltorak wrote: > > On Wed, Feb 20, 2002 at 07:35:21PM +0100, Andreas Buening wrote: > > > Should be fixed now: > > ftp://ftp.unixos2.com/incoming/make-3_79_1-bin-beta2.zip > > Can anyone get this to work with the Makefile in? :- > > emx\bsd\libc Should be fixed now: ftp://ftp.unixos2.com/incoming/make-3_79_1-bin-beta3.zip 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 Redmond where the Shadows lie. **= Email 2 ==========================** Date: Fri, 22 Feb 2002 02:07:37 -0500 (EST) From: "Marty" Subject: Re: UnixOS/2 distro On Thu, 21 Feb 2002 17:12:05 +0000, John Poltorak wrote: > > Here is a list of the most recent versions of many of the important apps > in Slackware. Some of these are not in the latest Slackware distro yet. It > would be nice to get as many of these into UnixOS/2 as possible. In fact, > most of these apps are already available on OS/2, although a few are just > slightly back levelled, so we are not far off having a credible distro... > > > > gawk: ftp://ftp.gnu.org/pub/gnu/gawk/gawk-3.1.0.tar.gz > grep: ftp://ftp.gnu.org/pub/gnu/grep/grep-2.4.2.tar.gz > sed: ftp://ftp.gnu.org/pub/gnu/sed/sed-3.02.tar.gz > patch: ftp://ftp.gnu.org/pub/gnu/patch/patch-2.5.4.tar.gz > m4: ftp://ftp.gnu.org/pub/gnu/m4/m4-1.4.tar.gz > gmake: ftp://ftp.gnu.org/pub/gnu/make/make-3.79.1.tar.gz > gettext: ftp://ftp.gnu.org/pub/gnu/gettext/gettext-0.11.tar.gz > fileutls: ftp://ftp.gnu.org/pub/gnu/fileutils/fileutils-4.1.tar.gz > find: ftp://ftp.gnu.org/pub/gnu/findutils/findutils-4.1.tar.gz > sh_utils: ftp://ftp.gnu.org/pub/gnu/sh-utils/sh-utils-2.0.tar.gz > txtutils: ftp://ftp.gnu.org/pub/gnu/textutils/textutils-2.0.tar.gz > autoconf: ftp://alpha.gnu.org/pub/gnu/autoconf/autoconf-2.52h.tar.gz > automake: ftp://ftp.gnu.org/pub/gnu/automake/automake-1.5.tar.gz > cpio: ftp://ftp.gnu.org/pub/gnu/cpio/cpio-2.4.2.tar.gz > diff: ftp://ftp.gnu.org/pub/gnu/diffutils/diffutils-2.7.tar.gz > bison: ftp://ftp.gnu.org/pub/gnu/bison/bison-1.33.tar.gz > bash: ftp://ftp.gnu.org/pub/gnu/bash/bash-2.05a.tar.gz > bash1: ftp://ftp.gnu.org/pub/gnu/bash/bash-1.14.7.tar.gz > tcsh: ftp://ftp.astron.com/pub/tcsh/tcsh-6.11.tar.gz > gzip: ftp://gatekeeper.dec.com/pub/GNU/gzip/gzip-1.2.4.tar.gz > bzip2: ftp://sources.redhat.com/pub/bzip2/v102/bzip2-1.0.2.tar.gz > less: http://www.greenwoodsoftware.com/less/less-374.tar.gz > binutils: ftp://ftp.gnu.org/pub/gnu/binutils/binutils-2.11.2.tar.gz > gcc: ftp://ftp.gnu.org/pub/gnu/gcc/gcc-3.0.3/gcc-3.0.3.tar.gz > gcc_g77: ftp://ftp.gnu.org/pub/gnu/gcc/gcc-3.0.3/gcc-g77-3.0.3.tar.gz > gcc_objc: ftp://ftp.gnu.org/pub/gnu/gcc/gcc-3.0.3/gcc-objc-3.0.3.tar.gz > perl: http://www.cpan.org/src/stable.tar.gz > python: ftp://ftp.python.org/pub/python/2.2/Python-2.2.tgz > flex: ftp://ftp.gnu.org/pub/gnu/non-gnu/flex/flex-2.5.4a.tar.gz > ncurses: ftp://invisible-island.net/ncurses/ncurses-5.2.tar.gz > slang: ftp://space.mit.edu/pub/davis/slang/v1.4/slang-1.4.5.tar.gz > apache: http://www.apache.org/dist/httpd/apache_1.3.22.tar.gz > lynx: ftp://lynx.isc.org/lynx/lynx2.8.4/lynx2-8-4.tar.gz > openssl: http://www.openssl.org/source/openssl-engine-0.9.6b.tar.gz > tin: ftp://ftp.tin.org/pub/news/clients/tin/unstable/tin-1.5.11.tar.gz > bind: ftp://ftp.isc.org/isc/bind/src/8.3.1/bind-src.tar.gz > ftchmail: http://www.tuxedo.org/~esr/fetchmail/fetchmail-5.9.8.tar.gz > wget: ftp://ftp.gnu.org/pub/gnu/wget/wget-1.8.1.tar.gz > man: ftp://ftp.win.tue.nl/pub/linux-local/utils/man/man-1.5j.tar.gz > groff: ftp://ftp.ffii.org/pub/groff/groff-1.17.2.tar.gz > texinfo: ftp://ftp.gnu.org/pub/gnu/texinfo/texinfo-4.0.tar.gz > manpages: ftp://ftp.win.tue.nl/pub/linux-local/manpages/man-pages-1.47.tar.gz > rcs: http://www.cs.purdue.edu/homes/trinkle/RCS/rcs-5.7.tar.Z > sox: http://prdownloads.sourceforge.net/sox/sox-12.17.3.tar.gz > a2ps: ftp://ftp.enst.fr/pub/unix/a2ps/a2ps-4.13b.tar.gz > zlib: ftp://ftp.info-zip.org/pub/infozip/zlib/zlib-1.1.3.tar.gz > zip: ftp://ftp.info-zip.org/pub/infozip/src/zip23.tar.gz > unzip: ftp://ftp.info-zip.org/pub/infozip/src/unzip542.tar.gz > jed: ftp://space.mit.edu/pub/davis/jed/v0.99/jed-B0.99-15.tar.gz > oggutils: http://www.vorbis.com/files/rc3/unix/vorbis-tools-1.0rc3.tar.gz > bitchx: ftp://ftp.bitchx.org/pub/BitchX/source/ircii-pana-1.0c18.tar.gz > vim: ftp://ftp.vim.org/pub/vim/unix/vim-6.0.tar.bz2 > elvis: ftp://ftp.fh-wedel.de/pub/fh-wedel/staff/herbert/elvis/elvis-2.2g-os2.tar.gz > emacleim: ftp://ftp.gnu.org/pub/gnu/emacs/leim-21.1.tar.gz > emacsbin: ftp://ftp.gnu.org/pub/gnu/emacs/emacs-21.1.tar.gz > ghostscr: http://prdownloads.sourceforge.net/ghostscript/ghostscript-7.04.tar.gz > mysql: http://www.mysql.com/Downloads/MySQL-3.23/mysql-3.23.49.tar.gz > readline: ftp://ftp.gnu.org/pub/gnu/readline/readline-4.2a.tar.gz > pine: ftp://ftp.cac.washington.edu/pine/pine.tar.Z > cvs: ftp://ftp.cvshome.org/pub/cvs-1.11.1/cvs-1.11.1p1.tar.gz > > What have I missed (apart from XFree86 and X apps) ? Don't forget Joe's Own Editor (JOE). Personal favorite of mine that has been with the early days of Slackware and most Linux distros. Entirely remappable key bindings, help system, shell/pipe mode, multi-document, macro recording/playback, able to read >1GB files without choking, incremental forward and backward search, and loads of other cool features in a small disk and memory footprint. It's been ported to every platform known to man, but the only existing OS/2 version I was able to find is a 16-bit port that can't handle large files. Also is there a Lex and Yacc on your list? These are needed in any standard distro, as they're used by many configure scripts as well as development. **= Email 3 ==========================** Date: Fri, 22 Feb 2002 06:50:45 -0500 From: Thomas Dickey Subject: Re: UnixOS/2 distro On Fri, Feb 22, 2002 at 09:13:13AM +0000, John Poltorak wrote: > > ftp://unixos2.com/pub/unixos2/unixos2-current/unixos2/d1/byacc.zip > > it's just that I don't have a definitive location as the home of BYACC. I'll make a small webpage for the copy of byacc that I use (am doing so now). http://invisible-island.net/byacc/ ftp://invisible-island.net/byacc/ -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 4 ==========================** Date: Fri, 22 Feb 2002 07:41:44 +0100 From: Holger Veit Subject: Re: EMACS build error On Thu, Feb 21, 2002 at 11:14:01PM +0100, Andreas Buening wrote: [...] > > > If a program requires that link() must succeed then it's broken. > > > In general the only file system that supports hard links is /tmp > > > on Unix systems (to my knowledge). symlink() might be another story. > > > > You are wrong. Any Unix file system supports hard links, and has done > > so for decades. The thing that makes link() unattractive compared to > > symlink(), though, is that symlink can span over several mounted file > > systems, whereas a link is (due to its mechanism - is is basically > > an alias to an inode) restricted to the filesystem where the original > > file is located. The latter is not much a problem, because nowadays > > we have large disks, so splitting into /var, /usr, /opt, /home > > filesystems is often no longer done (except on larger servers for > > good reasons). > > Okay, to be more precise: At work I cannot do the following > in my home directory (it works only in /tmp): > > touch file1 > md subdir > ln file1 subdir/file2 > > Hard links are only possible _within_ the same directory and No. This is definitely wrong. That you have the impression is just that your home directory where you have write access to is AFS (and the other writeable directory is /tmp. Check other (real UNIX) filesystems on that host with ls -l and look at the link count (this is the number after the access rights): if it is > 1 then you have hard links in progress. > therefore quite useless, I've been told that this is an AFS > feature, so better every serious Unix software should be This is not a feature, it is a broken file system: AFS emulates hardlinks by hidden files, and the programmers were just lazy. > able to handle a failing link() without a core dump. Who has talked about a core dump? The result of a failing link() is typically that temporary garbage file won't get cleaned up. Some call this just annoying; I call it broken design of the underlying file system. > > > # ifndef symlink /* for the case config.h already handles chown() */ > > > inline int symlink(x,y,z) { /* copy the file? */ } > > > # endif > > > > Separation between *SUCCESS and *FAILURE is too complicated, IMHO, because > > you would sometimes need both: let fchown succeed and symlink fail, for > > instance. You'll encounter a clash if both #ifdefs check for > > #ifndef fchown. You also need some configuration file > > that will disable the replacement code by #define fchown if you have > > a real version. *Sometimes* (namely in the autoconf case), you have a > > config.h file which usually declares #define HAS_FCHOWN or similar; > > so it is a better idea to use these as switcher symbols. > > If config.h handles a missing lchown() it often uses stuff like > #define lchown repl_lchown ... if the programmer took care at all. I have seen numerous autoconf'd source packages where the generated config.h was just lying around, or was included in each source file, but never ever any HAS_XXX definition was evaluated at all. After all, the code worked fine under Linux... > which would be handled by "#ifndef lchown" in the code above, > but in general you're right. I do not say that there could be > a all in one solution of this problem. I only say that there > are packages that could benefit from such a treatment > (maybe less than 50%, I don't know). There is one more problem with that solution, not a technical one, but a psychological one: You proposed to add this into the EMX header logic. I have suggested more than once to modify EMX (even just for the simple purpose of exporting the prominent strcasecmp()) - never happened. Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 5 ==========================** Date: Fri, 22 Feb 2002 09:13:13 +0000 From: John Poltorak Subject: Re: UnixOS/2 distro On Fri, Feb 22, 2002 at 02:07:37AM -0500, Marty wrote: > On Thu, 21 Feb 2002 17:12:05 +0000, John Poltorak wrote: > > > > > Here is a list of the most recent versions of many of the important apps > > in Slackware. Some of these are not in the latest Slackware distro yet. It > > would be nice to get as many of these into UnixOS/2 as possible. In fact, > > most of these apps are already available on OS/2, although a few are just > > slightly back levelled, so we are not far off having a credible distro... > > flex: ftp://ftp.gnu.org/pub/gnu/non-gnu/flex/flex-2.5.4a.tar.gz > > What have I missed (apart from XFree86 and X apps) ? > > Don't forget Joe's Own Editor (JOE). Personal favorite of mine that has been with > the early days of Slackware and most Linux distros. Entirely remappable key > bindings, help system, shell/pipe mode, multi-document, macro recording/playback, > able to read >1GB files without choking, incremental forward and backward search, > and loads of other cool features in a small disk and memory footprint. It's been > ported to every platform known to man, but the only existing OS/2 version I was able > to find is a 16-bit port that can't handle large files. I'd like to include JOE, but I couldn't find anything for OS/2 apart from the ancient release you mention. However the most recent source is available here:- http://prdownloads.sourceforge.net/joe-editor/joe-2.9.8-pre1.tgz I tried building it but ws not successful. Maybe someone else may have more luck... If anyone is interested, there is also a JOE mailing list available:- https://lists.sourceforge.net/lists/listinfo/joe-editor-general > Also is there a Lex and Yacc on your list? These are needed in any standard distro, > as they're used by many configure scripts as well as development. I thought FLEX, which is included in the list, was the usual 'Lex' program on Unix - see above. BYACC is included in UnixOS/2 here:- ftp://unixos2.com/pub/unixos2/unixos2-current/unixos2/d1/byacc.zip it's just that I don't have a definitive location as the home of BYACC. -- John **= Email 6 ==========================** Date: Fri, 22 Feb 2002 09:19:52 +0100 (CET) From: "Adrian Gschwend" Subject: Re: Has anyone ported nmap? On Thu, 21 Feb 2002 10:29:54 -0600, email at eracc.hypermart.net wrote: Hi Gene, >I *have* to ask ... have you got it yet? I've been holding on to your >message to remember to check for 'nmap' and, like a kid anticipating >Christmas, I am "dying" for it to get here. :-) yeah I'm waiting too :-) Brian was very busy the past days because he was hunting a bug which was rather difficult to solve as it looks like :-) I will ask him again and let you know cu Adrian -- Adrian Gschwend at OS/2 Netlabs ICQ: 22419590 ktk at netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org **= Email 7 ==========================** Date: Fri, 22 Feb 2002 09:20:40 +0000 From: John Poltorak Subject: Re: make 3.79.1 On Fri, Feb 22, 2002 at 12:22:27AM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > > Can anyone get this to work with the Makefile in? :- > > > > emx\bsd\libc > > Should be fixed now: > ftp://ftp.unixos2.com/incoming/make-3_79_1-bin-beta3.zip Yup. I can also use it to build emacs, which I couldn't before, although it does trip up here:- emximp -o os2/tcp.a os2/tcp.imp gcc -Zexe -DOS2 -O -Zmts tcp.c os2/tcp.a -Ios2 -o tcp gcc -Zexe -DOS2 -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O os2/bdf2mfn.c -lc -o bdf2mfn rc -r -x2 os2/pmcolors.rc IBM RC (Resource Compiler) Version 5.00.006 Oct 20 2000 Copyright (C) IBM Corp. 2000. - Licensed Materials - Program Property of IBM - All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. RC is creating binary resource file os2/pmcolors.res gcc -Zexe -DOS2 -O os2/pmcolors.c os2/pmcolors.def os2/pmcolors.res -o pmcolors gcc -Zexe -DOS2 -O os2/pmsysfont.c -o pmsysfont gcc -Zexe -DOS2 -c -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O -DCONFIG_BROKETS -DINHIBIT_STRING_HEADER ../src/regex.c gcc -Zexe -DOS2 -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O -DVERSION="\"20.7\"" etags.c getopt.o getopt1.o regex.o -lc -o etags etags.c: In function `print_version': etags.c:512: stray '\' in program etags.c:512: stray '\' in program make[1]: *** [etags] Error 1 make[1]: Leaving directory `C:/eval/emacs/emacs-20.7/lib-src' make: *** [lib-src] Error 2 I don't get this error with v3.76.1, so suspect that it is a Make bug. > 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 Redmond where the Shadows lie. -- John **= Email 8 ==========================** Date: Fri, 22 Feb 2002 09:30:45 +0000 From: John Poltorak Subject: Re: (un)protoize On Thu, Feb 21, 2002 at 11:53:23PM +0100, Sebastian Wittmeier (ShadoW) wrote: > On Thu, 21 Feb 2002 20:41:52 +0000, John Poltorak wrote: > > "The program protoize is an optional part of GCC. You can use it to add > prototypes to a program, thus converting the program to ISO C in one > respect. The companion program unprotoize does the reverse: it removes > argument types from any prototypes that are found." > > >gcc v3.0.3 has a couple of programs, protoize and unprotoize, which are > >missing from the OS/2 port. I have no idea what they are but would prefer > >to include them in a GCC package if possible. Does anyone know where I > >coud get them? > > In the original gnu gcc.tar.gz archive? Yes, I can see a protoize.c. I guess unprotoize is simply linked to the same program... Can anyone build an OS/2 version of this program? > Sebastian -- John **= Email 9 ==========================** Date: Fri, 22 Feb 2002 09:39:39 +0000 From: John Poltorak Subject: db.a How does the db.a provided by IZ here:- http://www.math.ohio-state.edu/~ilya/software/os2/db_mt.zip differ from the one included in EMX? Is it just compiled with different *FLAGS? Anyone got a Makefile for it? -- John **= Email 10 ==========================** Date: Fri, 22 Feb 2002 10:02:06 +0000 From: "Lyn St George" Subject: Re: db.a On Fri, 22 Feb 2002 09:39:39 +0000, John Poltorak wrote: > >How does the db.a provided by IZ here:- > >http://www.math.ohio-state.edu/~ilya/software/os2/db_mt.zip > >differ from the one included in EMX? > >Is it just compiled with different *FLAGS? Anyone got a Makefile for it? The 1.85 tarball is still on the Sleepycat site. Regarding 4.0.14 - I've found 2 things: 1. when built with compatibility for 1.85, the Perl install refuses to even recognise it. 2. reading the docs, the API has changed from 3.x to 4.x, and even the latest version of MySQL, 2.23.49, contains only v 3.2.9. Therefore, it seems to me that the usefulness of v4.x becomes rather limited. I'll have another go at 3.2.9 (it objected the last time, so I'll need to be more firm with it .... ) >-- >John > > > Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 11 ==========================** Date: Fri, 22 Feb 2002 10:05:54 -0500 (EST) From: "Thomas E. Dickey" Subject: Re: Identifying sh.exe On Fri, 22 Feb 2002, John Poltorak wrote: > > Is there any way to identify which version of shell is being used from > within a shell script? not easily (many shells do set the $SHELL variable, but that is a convention rather than a standard). -- T.E.Dickey http://invisible-island.net ftp://invisible-island.net **= Email 12 ==========================** Date: Fri, 22 Feb 2002 11:12:03 +0000 From: John Poltorak Subject: Emacs customisation I've managed to get emacs v20.7 built, and I'd like to try and get a little comfortable with it. I've tried various builds in the past, but never managed to feel at home with emacs itself. I have normally used it as a text mode (vio) app in the past and am not sure if this new build lets it work in that mode... One thing I would like to do is change the font - it's a large courier font at the moment, and would much prefer to use a small System Vio font. Is it possible to do that? How do I get it work more like EPM? Is there an available set of startup macros to emulate EPM? -- John **= Email 13 ==========================** Date: Fri, 22 Feb 2002 13:18:50 +0000 From: John Poltorak Subject: Re: Re: Emacs customisation On Fri, Feb 22, 2002 at 09:18:01PM +0900, Masaru Nomiya wrote: > Hello, John. > > How tough you are! :-) I'm only trying to make it easy for other people to enjoy the benefits of some hard work done by a few porters. Would I'd like to have if possible is OS/2 based versions of some emacs packages which appear in Slackware here:- ftp://ftp.mirror.ac.uk/sites/ftp.slackware.com/pub/slackware/slackware/slakware/e1/ consisting of:- elisp: Emacs lisp source files. emac_nox: Emacs binary without X support. emacinfo: Info files for emacs-20.7 emacleim: leim-20.7 (Library of Emacs Input Method) emacmisc: Miscellaneous files for emacs-20.7. emacsbin: GNU Emacs 20.7 > BTW > > [John] == John Poltorak has written: > > John> I've managed to get emacs v20.7 built, and I'd like to try and get a > John> little comfortable with it. I've tried various builds in the past, but > John> never managed to feel at home with emacs itself. > > I'm very glad, and I must tell to Mr. Sasaki, Mr.Nakagawa. It would be good to have the porters on the list. > John> I have normally used it as a text mode (vio) app in the past > John> and am not sure if this new build lets it work in that mode... > > I'm sorry, but I can't understand the meaning of "text mode". Can be run full screen, ie not PM. > John> One thing I would like to do is change the font - it's a large courier > John> font at the moment, and would much prefer to use a small System Vio font. > John> Is it possible to do that? > > Could you show me your .emacs and .XDefaults? It's not very extensive, I'm just starting to collect a few macros. I have not used emacs under XFree so far. (message "processing .emacs") (fset 'save-and-exit "\C-x\C-s\C-x\C-c") (setq default-major-mode 'text-mode) (setq text-mode-hook 'turn-on-auto-fill) (setq visible-bell t) (setq transient-mark-mode t) (global-set-key "\C-o" 'compile) (global-set-key [f3] 'kill-emacs) (global-set-key [f4] 'save-and-exit) (global-set-key [f7] 'compile) (global-set-key [f8] 'call-last-kbd-macro) (global-set-key [f11] 'describe-no-warranty) (global-set-key [f12] 'info) (put 'eval-expression 'disabled nil) > In the Emacs 20.7 for OS/2, you can't use bdf fonts. > That is, you must conver bdf fonts to mfn fonts. > bdff2mfn.exe in the ..emacs-20.7/lib-src is the tool for this. > When you use bdf2mfn.exe, this create FONTSET.OS2 at the same time. > Copy FONTSET.OS2 to your home directory. > Then you'll get multiligual world! This sounds useful. I'm not very familiar with font formats. Is there any info on BDF2MFN ? Where does it need as an input file? > Regards, > > --- > Masaru Nomiya mail-to: nomiya at ttmy.ne.jp > > "No WIndows, no gains!" ..... "Why, I am wrong?" > > -- Bill -- -- John **= Email 14 ==========================** Date: Fri, 22 Feb 2002 14:45:03 +0000 From: John Poltorak Subject: Identifying sh.exe Is there any way to identify which version of shell is being used from within a shell script? -- John **= Email 15 ==========================** Date: Fri, 22 Feb 2002 16:12:28 +0000 From: John Poltorak Subject: GNAT 3.14p Anyone looking at building GNAT 3.14p? Is this one based on gcc 3.0.3? -- John **= Email 16 ==========================** Date: Fri, 22 Feb 2002 19:00:38 -0500 From: Vincent Marciante Subject: Re: GNAT 3.14p John Poltorak wrote: > > Anyone looking at building GNAT 3.14p? Not me, (don't reallty know how) but I would definately use it. > Is this one based on gcc 3.0.3? No, still 2.8... IIRC 3.15p if one is released will also be 2.8... > -- > John **= Email 17 ==========================** Date: Fri, 22 Feb 2002 19:33:43 -0500 From: Thomas Dickey Subject: Re: Identifying sh.exe On Sat, Feb 23, 2002 at 01:39:03AM +0900, Jun Sawataishi wrote: > > > >Is there any way to identify which version of shell is being used from > >within a shell script? > > > >-- > >John > How about dowing like this zsh doesn't set a version (at least my check here doesn't show one). shells may inherit variables in a misleading fashion, as well. > if [ -n "$SH_VERSION" ] ; then > echo "shell: $SH_VERSION" > fi > if [ -n "$KSH_VERSION" ] ; then > echo "shell: $KSH_VERSION" > fi > if [ -n "$BASH_VERSION" ] ; then > echo "shell: $BASH_VERSION" > fi > # OS/2 is not a question, it's a solution. > # SAWATAISHI Jun > # http://www2s.biglobe.ne.jp/~vtgf3mpr/ > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 18 ==========================** Date: Fri, 22 Feb 2002 20:57:15 +0100 From: Andreas Buening Subject: Re: make 3.79.1 John Poltorak wrote: > > On Fri, Feb 22, 2002 at 12:22:27AM +0100, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > Can anyone get this to work with the Makefile in? :- > > > > > > emx\bsd\libc > > > > Should be fixed now: > > ftp://ftp.unixos2.com/incoming/make-3_79_1-bin-beta3.zip > > Yup. > > I can also use it to build emacs, which I couldn't before, although it > does trip up here:- > > emximp -o os2/tcp.a os2/tcp.imp > gcc -Zexe -DOS2 -O -Zmts tcp.c os2/tcp.a -Ios2 -o tcp > gcc -Zexe -DOS2 -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O os2/bdf2mfn.c -lc -o bdf2mfn > rc -r -x2 os2/pmcolors.rc > IBM RC (Resource Compiler) Version 5.00.006 Oct 20 2000 > Copyright (C) IBM Corp. 2000. > - Licensed Materials - Program Property of IBM - All Rights Reserved. > US Government Users Restricted Rights - Use, duplication or disclosure > restricted by GSA ADP Schedule Contract with IBM Corp. > > RC is creating binary resource file os2/pmcolors.res > > gcc -Zexe -DOS2 -O os2/pmcolors.c os2/pmcolors.def os2/pmcolors.res -o pmcolors > gcc -Zexe -DOS2 -O os2/pmsysfont.c -o pmsysfont > gcc -Zexe -DOS2 -c -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O > -DCONFIG_BROKETS -DINHIBIT_STRING_HEADER ../src/regex.c > gcc -Zexe -DOS2 -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O > -DVERSION="\"20.7\"" etags.c getopt.o getopt1.o regex.o -lc -o etags > etags.c: In function `print_version': > etags.c:512: stray '\' in program > etags.c:512: stray '\' in program > make[1]: *** [etags] Error 1 > make[1]: Leaving directory `C:/eval/emacs/emacs-20.7/lib-src' > make: *** [lib-src] Error 2 > > I don't get this error with v3.76.1, so suspect that it is a Make bug. Hmm, I have another suspicion. Which shell does this Makefile use? Is there a "SHELL = /bin/sh" line? I.e. do you get that "make: $SHELL changed (was `cmd.exe', now `/bin/sh')" message? If this is not the case set MAKESHELL=/bin/sh and try again. 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 Redmond where the Shadows lie. **= Email 19 ==========================** Date: Fri, 22 Feb 2002 20:58:04 +0100 From: Andreas Buening Subject: Re: EMACS build error Holger Veit wrote: > > On Thu, Feb 21, 2002 at 11:14:01PM +0100, Andreas Buening wrote: [snip] > > Okay, to be more precise: At work I cannot do the following > > in my home directory (it works only in /tmp): > > > > touch file1 > > md subdir > > ln file1 subdir/file2 > > > > Hard links are only possible _within_ the same directory and > > No. This is definitely wrong. That you have the impression is just > that your home directory where you have write access to is AFS > (and the other writeable directory is /tmp. Check other (real UNIX) > filesystems on that host with ls -l and look at the link count (this is > the number after the access rights): if it is > 1 then you have hard links > in progress. Okay, there are links in /usr, but nearly everything is linked to /afs. Therefore _I_ have practically no working hard links and therefore a reasonable program should be able to handle this. I don't think it will be the only AFS network on this planet. > > therefore quite useless, I've been told that this is an AFS > > feature, so better every serious Unix software should be > > This is not a feature, it is a broken file system: AFS emulates > hardlinks by hidden files, and the programmers were just lazy. > > > able to handle a failing link() without a core dump. > > Who has talked about a core dump? The result of a failing link() is > typically that temporary garbage file won't get cleaned up. > Some call this just annoying; I call it broken design of the underlying > file system. Okay, there was a irony tag missing. ;-) [snip] > > If config.h handles a missing lchown() it often uses stuff like > > #define lchown repl_lchown > > ... if the programmer took care at all. I have seen numerous autoconf'd > source packages where the generated config.h was just lying around, > or was included in each source file, but never ever any HAS_XXX > definition was evaluated at all. After all, the code worked fine under > Linux... ;-) Most of those HAVE_FOO statements are there because one autoconf test may push dozens of them into config.h. However, they aren't used that consequently in the source code as it was intended to be. > > which would be handled by "#ifndef lchown" in the code above, > > but in general you're right. I do not say that there could be > > a all in one solution of this problem. I only say that there > > are packages that could benefit from such a treatment > > (maybe less than 50%, I don't know). > > There is one more problem with that solution, not a technical one, but > a psychological one: You proposed to add this into the EMX header logic. > I have suggested more than once to modify EMX (even just for the simple > purpose of exporting the prominent strcasecmp()) - never happened. You mean EM won't put a simple "#define strcasecmp stricmp" into string.h? 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 Redmond where the Shadows lie. **= Email 20 ==========================** Date: Fri, 22 Feb 2002 21:14:03 +0000 From: John Poltorak Subject: Re: make 3.79.1 On Fri, Feb 22, 2002 at 08:57:15PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > gcc -Zexe -DOS2 -O os2/pmcolors.c os2/pmcolors.def os2/pmcolors.res -o pmcolors > > gcc -Zexe -DOS2 -O os2/pmsysfont.c -o pmsysfont > > gcc -Zexe -DOS2 -c -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O > > -DCONFIG_BROKETS -DINHIBIT_STRING_HEADER ../src/regex.c > > gcc -Zexe -DOS2 -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O > > -DVERSION="\"20.7\"" etags.c getopt.o getopt1.o regex.o -lc -o etags > > etags.c: In function `print_version': > > etags.c:512: stray '\' in program > > etags.c:512: stray '\' in program > > make[1]: *** [etags] Error 1 > > make[1]: Leaving directory `C:/eval/emacs/emacs-20.7/lib-src' > > make: *** [lib-src] Error 2 > > > > I don't get this error with v3.76.1, so suspect that it is a Make bug. > > Hmm, I have another suspicion. Which shell does this Makefile use? > Is there a "SHELL = /bin/sh" line? I.e. do you get that > "make: $SHELL changed (was `cmd.exe', now `/bin/sh')" message? > If this is not the case set MAKESHELL=/bin/sh and try again. There was no %SHELL% or %MAKESHELL% variable set in the environment or in the Makefile. I set both on in turn, both with BASH and PDKSH as /bin/sh, and it made no difference. There was no '$SHELL changed' msg. I tried using the debug flag, but didn't gain any additional info. > > 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 Redmond where the Shadows lie. -- John **= Email 21 ==========================** Date: Fri, 22 Feb 2002 21:18:01 +0900 From: Masaru Nomiya Subject: Re: Emacs customisation Hello, John. How tough you are! BTW In the Message; Subject : Emacs customisation Message-ID : <20020222111202.I23629 at eyup.org> Date & Time: Fri, 22 Feb 2002 11:12:03 +0000 [John] == John Poltorak has written: John> I've managed to get emacs v20.7 built, and I'd like to try and get a John> little comfortable with it. I've tried various builds in the past, but John> never managed to feel at home with emacs itself. I'm very glad, and I must tell to Mr. Sasaki, Mr.Nakagawa. John> I have normally used it as a text mode (vio) app in the past John> and am not sure if this new build lets it work in that mode... I'm sorry, but I can't understand the meaning of "text mode". John> One thing I would like to do is change the font - it's a large courier John> font at the moment, and would much prefer to use a small System Vio font. John> Is it possible to do that? Could you show me your .emacs and .XDefaults? In the Emacs 20.7 for OS/2, you can't use bdf fonts. That is, you must conver bdf fonts to mfn fonts. bdff2mfn.exe in the ..emacs-20.7/lib-src is the tool for this. When you use bdf2mfn.exe, this create FONTSET.OS2 at the same time. Copy FONTSET.OS2 to your home directory. Then you'll get multiligual world! John> How do I get it work more like EPM? Is there an available set of startup John> macros to emulate EPM? .....(_ _? Regards, --- Masaru Nomiya mail-to: nomiya at ttmy.ne.jp "No WIndows, no gains!" ..... "Why, I am wrong?" -- Bill -- **= Email 22 ==========================** Date: Fri, 22 Feb 2002 22:53:37 +0100 From: Andreas Buening Subject: Re: make 3.79.1 John Poltorak wrote: > > On Fri, Feb 22, 2002 at 08:57:15PM +0100, Andreas Buening wrote: > > John Poltorak wrote: > > > > gcc -Zexe -DOS2 -O os2/pmcolors.c os2/pmcolors.def os2/pmcolors.res -o pmcolors > > > gcc -Zexe -DOS2 -O os2/pmsysfont.c -o pmsysfont > > > gcc -Zexe -DOS2 -c -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O > > > -DCONFIG_BROKETS -DINHIBIT_STRING_HEADER ../src/regex.c > > > gcc -Zexe -DOS2 -D_BSD_SOURCE -DHAVE_CONFIG_H -I. -I../src -g -O > > > -DVERSION="\"20.7\"" etags.c getopt.o getopt1.o regex.o -lc -o etags > > > etags.c: In function `print_version': > > > etags.c:512: stray '\' in program > > > etags.c:512: stray '\' in program > > > make[1]: *** [etags] Error 1 > > > make[1]: Leaving directory `C:/eval/emacs/emacs-20.7/lib-src' > > > make: *** [lib-src] Error 2 > > > > > > I don't get this error with v3.76.1, so suspect that it is a Make bug. > > > > Hmm, I have another suspicion. Which shell does this Makefile use? > > Is there a "SHELL = /bin/sh" line? I.e. do you get that > > "make: $SHELL changed (was `cmd.exe', now `/bin/sh')" message? > > If this is not the case set MAKESHELL=/bin/sh and try again. > > There was no %SHELL% or %MAKESHELL% variable set in the environment or in > the Makefile. > > I set both on in turn, both with BASH and PDKSH as /bin/sh, and it made > no difference. There was no '$SHELL changed' msg. Did you use "MAKESHELL=/bin/sh"? "export MAKESHELL=/bin/sh" might be required. > I tried using the debug flag, but didn't gain any additional info. I think I know what happened. If there is no SHELL statement within the Makefile then cmd is used as default shell and you get no "$SHELL changed" message. And cmd cannot handle those backslash escaped quotes like -DVERSION="\"20.7\"" etags.c getopt.o getopt1.o regex.o -lc -o etags make 3.76 and earlier has some magic built in but therefore it fails on more complicated commands. 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 Redmond where the Shadows lie.