HDTenEightyP/NetNews huggingface dataset:
From: swispl@solomon.technet.sg (SW International)
Subject: GS 2.52 on ICL DRS6000 ?
Organization: TECHNET, Singapore
X-Newsreader: TIN [version 1.1 PL8]
Date: Fri, 18 Dec 1992 06:51:06 GMT


Hello everyone !

We have here a DRS6000 from ICL, running SVR4:
# uname -a
unix unicorn 4.0 5.1.04 DRS 6000 sparc

I have tried building Ghostscript 2.5.2 on this machine using the
SVR$ settings. I have several problems:

a) In gdevepsn.c (line 101 and 107) I get an Initialiser doesn't fit
	warning, showing values of 131 and 168. They are assigned
	to char, so I assume that char is *signed*?

b) In iinit.c, there are a few places where it seems that a constant
	variable is assigned to. I don't have my ANSI-Standards around,
	but this looks wrong to me:

---- iinit.c ----
[...]
   163	/* Run the initialization procedures of the individual operator files. */
   164	void
   165	zop_init()
   166	{	op_def_ptr _ds *tptr;
   167		op_def_ptr def;
		^^^^^^^^^^op-def_ptr is typedef'd const in opdef.h
   168		for ( tptr = op_defs_all; *tptr != 0; tptr++ )
   169		   {	for ( def = *tptr; def->oname != 0; def++ ) ;
                              ^^^ assigned here             ^^^^
   170			if ( def->proc != 0 )
   171				((void (*)(P0()))(def->proc))();
   172		   }
   173	}
   174	/* Initialize the operator table. */
   175	void
   176	op_init()
   177	{	int count = 1;
   178		op_def_ptr _ds *tptr;
   179		op_def_ptr def;
                ^^^^^^^^^^^^^^same here
   180		const char _ds *nstr;
   181	
   182		/* Do a first pass just to count the operators. */
   183	
   184		for ( tptr = op_defs_all; *tptr != 0; tptr ++ )
   185		 for ( def = *tptr; def->oname != 0; count++, def++ )
                       ^^^^and here
[...]
--------
and some other places.

	It looks wrong, but I'm not a ANSI guru, and my H&S is far away...
	My compiler certainly barfs here..

c)	The gettimeofday of the DRS6000 only knows one argument, the
	struct time pointer, not the struct timezone one. I can use
	the global timezone variable to get around it, but is there
	a better way?


So here is my foremost question: Has anyone got GS to run on such
a machine and is willing to share the info?

Thx alot

Mathias

--
SW International Systems Pte Ltd     |  "I've got a plan so cunning 
    14, Science Park Drive           | you could put a tail on it and
    Singapore Science Park           | call it a weasel".. Black Adder
    Singapore 0511                   | 
    Tel: (65) 778-0066               |
    Fax: (65) 777-9401               | swispl@solomon.technet.sg
From: jhenders@jonh.wimsey.bc.ca (John Henders)
Newsgroups: gnu.misc.discuss
Distribution: world
Organization:  One of these days for sure
X-News: HERMES MMAIL 1.10 Rev. Nov 25 1992
Subject: Re: Dylan supported by GNU in future ?
	<F7LVVB14w165w@mantis.co.uk> <1gnu87INNguv@uwm.edu>
	<1992Dec17.012658.11627@u.washington.edu>
	<1992Dec18.111753.38592@news.th-darmstadt.de>
Date: Fri, 18 Dec 1992 15:50:16 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In <1992Dec18.111753.38592@news.th-darmstadt.de>
	schrod@iti.informatik.th-darmstadt.de (Joachim Schrod) writes:

>In article <1992Dec17.012658.11627@u.washington.edu>,
	tzs@carson.u.washington.edu (Tim Smith) writes:
>> 
>> So why did Apple pay off the guy who claimed Hypercard infringed his
>> patent rather than just litigate his tiny company out of existence?

>Pay off ??? You're either kidding or you don't follow the discussion
>on software patents.

