INFO-VAX Fri, 29 Feb 2008 Volume 2008 : Issue 120 Contents: Re: 6-core CPU on the horizon Re: 6-core CPU on the horizon Re: Buying disks for DS10s Re: Buying disks for DS10s Re: DCPS downloadable? Re: DCPS downloadable? Re: DCPS downloadable? Re: Eunice Re: Leap Year Re: Microsoft pro says OpenVMS best OS ever invented! Re: Microsoft pro says OpenVMS best OS ever invented! Re: Microsoft pro says OpenVMS best OS ever invented! Re: UnZip 6.0d source kit is available. Re: various MAKE tools for VMS Re: various MAKE tools for VMS Re: various MAKE tools for VMS Re: Wide drives on VAXstation 4000-60 Re: Wide drives on VAXstation 4000-60 ---------------------------------------------------------------------- Date: Fri, 29 Feb 2008 04:48:11 -0800 (PST) From: Neil Rieck Subject: Re: 6-core CPU on the horizon Message-ID: On Feb 28, 9:36=A0am, billg...@cs.uofs.edu (Bill Gunshannon) wrote: > In article <0f290c00-b750-40c8-a706-127667c4c...@o77g2000hsf.googlegroups.= com>, [...snip...] > Well, RSX-11 and RT-11 are hardly museum bait. =A0They are still sold and > maintained by Mentec and I know of a number of commercial operations > using them. =A0Oh yeah, and RSTS as well. > My point exactly. When OpenVMS stops laying (large enough) golden eggs for HP, they will sell it off to a smaller company rather than put the source code into the public domain which would allow an Open Source community to keep it alive and current. On the flip side, maybe JF's comment should be explored further: HP should do a deal with Intel to help pay for porting OpenVMS to x86-64. This way, Intel will have covered all their bases. The user community could then develop user apps on smaller OpenVMS platforms which could then be implemented are large corporate systems once sold. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: 29 Feb 2008 14:03:30 GMT From: billg999@cs.uofs.edu (Bill Gunshannon) Subject: Re: 6-core CPU on the horizon Message-ID: <62qhlhF24ut38U1@mid.individual.net> In article , Neil Rieck writes: > On Feb 28, 9:36 am, billg...@cs.uofs.edu (Bill Gunshannon) wrote: >> In article <0f290c00-b750-40c8-a706-127667c4c...@o77g2000hsf.googlegroups.com>, > [...snip...] >> Well, RSX-11 and RT-11 are hardly museum bait.  They are still sold and >> maintained by Mentec and I know of a number of commercial operations >> using them.  Oh yeah, and RSTS as well. >> > My point exactly. When OpenVMS stops laying (large enough) golden eggs > for HP, they will sell it off to a smaller company rather than put the > source code into the public domain which would allow an Open Source > community to keep it alive and current. Missed my point. I was just trying, once again, to show that contrary to popular belief the PDP-11 is still alive and well. As for you point above, different Corporation, different Corporate model. I see HP killing VMS when they are done with it. DEC passed RT/RSX/RSTS on when they were still extremely healthy OSes. DEC had just lost all interest in the PDP-11. In the case of VMS, whne HP decides it is done with VMS it will be because the cash cow is dead. Releasing it to the Open Source Community while an interesting concept is highly unlikely. A quick closed casket funerl and burial is the most likely occurance. > On the flip side, maybe JF's comment should be explored further: HP > should do a deal with Intel to help pay for porting OpenVMS to x86-64. > This way, Intel will have covered all their bases. The user community > could then develop user apps on smaller OpenVMS platforms which could > then be implemented are large corporate systems once sold. Being as there would be nothing in it for either HP or Intel, I can not comprehend why anyone would even consider this a possibility. HP has shown no interest in extending the life of VMW on the hardware it now supports, why would they invest any time or money to port it yet again. And considering the decimation of VMS Engineering in recent times, who do you think would do the job? And on another interesting side note, I have actually found one of the mythical DOD VMS systems. I recently threw my resume in the hat for a postion that is looking for someone who will "create, maintain and modify scientific software using FORTRAN 9x, C, and Pascal." In a later part under "Specialized Experience" it further specifies, "A working knowledge of FORTRAN 9X, C and Pascal using a VMS server." I wonder if it's a VAX? bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves billg999@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Fri, 29 Feb 2008 07:12:05 -0800 (PST) From: yyyc186 Subject: Re: Buying disks for DS10s Message-ID: <87b32f9a-d7c3-43d4-87b7-fe3ae4f7debc@u69g2000hse.googlegroups.com> On Feb 27, 12:56=A0pm, "Richard B. Gilbert" wrote: > yyyc186 wrote: > > Here is a much better question: > > > Has anyone tried any of those 2TB network enclosures you see being > > sold at places like Microcenter? =A0They claim to have a Gigabit > > interface. =A0I was wondering if they could be made to play with a DS10 > > running a hobbiest license. =A0I don't mind leaving the boot disk on the= > > DS10, but was thinking it would make getting 2TB of storage worth > > while if I could spread it across many machines. > I only have a passing interest in this. My Alpha is currently powered off. Other than sending out an email when the SOA book is finally printed, I don't have plans to turn it back on. If HP hadn't completely and officially abandoned OpenVMS, I might have followed through in helping to port PostGreSQL to OpenVMS so we could have a REAL database which was OpenSource on the platform. (MySQL is OpenSource, but not a REAL database. The InnoDB it actually uses is now owned by Oracle and Oracle will be squeezing that orange shortly.) The 2TB boxes interest me only because I could share disk space between my Ubuntu workstation, Ubuntu notebook, and Alpha. I was hoping to avoid setting up yet another server to be a file server. I could have left Netware running if I wanted to do that. Then again, this only works if there is a reasonably cheap GigaBit card for the DS10 and if I upgrade my internal office network to GigaBit. ------------------------------ Date: Fri, 29 Feb 2008 11:25:54 -0500 From: "Richard B. Gilbert" Subject: Re: Buying disks for DS10s Message-ID: <47C83212.8000109@comcast.net> yyyc186 wrote: > On Feb 27, 12:56 pm, "Richard B. Gilbert" > wrote: > >>yyyc186 wrote: >> >>>Here is a much better question: >> >>>Has anyone tried any of those 2TB network enclosures you see being >>>sold at places like Microcenter? They claim to have a Gigabit >>>interface. I was wondering if they could be made to play with a DS10 >>>running a hobbiest license. I don't mind leaving the boot disk on the >>>DS10, but was thinking it would make getting 2TB of storage worth >>>while if I could spread it across many machines. >> > > I only have a passing interest in this. My Alpha is currently powered > off. Other than sending out an email when the SOA book is finally > printed, I don't have plans to turn it back on. If HP hadn't > completely and officially abandoned OpenVMS, I might have followed > through in helping to port PostGreSQL to OpenVMS so we could have a > REAL database which was OpenSource on the platform. (MySQL is > OpenSource, but not a REAL database. The InnoDB it actually uses is > now owned by Oracle and Oracle will be squeezing that orange shortly.) > > The 2TB boxes interest me only because I could share disk space > between my Ubuntu workstation, Ubuntu notebook, and Alpha. I was > hoping to avoid setting up yet another server to be a file server. I > could have left Netware running if I wanted to do that. Then again, > this only works if there is a reasonably cheap GigaBit card for the > DS10 and if I upgrade my internal office network to GigaBit. > > Please be a little more careful with your attributions and/or trimming!! I did not write ANY of the above text! Richard B. Gilbert ------------------------------ Date: Fri, 29 Feb 2008 10:24:17 +0100 From: "Maarten van Breemen" Subject: Re: DCPS downloadable? Message-ID: <47c7cf52$0$662$4d4ebb8e@read.news.nl.uu.net> I strongly support your suggestion that HP should make new DCPS versions available without having to buy a complete CONDIST media set. It even prevents us buying new HP printer models because the first investment in a new model has these silly costs added. DCPS is the only piece of software I would like to update the coming years. I don't need CONDIST for other products. Maarten "Rich Jordan" wrote in message news:7da53c14-68b5-49d1-a774-13ef37d0e0b9@s37g2000prg.googlegroups.com... >I think the answer is 'no' but I thought I'd ask. Since DSPP > discontinued the Alpha media kit as part of the service, severely > downgrading their usefulness to us, we only get very rare updates. > Usually when a new OS release comes out we'll get the next quarterly > kit. > > OpenVMS Alpha V8.3 includes DCPS 2.5 on the layered products disk. > I've been asked to see if getting V2.6 is possible without spending > unhealthy gobs of money on a CONDIST set. > > If it still isn't I'll just tell them they need to shell out some more > cash. > > I'll echo an earlier post here on this subject; it would be awfully > nice if HP made layered products that are licensed with the OS > available without spending so much on a media kit. > > Thanks > > Rich ------------------------------ Date: Fri, 29 Feb 2008 11:13:38 -0000 From: "Roger Fraser" Subject: Re: DCPS downloadable? Message-ID: <47c7e4ed$1_1@glkas0286.greenlnk.net> They are available at ftp://ftp.itrc.hp.com/product_patches/hpdecprintsupervisor/dcps/openvms/ HTH Roger "Maarten van Breemen" wrote in message news:47c7cf52$0$662$4d4ebb8e@read.news.nl.uu.net... >I strongly support your suggestion that HP should make new DCPS versions >available without having to buy a complete CONDIST media set. > It even prevents us buying new HP printer models because the first > investment in a new model has these silly costs added. > DCPS is the only piece of software I would like to update the coming > years. I don't need CONDIST for other products. > > Maarten > > "Rich Jordan" wrote in message > news:7da53c14-68b5-49d1-a774-13ef37d0e0b9@s37g2000prg.googlegroups.com... >>I think the answer is 'no' but I thought I'd ask. Since DSPP >> discontinued the Alpha media kit as part of the service, severely >> downgrading their usefulness to us, we only get very rare updates. >> Usually when a new OS release comes out we'll get the next quarterly >> kit. >> >> OpenVMS Alpha V8.3 includes DCPS 2.5 on the layered products disk. >> I've been asked to see if getting V2.6 is possible without spending >> unhealthy gobs of money on a CONDIST set. >> >> If it still isn't I'll just tell them they need to shell out some more >> cash. >> >> I'll echo an earlier post here on this subject; it would be awfully >> nice if HP made layered products that are licensed with the OS >> available without spending so much on a media kit. >> >> Thanks >> >> Rich > > ------------------------------ Date: Fri, 29 Feb 2008 11:40:55 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: DCPS downloadable? Message-ID: Roger Fraser wrote: > They are available at > ftp://ftp.itrc.hp.com/product_patches/hpdecprintsupervisor/dcps/openvms/ > > HTH > > Roger Not the base kit, only the ECO's... Jan-Erik. ------------------------------ Date: 29 Feb 2008 07:35:07 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Eunice Message-ID: <9rFZpujw+wqF@eisner.encompasserve.org> In article <3_Dxj.9180$xg6.871@trnddc07>, John Santos writes: > > VMS doesn't open any channels if you don't let it... If you don't go through the VMS kernel, you aren't going to open any, either. ------------------------------ Date: Fri, 29 Feb 2008 07:49:46 -0800 (PST) From: Hein RMS van den Heuvel Subject: Re: Leap Year Message-ID: On Feb 28, 6:18=A0am, "The Mip" wrote: > Some told me that chance of 29. feb. would be a Friday (as this year) was > close to average, but that not all weekdays was on average. Cute! Never though about that. > That did sound strange to me, so i wrote a little DCL I can not help but comment a little on the DCL 1) What's with all the substitutions?! Don't trust yourself (or DCL?) 2) $ if p2 .eqs. "" then exit Unreachable. If p1 is empty, then p2 must be empty 3) $ if ('p1'/4)*4 .ne. 'p1' .or. - ('p1'/100)*100 .eq.'p.... Yuck, hardcoded leapyear logic. Too easy to get wrong. Here is an DCL aided leap-year test: IF F$CVTIME("1-MAR-''year' -1-",,"DAY") ... ! Leap year? Remember Odd is True! 28 is not. 4) $ If Weekday .eqs. "Sunday" then Sundays =3D 'Sundays' + 1 You know DCL substitututions work for symbols as well right? So that changes into a one-fole-all: 'weekday's =3D 'weekday's + 1 5) $ write sys$output " ''p1' is not a leap Year " Unforgiving! Why not help a little. Combining this gives: $! 29_feb.com $! $ if p1 .eqs. "" then exit $ year =3D 'p1' $ days =3D 0 $ Sundays =3D 0 $ Mondays =3D 0 $ Tuesdays =3D 0 $ Wednesdays =3D 0 $ Thursdays =3D 0 $ Fridays =3D 0 $ Saturdays =3D 0 $! $ loop: $ IF F$CVTIME("1-MAR-''year' -1-",,"DAY") ! Leap year? $ THEN $ weekday =3D F$CVTIME("29-feb-''year'",,"weekday") $ 'weekday's =3D 'weekday's + 1 $ days =3D days + 1 $ ENDIF $! $ Year =3D Year + 1 $ if 'Year' .lt. p2 then goto loop $! $ pct=3D 10000*'Sundays'/ 'days' $ write sys$output " Sunday: ''Sundays' (''pct' %%) " $ pct=3D 10000*'Mondays'/ 'days' $ write sys$output " Monday: ''Mondays' (''pct' %%) " $ pct=3D 10000*'Tuesdays'/ 'days' $ write sys$output " Tuesday: ''Tuesdays' (''pct' %%) " $ pct=3D 10000*'Wednesdays'/'days' $ write sys$output " Wednesday: ''Wednesdays' (''pct' %%) " $ pct=3D 10000*'Thursdays' / 'days' $ write sys$output " Thursday: ''Thursdays' (''pct' %%) " $ pct=3D 10000*'Fridays' / 'days' $ write sys$output " Friday: ''Fridays' (''pct' %%) " $ pct=3D 10000*'Saturdays' / 'days' $ write sys$output " Saturday: ''Saturdays' (''pct' %%) " The hardcoded day names however are still ugly, tedious, error-prone and not internationalized. We can replace those by loops through the days and then we get: $! 29_feb.com $! $ if p1 .eqs. "" then exit $ year =3D 'p1' $ days =3D 0 $ day =3D 7 $day_init_loop: $ weekday =3D F$CVTIME("+''day'-",,"WEEKDAY") ! Pick a day, any day. $ 'weekday' =3D 0 $ day =3D day - 1 $ IF day .GT. 0 THEN GOTO day_init_loop $ $main_loop: $ IF F$CVTIME("1-MAR-''year' -1-",,"DAY") ! Leap year? $ THEN $ weekday =3D F$CVTIME("29-feb-''year'",,"weekday") $ 'weekday' =3D 'weekday' + 1 $ days =3D days + 1 $ ENDIF $! $ Year =3D Year + 1 $ if 'Year' .lt. p2 then goto main_loop $! $display_loop: $ weekday =3D F$CVTIME("1-JAN-2006 +''day'-",,"WEEKDAY") ! Pick a Sunday, any Sunday. $ WRITE SYS$OUTPUT F$FAO("!15AS !3UL (!4UL)%%", - weekday + ":", 'weekday', 10000*'weekday' / days) $ day =3D day + 1 $ IF day .LT. 7 THEN GOTO display_loop Thanks for the smiles! Hein ------------------------------ Date: Fri, 29 Feb 2008 09:11:55 -0800 (PST) From: ultradwc@gmail.com Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: On Feb 21, 7:38=A0pm, ultra...@gmail.com wrote: > http://visualstudiomagazine.com/columns/article.aspx?editorialsid=3D2469 this thread needs to stay at the top of this group for a long time ... ------------------------------ Date: Fri, 29 Feb 2008 13:37:16 -0500 From: JF Mezei Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: <47c8512f$0$10289$c3e8da3@news.astraweb.com> ultradwc@gmail.com wrote: > On Feb 21, 7:38 pm, ultra...@gmail.com wrote: >> http://visualstudiomagazine.com/columns/article.aspx?editorialsid=2469 > > this thread needs to stay at the top of this group for a long time ... Yep, that is to be VMS' epitaph. It *WAS* better than Windows. I guess articles that talk about VMS in the past are perhaps better than no articles at all. But right now, the industry talks of VMS like they talk of Multics. ------------------------------ Date: Fri, 29 Feb 2008 13:45:46 -0500 From: "Richard B. Gilbert" Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: <47C852DA.4050409@comcast.net> JF Mezei wrote: > ultradwc@gmail.com wrote: > >>On Feb 21, 7:38 pm, ultra...@gmail.com wrote: >> >>>http://visualstudiomagazine.com/columns/article.aspx?editorialsid=2469 >> >>this thread needs to stay at the top of this group for a long time ... > > > > Yep, that is to be VMS' epitaph. It *WAS* better than Windows. > > I guess articles that talk about VMS in the past are perhaps better than > no articles at all. But right now, the industry talks of VMS like they > talk of Multics. I spent some twenty-five years in IT and the ONLY mention Multics ever got was in books about the origins of Unix. Apparently the name was picked to contrast with Multics! ------------------------------ Date: Fri, 29 Feb 2008 11:26:25 +0100 From: joukj Subject: Re: UnZip 6.0d source kit is available. Message-ID: <47C7DDD1.2050608@hrem.nano.tudelft.nl> Steven M. Schweda wrote: > A source kit for UnZip 6.0d (pre-release, "BETA") should be available > at the usual places: > > ftp://ftp.info-zip.org/pub/infozip/beta/unzip60d.zip > http://downloads.sourceforge.net/infozip/unzip60d.zip > > It should be pretty close to the real UnZip 6.0, particularly on VMS. > This kit should cure the long-standing spurious "76 bytes" warning > messages (6.0c), and should solve all known problems, while adding > support for large files, ODS5 extended file specs, bzip2 compression, > symbolic links, and a typical set of bug fixes. > > Problems which are reported promptly may get fixed in the real > release. > > Zip 3.0g (also pre-release, "BETA") source kits should be available > nearby. > > Complaints are always welcome. > Unzipping a zip-file created on a Linux system gives me lots of warnings like the ones below. I did not get these with the 6.0c unzip. I think the .^] should be read as : ]^. to have the right VMS file specification. Jouk warning: set-dir-attributes failed ($parse) for [.imagemagick.ImageMagick.www.s ource.^]svn.DIR;1. [ %RMS-F-SYN, file specification syntax error ] warning: set times/attribs failed for [.imagemagick.ImageMagick.www.source.^.sv n] warning: set-dir-attributes failed ($parse) for [.imagemagick.ImageMagick.www.a pi.^]svn.DIR;1. [ %RMS-F-SYN, file specification syntax error ] warning: set times/attribs failed for [.imagemagick.ImageMagick.www.api.^.svn] warning: set-dir-attributes failed ($parse) for [.imagemagick.ImageMagick.www.a pi.MagickWand.^]svn.DIR;1. [ %RMS-F-SYN, file specification syntax error ] warning: set times/attribs failed for [.imagemagick.ImageMagick.www.api.MagickW and.^.svn] warning: set-dir-attributes failed ($parse) for [.imagemagick.ImageMagick.www.a pi.MagickCore.^]svn.DIR;1. ------------------------------ Date: Fri, 29 Feb 2008 00:45:39 -0800 (PST) From: Pierre Subject: Re: various MAKE tools for VMS Message-ID: > You mean like this? > > [.$(DEST)]ZIPCLOAK.EXE : [.$(DEST)]ZIPCLOAK.OBJ \ > $(LIB_ZIPUTILS) \ > $(OPT_ID) $(OPT_FILE) > $(LINK) $(LINKFLAGS) $(MMS$SOURCE), - > $(LIB_ZIPUTILS) /include = (GLOBALS) /library, - > $(LFLAGS_ARCH) - > $(OPT_ID) /options > > (I tend to use "\" in the dependencies, and "-" in the (DCL) action > lines, but I may be eccentric.) You may be trying to solve problems > which do not exist in MMS/MMK. I mean like this: -- # makefile for building Lua # see ../INSTALL for installation instructions # see ../Makefile and luaconf.h for further customization # == CHANGE THE SETTINGS BELOW TO SUIT YOUR ENVIRONMENT ======================= # Your platform. See PLATS for possible values. PLAT= none CC= gcc CFLAGS= -O2 -Wall $(MYCFLAGS) AR= ar rcu RANLIB= ranlib RM= rm -f LIBS= -lm $(MYLIBS) MYCFLAGS= MYLDFLAGS= MYLIBS= # == END OF USER SETTINGS. NO NEED TO CHANGE ANYTHING BELOW THIS LINE ========= PLATS= aix ansi bsd freebsd generic linux macosx mingw posix solaris LUA_A= liblua.a CORE_O= lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o \ lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o \ lundump.o lvm.o lzio.o LIB_O= lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o \ lstrlib.o loadlib.o linit.o LUA_T= lua LUA_O= lua.o LUAC_T= luac LUAC_O= luac.o print.o ALL_O= $(CORE_O) $(LIB_O) $(LUA_O) $(LUAC_O) ALL_T= $(LUA_A) $(LUA_T) $(LUAC_T) ALL_A= $(LUA_A) default: $(PLAT) all: $(ALL_T) o: $(ALL_O) a: $(ALL_A) $(LUA_A): $(CORE_O) $(LIB_O) $(AR) $@ $? $(RANLIB) $@ $(LUA_T): $(LUA_O) $(LUA_A) $(CC) -o $@ $(MYLDFLAGS) $(LUA_O) $(LUA_A) $(LIBS) $(LUAC_T): $(LUAC_O) $(LUA_A) $(CC) -o $@ $(MYLDFLAGS) $(LUAC_O) $(LUA_A) $(LIBS) clean: $(RM) $(ALL_T) $(ALL_O) depend: @$(CC) $(CFLAGS) -MM l*.c print.c echo: @echo "PLAT = $(PLAT)" @echo "CC = $(CC)" @echo "CFLAGS = $(CFLAGS)" @echo "AR = $(AR)" @echo "RANLIB = $(RANLIB)" @echo "RM = $(RM)" @echo "MYCFLAGS = $(MYCFLAGS)" @echo "MYLDFLAGS = $(MYLDFLAGS)" @echo "MYLIBS = $(MYLIBS)" # convenience targets for popular platforms none: @echo "Please choose a platform:" @echo " $(PLATS)" aix: $(MAKE) all CC="xlc" CFLAGS="-O2 -DLUA_USE_POSIX -DLUA_USE_DLOPEN" MYLIBS="-ldl" MYLDFLAGS="-brtl -bexpall" ansi: $(MAKE) all MYCFLAGS=-DLUA_ANSI bsd: $(MAKE) all MYCFLAGS="-DLUA_USE_POSIX -DLUA_USE_DLOPEN" MYLIBS="-Wl,- E" freebsd: $(MAKE) all MYCFLAGS="-DLUA_USE_LINUX" MYLIBS="-Wl,-E -lreadline" generic: $(MAKE) all MYCFLAGS= linux: $(MAKE) all MYCFLAGS=-DLUA_USE_LINUX MYLIBS="-Wl,-E -ldl -lreadline - lhistory -lncurses" macosx: $(MAKE) all MYCFLAGS=-DLUA_USE_LINUX MYLIBS="-lreadline" # use this on Mac OS X 10.3- # $(MAKE) all MYCFLAGS=-DLUA_USE_MACOSX mingw: $(MAKE) "LUA_A=lua51.dll" "LUA_T=lua.exe" \ "AR=$(CC) -shared -o" "RANLIB=strip --strip-unneeded" \ "MYCFLAGS=-DLUA_BUILD_AS_DLL" "MYLIBS=" "MYLDFLAGS=-s" lua.exe $(MAKE) "LUAC_T=luac.exe" luac.exe posix: $(MAKE) all MYCFLAGS=-DLUA_USE_POSIX solaris: $(MAKE) all MYCFLAGS="-DLUA_USE_POSIX -DLUA_USE_DLOPEN" MYLIBS="-ldl" # list targets that do not create files (but not all makes understand .PHONY) .PHONY: all $(PLATS) default o a clean depend echo none # DO NOT DELETE lapi.o: lapi.c lua.h luaconf.h lapi.h lobject.h llimits.h ldebug.h \ lstate.h ltm.h lzio.h lmem.h ldo.h lfunc.h lgc.h lstring.h ltable.h \ lundump.h lvm.h lauxlib.o: lauxlib.c lua.h luaconf.h lauxlib.h lbaselib.o: lbaselib.c lua.h luaconf.h lauxlib.h lualib.h lcode.o: lcode.c lua.h luaconf.h lcode.h llex.h lobject.h llimits.h \ lzio.h lmem.h lopcodes.h lparser.h ldebug.h lstate.h ltm.h ldo.h lgc.h \ ltable.h ldblib.o: ldblib.c lua.h luaconf.h lauxlib.h lualib.h ldebug.o: ldebug.c lua.h luaconf.h lapi.h lobject.h llimits.h lcode.h \ llex.h lzio.h lmem.h lopcodes.h lparser.h ldebug.h lstate.h ltm.h ldo.h \ lfunc.h lstring.h lgc.h ltable.h lvm.h ldo.o: ldo.c lua.h luaconf.h ldebug.h lstate.h lobject.h llimits.h ltm.h \ lzio.h lmem.h ldo.h lfunc.h lgc.h lopcodes.h lparser.h lstring.h \ ltable.h lundump.h lvm.h ldump.o: ldump.c lua.h luaconf.h lobject.h llimits.h lstate.h ltm.h \ lzio.h lmem.h lundump.h lfunc.o: lfunc.c lua.h luaconf.h lfunc.h lobject.h llimits.h lgc.h lmem.h \ lstate.h ltm.h lzio.h lgc.o: lgc.c lua.h luaconf.h ldebug.h lstate.h lobject.h llimits.h ltm.h \ lzio.h lmem.h ldo.h lfunc.h lgc.h lstring.h ltable.h linit.o: linit.c lua.h luaconf.h lualib.h lauxlib.h liolib.o: liolib.c lua.h luaconf.h lauxlib.h lualib.h llex.o: llex.c lua.h luaconf.h ldo.h lobject.h llimits.h lstate.h ltm.h \ lzio.h lmem.h llex.h lparser.h lstring.h lgc.h ltable.h lmathlib.o: lmathlib.c lua.h luaconf.h lauxlib.h lualib.h lmem.o: lmem.c lua.h luaconf.h ldebug.h lstate.h lobject.h llimits.h \ ltm.h lzio.h lmem.h ldo.h loadlib.o: loadlib.c lua.h luaconf.h lauxlib.h lualib.h lobject.o: lobject.c lua.h luaconf.h ldo.h lobject.h llimits.h lstate.h \ ltm.h lzio.h lmem.h lstring.h lgc.h lvm.h lopcodes.o: lopcodes.c lopcodes.h llimits.h lua.h luaconf.h loslib.o: loslib.c lua.h luaconf.h lauxlib.h lualib.h lparser.o: lparser.c lua.h luaconf.h lcode.h llex.h lobject.h llimits.h \ lzio.h lmem.h lopcodes.h lparser.h ldebug.h lstate.h ltm.h ldo.h \ lfunc.h lstring.h lgc.h ltable.h lstate.o: lstate.c lua.h luaconf.h ldebug.h lstate.h lobject.h llimits.h \ ltm.h lzio.h lmem.h ldo.h lfunc.h lgc.h llex.h lstring.h ltable.h lstring.o: lstring.c lua.h luaconf.h lmem.h llimits.h lobject.h lstate.h \ ltm.h lzio.h lstring.h lgc.h lstrlib.o: lstrlib.c lua.h luaconf.h lauxlib.h lualib.h ltable.o: ltable.c lua.h luaconf.h ldebug.h lstate.h lobject.h llimits.h \ ltm.h lzio.h lmem.h ldo.h lgc.h ltable.h ltablib.o: ltablib.c lua.h luaconf.h lauxlib.h lualib.h ltm.o: ltm.c lua.h luaconf.h lobject.h llimits.h lstate.h ltm.h lzio.h \ lmem.h lstring.h lgc.h ltable.h lua.o: lua.c lua.h luaconf.h lauxlib.h lualib.h luac.o: luac.c lua.h luaconf.h lauxlib.h ldo.h lobject.h llimits.h \ lstate.h ltm.h lzio.h lmem.h lfunc.h lopcodes.h lstring.h lgc.h \ lundump.h lundump.o: lundump.c lua.h luaconf.h ldebug.h lstate.h lobject.h \ llimits.h ltm.h lzio.h lmem.h ldo.h lfunc.h lstring.h lgc.h lundump.h lvm.o: lvm.c lua.h luaconf.h ldebug.h lstate.h lobject.h llimits.h ltm.h \ lzio.h lmem.h ldo.h lfunc.h lgc.h lopcodes.h lstring.h ltable.h lvm.h lzio.o: lzio.c lua.h luaconf.h llimits.h lmem.h lstate.h lobject.h ltm.h \ lzio.h print.o: print.c ldebug.h lstate.h lua.h luaconf.h lobject.h llimits.h \ ltm.h lzio.h lmem.h lopcodes.h lundump.h # (end of Makefile) ------------------------------ Date: Fri, 29 Feb 2008 09:14:39 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: various MAKE tools for VMS Message-ID: <47c8134e$0$90265$14726298@news.sunsite.dk> Pierre wrote: > I mean like this: > > -- > > # makefile for building Lua > # see ../INSTALL for installation instructions > # see ../Makefile and luaconf.h for further customization > > # == CHANGE THE SETTINGS BELOW TO SUIT YOUR ENVIRONMENT > ======================= > > # Your platform. See PLATS for possible values. > PLAT= none > > CC= gcc > CFLAGS= -O2 -Wall $(MYCFLAGS) > AR= ar rcu > RANLIB= ranlib > RM= rm -f > LIBS= -lm $(MYLIBS) > > MYCFLAGS= > MYLDFLAGS= > MYLIBS= > > # == END OF USER SETTINGS. NO NEED TO CHANGE ANYTHING BELOW THIS LINE > ========= > > PLATS= aix ansi bsd freebsd generic linux macosx mingw posix solaris I would try a port of GNU Make. Arne ------------------------------ Date: Fri, 29 Feb 2008 14:37:36 GMT From: "John E. Malmberg" Subject: Re: various MAKE tools for VMS Message-ID: Arne Vajhøj wrote: > Pierre wrote: >> I mean like this: >> >> -- >> >> # makefile for building Lua >> # see ../INSTALL for installation instructions >> # see ../Makefile and luaconf.h for further customization >> >> # == CHANGE THE SETTINGS BELOW TO SUIT YOUR ENVIRONMENT >> ======================= >> >> # Your platform. See PLATS for possible values. >> PLAT= none >> > >> PLATS= aix ansi bsd freebsd generic linux macosx mingw posix solaris > > I would try a port of GNU Make. GNU make is in the GNV kits for Alpha and I64. See the updates at ftp.encompasserve.org/gnv. Some of them are still needed for 2.1. Unix like make scripts may not run properly under DCL as they may expect a UNIX shell and tool kit to also be present. One of the updates to GNV at ftp.encompasserve.org/gnv is a Bash that does not have the pipe size limitations. Other GNV tools need the same fix, but I have not had the time to do it. -John wb8tyw@qsl.net Personal Opinion Only ------------------------------ Date: Fri, 29 Feb 2008 07:31:35 GMT From: Roger Ivie Subject: Re: Wide drives on VAXstation 4000-60 Message-ID: On 2008-02-29, Chris Scheers wrote: > Can anyone provide a suggestion on how to get this to work? Is there > some switch setting I am missing? Make certain you've set the drive address to the range 0 through 7. Drives are selected on SCSI using data bus bits, so with a narrow SCSI you can't select an address higher than 7. I have used a wide drive on a narrow machine; it's been a while, so I don't recall offhand whether it was a VAX or an Alpha. The drive that I used was (IIRC) some flavor of Barracuda pulled from a dead SparcStation of some sort. It had a single fine-pitch connector for SCSI, power, and drive select jumpers. I found an adapter on the net that plugged into the drive to pull out an 8-bit SCSI, power to a Molex connector, and provide push-on jumpers for drive select. With that adapter on the drive, I was able to simply mount it in the machine and use the internal SCSI cable to talk to the thing. -- roger rivie rivie@ridgenet.net ------------------------------ Date: Fri, 29 Feb 2008 10:03:37 +0000 From: Gary Parker Subject: Re: Wide drives on VAXstation 4000-60 Message-ID: <2008022910033716807-gjparker@lboroacuk> On 2008-02-29 06:23:42 +0000, Chris Scheers said: > Can anyone provide a suggestion on how to get this to work? Is there > some switch setting I am missing? I'm currently running a wide Seagate Baracuda ST34371W in a uVAX 3100-30. The trick is to ensure you're using an active terminator at the end of the chain and that you've got term-power enabled on the drive. Gary ------------------------------ End of INFO-VAX 2008.120 ************************