>Read the article of this guy in the CACM (`Debunking the Myth of
>Software Patents'), where he tells you in his introduction about the
>behaviour of Apple.
>    Btw, the most funny thing in this article is that this guy was
>_not_ able to enforce his patent, that he is now to shy to suit
>(obviously because he fears the `quality' of Apple's lawyers), and
>that he still defends software patents.

	Another interesting data point on this guy, Paul Heckel, I beleive.
The patent stems from a program for Msdos, and atari ST called
Zoomracks. The author, shortly befgore launching his suit against Apple,
advertised a major upgrade for the Atari ST version, promising lots of
nice features, and solicited prepayment for the upgrade. Surprisingly
enough, no upgrade and no refund ever arrived. Anyone want to take a
wild guess at what he used for legal fees?

-- 

 "If Rush fans were braindead, why are there so   Bruce Bufalini
 many people posting to alt.music.rush?"              PSU
Newsgroups: gnu.misc.discuss
From: pshannon@iapetus.cv.nrao.edu (Paul Shannon)
Subject: RFC: using Texinfo and InterViews for a context-sensitive help program
Organization: nrao
Distribution: gnu
Date: Mon, 14 Dec 1992 19:40:48 GMT

We'd like to get comments on a small project we're about to begin.  By 
"comments" I mean anything like

 1. "this is a great idea, please let us use the code when you're done"
 2. "this was done months ago, look at anon ftp site xxx.yyy.zzz for 
    a copy"
 3. "this is a stupid idea, for these reasons....."


                A Context-sensitive help program, based upon
                      Texinfo and InterViews

By using the GNU project's Texinfo for documentation, we're able to have a
single source file for printed manuals and and on-line help.  So there's
two ways to read the Texinfo source: print it out, or  use emacs in info
mode.  We want to add a third way:  a program with a graphical user
interface that responds  to ipc requests (over a socket, for instance),
by displaying a particular node in the file.  Once this node is displayed,
the user can navigate using the normal info keyboard commands (m,d,u,....) 
and with corresponding gui widgets as well (menus, buttons, and sliders).

This gui program, sensitive to ipc requests, will allow us to provide
context-sensitive help to our users:  any of our application programs
that knows the protocol (socket number, node names, info navigation commands)
can popup the Texinfo viewer, at a particular node, at will.

In time we'd like to add printing, bookmarks, different fonts, and perhaps 
the ability to display postscript.

We propose to use the C++ gui toolkit InterViews.  IV has many strengths:

   1. written in C++, with classes that are easily adapted to
      the model-view-controller approach to gui design
   2. public domain source
   3. isolation of X and OS related code
   4. may become the standard X consortium C++ toolkit
  
and some weaknesses
   
   1. few examples to learn from
   2. scant documentation 
   3. unstable design:  though version 3.0 brought glyphs, and 3.1
      introduced object creation kits, these rest uneasily among
      classes left over from the earlier 2.6 design.
   4. some functionality from the X Intrinsics is not
      available: XtWorkProc, for example, allows the programmer
      to install a task to run whenever no events are pending; 
      this is difficult to do in IV.

There's an InterViews 2.6 application, ivinfo, available on the ftp
archive at interviews.stanford.edu, which contains some code we'd
either use directly or learn from.

We plan to distribute the code for our larger project (aips++, an image
processing tools for radio astronomy) under the gnu copyleft agreement.
We would do the same for the context-sensitive help program as well.

Any comments, criticisms or suggestions?

   Paul Shannon
   pshannon@nrao.edu
   National Radio Astronomy Observatory



Newsgroups: gnu.misc.discuss
From: lynbech@daimi.aau.dk (Christian Lynbech)
Subject: Re: texinfo manual for C library functions
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark
Date: Wed, 16 Dec 92 09:08:22 GMT

slhpv@cc.usu.edu writes:


>Has anyone created a texinfo file which documents the functions, types, and
>macros contained in a normal set of include files?

>If not, is there any interest in having access to such documentation?

>Specifically what I had in mind was a 'manual' organized according to
>include library, and indexed off function names.  A figure a typical entry
>would look like this:

[...stuff deleted...]

I think the idea is good and worthwhile, but would recommend some consideration
before plunging into the project. The C library is pretty huge, and thus
writing such a libc.info is a considerable task.

What is imporatnt is to assure one self that such a manual can do things that
tha manual system do not. I my opinion, if libc.info is just another format for
essentially the same information (perhaps with some crossreferencing), then
some sort of intelligent emacs interface to the man system would be a much
better investment of time and ressources.

For libc.info to be worth the effort, it should be like the elisp ref manual,
which contains tons of explanations and examples, and then we are talking a
major effort.

A man interface could deal with making of menus (based on for instance include
libraries), indexes and references, parsing up the information from the actual
manpages. The advantage of this would be that the system would go with whatever
OS you would be programming on, where writing an texinfo file would fix which
library we were talking about.

Such an interface may even exist already. One would for instance like to check
out the hyperbole package, which are supposed to deal with navigating through
massive amounts of information.



------------------------------------------------------------------------------
Christian Lynbech

DAIMI						office: R0.32   phone: 5034
University of Aarhus,DK-Denmark                 email: lynbech@daimi.aau.dk
------------------------------------------------------------------------------
			  EMACS, The One True Editor                       


Hit the philistines three times over the head with the Elisp reference manual.

                                        - petonic@hal.com (Michael A. Petonic)


Newsgroups: gnu.misc.discuss
From: fischer@iesd.auc.dk (Lars Peter Fischer)
Subject: Re: Dylan supported by GNU in future ?
Organization: Mathematics and Computer Science, Aalborg University
Date: 15 Dec 92 01:49:23


>>>>> "Martin" == Martin Cracauer (cracauer@wavehh.hanse.de)

Martin> I would like to know, if FSF will release a 'Dylan' implementation.
Martin> (Dylan is a language like CLOS, invented by Apple).

Any special reason you'd like Dylan over, day, Scheme or CLOS? Or
Emacs Lisp? Anything special Dylan will do, apart from blowing in the
wind?

Martin> I know, FSF don't like Apple, but isn't dylan 'free enough' to be
Martin> supported ? 

Well, write a GNU Dylan inetrpreter/compiler/system and donate it to
the FSF and things will look much more promising.

/Lars
--
Lars Fischer, fischer@iesd.auc.dk | It takes an uncommon mind to think of
CS Dept., Aalborg Univ., DENMARK. | these things.  -- Calvin
Newsgroups: gnu.misc.discuss
From: cracauer@wavehh.hanse.de (Martin Cracauer)
Subject: Re: Dylan supported by GNU in future ?
Organization: Private UUCP, Martin Cracauer, Norderstedt, Germany
Date: Wed, 16 Dec 92 12:39:45 GMT

fischer@iesd.auc.dk (Lars Peter Fischer) writes:


>>>>>> "Martin" == Martin Cracauer (cracauer@wavehh.hanse.de)

>Martin> I would like to know, if FSF will release a 'Dylan' implementation.
>Martin> (Dylan is a language like CLOS, invented by Apple).

>Any special reason you'd like Dylan over, day, Scheme or CLOS? Or
>Emacs Lisp? Anything special Dylan will do, apart from blowing in the
>wind?

You should take a look at 'Journal of Object Oriented Programming',
November/December issue, page 75.

There is an article about the advantages of dylan over CLOS by Denison
Bollay (the start of a little series, I think).


>Martin> I know, FSF don't like Apple, but isn't dylan 'free enough' to be
>Martin> supported ? 

>Well, write a GNU Dylan inetrpreter/compiler/system and donate it to
>the FSF and things will look much more promising.

If I could do this, I would'd ask for an implementation.

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer,    cracauer@wavehh.hanse.de
Waldstrasse 200, W-2000 Norderstedt, Germany
Tel.: +49 / 522 18 29, Fax.: +49 / 522 85 36
Newsgroups: gnu.misc.discuss,comp.sys.sun.misc
From: zoo@cygnus.com (david d 'zoo' zuhn)
Subject: Re: quality of GNU stuff vs. Sun OS stuff
Organization: Cygnus Support -- +1 415 903 1434
	<1992Dec7.234628.2941@fulcrum.oz.au> <1992Dec17.162638.26911@lut.ac.uk>
Date: Fri, 18 Dec 1992 03:11:02 GMT


    I raised this question with the Cygnus guys at the Sun User show
   in San Jose, and they assured me that if I build a product using
   GNU stuff, then I have to ship the src. *BUT* I do not have to ship
   the src to my application. This has been checked out by various
   legal eagles including those of a certain large (though getting smaller :-)
   computer company.

Given that I answered this question a few times at the SUG show, this may
be my answer that got munged somewhere along the line .  Let me clarify the
above.

If you build your product using GCC, or G++, or GAS, or whatever, this does
not force you to ship sources to anything (not gcc, not your product).

If you use the source code for gcc (or g++ or gas or emacs) in your
product, then you *do* need to ship the sources for your product.


If object code compiled from "copylefted" source code is linked into your
application, then your application falls under the version of the GPL
associated with the given source code (the normal GPL or the Library GPL).
This happens if you are, for example, writing a new front end for GCC, or
porting GAS to a new processor.  

Compiling a program with gcc does not alter the copyright status of that
program.  If your code is proprietary, or if it is PD, or anywhere in
between, you can still use gcc as a compiler.  

I hope this makes things a little more clear.  

  david d 'zoo' zuhn |    There is great disorder under the heavens,
    cygnus support   |         and the situation is excellent.
    zoo@cygnus.com   |    

Newsgroups: gnu.misc.discuss
From: jem@sunSITE.unc.edu (Jonathan Magid)
Subject: Re: Apple/Novell merger discussed
Organization: University of North Carolina, Chapel Hill
Date: Sat, 19 Dec 1992 08:02:33 GMT

In article <oiNZVB46w165w@mantis.co.uk> mathew <mathew@mantis.co.uk> writes:
>
>It's going to be technically difficult, not to mention unpopular.  When
>someone says "I'm running GCC on my 386 under Windows, and it's causing my
>DOS shells to crash", you're going to have to ask him exactly which DOS he
>bought, and explain that if he bought DR-DOS instead of MS-DOS or PC-DOS or
>Compaq DOS or whatever, you're going to refuse to help him.  You're going to
>have to ask him if he's running gcc on a Novell Netware fileserver.

Not to mention nonsensical.  Already the FSF does not actively port 
GNU software to MS-DOS platforms.  This is because that is not their focus
nor expertise.  As far as I can tell, a boycott of MS-DOS by the FSF would
have a nil effect on the FSF and the GNU project.

>
>Also, DR-DOS and Netware have a significant share of the market.  Such a
>boycott might actually hurt the FSF.
>

Significant share? Nobody sells more computers than Apple. Not even IBM.

But, despite this, I still don't see why a boycott of Novell products or
even the entire MS-DOS SLOPerating system would have any effect on the 
efforts of the FSF.  

MS-DOS != the x86 architecture.

"says the man with a very happy Linux system."
jem.
>
>mathew
>


-- 
Jonathan Magid     jem@sunSITE.unc.edu       sunSITE Administrator
Virtual pizza Delivery (tm)::faxed in 30 cycles or less or you get it
----------------------------------------FREE!!!-----------------------
From: edguer@ces.cwru.edu (Aydin Edguer)
Newsgroups: gnu.misc.discuss
Subject: Re: What is what in the GNUniverse?
Date: 18 Dec 1992 21:26:12 GMT
Organization: Computer Engineering and Science, Case Western Reserve University
Distribution: gnu
NNTP-Posting-Host: sentinel.ces.cwru.edu

In article <1992Dec18.085053.2588@nntp.hut.fi> jkp@cs.HUT.FI (Jyrki Kuoppala) writes:
>In article <1992Dec17.031048.20796@samba.oit.unc.edu>, jem@sunSITE (Jonathan Magid) writes:
>>Would you believe that I have already done this?
>
>Great!  At nic.funet.fi, we also had some feedback that the GNU
>software distribution is not documented very well, this will help at
>least some.

Great!  Would you believe that FSF has already done this?

If you check prep.ai.mit.edu in the /pub/gnu/GNUinfo directory, you will
find a file called FTP which describes much of the software in the archive
and how to obtain it.  You might also want to check the file named DISTRIB
which contains an order form for the GNU tapes and manuals.

Just a thought,
Aydin Edguer
From: xjam@cork.CS.Berkeley.EDU (The Crossjammer)
Newsgroups: gnu.misc.discuss
Subject: Re: Dylan supported by GNU in future ?
Date: 14 Dec 92 23:39:11
Organization: University of California, Berserkeley
	<FISCHER.92Dec15014923@thor.iesd.auc.dk>
	<1992Dec15.042930.23371@pasteur.Berkeley.EDU>
NNTP-Posting-Host: cork.cs.berkeley.edu
In-reply-to: johnm@cory.Berkeley.EDU's message of Tue, 15 Dec 1992 04:29:30 GMT

>>>>> "John" == John D. Mitchell <johnm@cory.Berkeley.EDU> writes:
	[stuff deleted]
  John> I believe that Dylan is trademarked by Apple.  That's why the free
  John> implementation of a language based on the Dylan Language Manual is called
  John> "Thomas" (or somesuch).  Dylan most certainly *not* a free language.  I
  John> recall some mention of certification of language implementations by Apple.

The Dylan *name* is trademarked just as UNIX is trademarked by AT&T. Apple
will have to actively protect to maintain it as such so you can expect some
litigation down the road. The validation suite is supposedly to ensure that
anyone using the name Dylan meets whatever specifications Apple sets out
for the language. You'll have to meet it to at least have a shot at using
the Dylan trademark.

Having said all that, you miss the point of Thomas. Anybody can get the
Dylan manual and implement a language that meets that specification. I
imagine that the validation suite will be publically available so you can
even see if your implementation is up to "snuff". But unless you go begging
to Apple you can't call it Dylan.

In my book that means the word "Dylan" isn't free, but the language is. At
least until Congress gets through mucking up the copyright and patent laws.

Thomas proves this point eminently. 

  John> I, for one, believe that Dylan is mostly just a tool for Apple to get
  John> people locked into their universe by promising all sorts of
  John> performance/abilities/etc. on hardware that has yet to be shown (Newton)
	[stuff deleted]
  John> The Dylan Language Manual ain't all that great and I don't find anything in
  John> the language that makes it worth locking myself to Apple and if you want a
  John> free version, somebody has already done it so why spend the time and effort?

The current Thomas implementation isn't exactly a speed burner, but people
can work on it, or write their own implementations, or whatever. But as far
as I can tell, Apple has no means by which to "lock" people into their
hardware using a language. People lock themselves in when they *must* have
the language, but don't want to go to the trouble of implementing it
themselves. 

Technically speaking, there are some interesting ideas in Dylan and a FSF
implementation would be another datapoint. But I doubt if there will be
many takers.




--
xjam@cork.Berkeley.EDU  	Fiiiive Thousand Boomin Watts...... -The JBeez

They can't come on and play me in prime time, 	    | Free Millipede coin op
Cause I know the time, cause I'm gettin' mine.	    | and House music at my
I get on the mix late in the night... -Public Enemy | place! Drop by sometime.
From: mstankus@oba.ucsd.edu (Mark Stankus)
Newsgroups: gnu.misc.discuss
Subject: Viewing .dvi files on a vt100 screen
Date: 20 Dec 92 21:07:01 GMT
Distribution: usa
Organization: Mathematics @ UCSD

I vaguely remember seeing somewhere a program which allows one to look
at the output of tex or latex on the screen of a vt100 terminal.
Maybe some .mil computer somewhere. Does anyone know where this 
program is?

Also, is there (or should there be) a public domain software 
availability FAQ?

Mark Stankus

-- 
mstankus
mstankus@oba
From: bruce@uxb.liv.ac.uk (Bruce Stephens)
Newsgroups: gnu.misc.discuss
Subject: Re: Concerns about the FSF and the GNU project
Date: 16 Dec 92 15:20:36 GMT
	<DREIER.92Dec10121615@phnom-penh.berkeley.edu>
	<Bz4pvD.545@mtholyoke.edu>
Organization: Centre for Mathematical Software Research, Univ. Liverpool, UK

>>>>> On 12 Dec 92 04:30:49 GMT, jbotz@mtholyoke.edu (Jurgen Botz) said:

> Well, I understand your point of view, but I believe that you are
> misguided.  There /is/ protection for your livelihood, in the form
> of source-code copyrights, which I believe (and apparently so does
> the LPF) is appropriate and adequate.

I think it's more accurate to say that the LPF is not concerned with
source-code copyrights, and so has no position on them.
--
Bruce              CMSR, University of Liverpool
Use PGP 2.1; make private email private!  
Key fingerprint =  E0 2E 17 55 56 C6 14 D2  03 E4 18 D7 A4 5B 86 20 
Newsgroups: gnu.misc.discuss
From: jimlynch@netcom.com (Jim Lynch)
Subject: Re: Concerns about the FSF and the GNU project
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 12 Dec 1992 07:19:42 GMT

P.S: Perhaps EFF can be of help since they are active in dealing with
lawmakers in the computer/privacy/freedom realm.
Newsgroups: gnu.misc.discuss,comp.sys.sgi
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: makefile for gnu make on SGI
Organization: Draper Laboratory
Date: Tue, 15 Dec 1992 21:17:00 GMT


On Tue, 25 Aug 1992 14:45:23 GMT fish@daacdev1.stx.com wrote:

>i need the Makefile for GNU make for an SGI platform - i have the
>Makefile but can't figure out what def's and flags to set
>
>i had to set -cckr CFLAG and i def'ed USG and USGr3 (isn't irix USGr4 though?)
>
>and then i ran into a problem with it finding alloca() in glob.c
>and then i found that i need to have -l mld for nlist and then
>i decided i better go to the net fer help.
>
>                        fish
>--
>John R. Vanderpool                INTERNET: fish@daacdev1.stx.com
>NASA/GSFC                         VOX: 301-513-1683
>Hughes/STX Corporation            FAX: 301-513-1608

I got it to work by also specifying -Dsparc.

It turns out that if sparc is defined, alloca.h is include'd.  Since
the sparc define is referenced only in 2 modules, and only for the
purpose of determining what to do about alloca, I found it safe to
specify -Dsparc in the makefile.  So, here are the changes I used:
while making gnu make 3.62 on an SGI box:

 22,24d21
 < # Following added by seb1525
 < prefix = /user1/people/seb1525/make
 <
 44,47c41
 < # *** Following line changed by seb1525 from
 < # defines =
 < # *** to
 < defines = -DUSG -DUSGr3 -Dsparc -cckr
 ---
 > defines =
 72,75c66
 < # *** following line changed by SEB1525 from
 < # LOADLIBES =
 < # *** to
 < LOADLIBES = -lmld -lPW
 ---
 > LOADLIBES =

Now all I need is for the sysadmin to create a group "kmem"... :-(

Btw, John, how did you come up with -cckr?  I wouldn't have even
tried it if not for you.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Newsgroups: gnu.misc.discuss
From: ohd@ornl.gov (OLIVE D H)
Subject: emacs for VMS, in search of binaries
Organization: Oak Ridge National Laboratory
Date: Thu, 17 Dec 1992 15:51:26 GMT

Is there a distribution of GNU Emacs for VMS in binary form?  Thanks...