Article View: gnu.gcc.help
Article #52791GCC 2.1 Documentation
From: GNU Mailing List Maintenance
Date: Fri, 22 May 1992 03:53
Date: Fri, 22 May 1992 03:53
334 lines
15919 bytes
15919 bytes
Return-Path: <MEHRDAD@gollum.dev.cardiff.ac.uk> Received: from mhs-relay.ac.uk by life.ai.mit.edu (4.1/AI-4.10) id AA17508; Thu, 21 May 92 06:38:21 EDT Message-Id: <9205211038.AA17508@life.ai.mit.edu> Received: from ean-relay.ac.uk by mhs-relay.ac.uk with SMTP inbound id <14197-0@mhs-relay.ac.uk>; Thu, 21 May 1992 11:37:40 +0100 Received: from gollum.dev.cardiff.ac.uk by Ean-Relay.AC.UK via Janet with NIFTP id aa03218; 21 May 92 12:24 BST Date: Thu, 21 May 92 11:30 BST From: GHASSEMPOORY <MEHRDAD@gollum.dev.cardiff.ac.uk> To: HELP-GCC <@ean-relay.ac.uk:HELP-GCC@PREP.AI.MIT.edu> Subject: GCC 2.1 Documentation Where can I find the full documentation on GCC 2.1 ? I am also looking for a copy of TeX utility for VMS. The version I have on my machine is a pain to install and does not work properly,(Bits missing, Syntax errors in DCL scripts etc.). Can someone please direct me to the right sources for VMS TeX Latex texinfo etc. Many Thanks You might want to ask the USENET newsgroup: comp.os.vms and/or comp.text.tex help-gcc is not the right place. If your machine isn't on USENET, I've appended information on how to post via mail. Be sure to say that you need replies by mail, because your machine isn't on USENET. enjoy -len PS: By the way, what do you think of look-and-feel lawsuits? ---------------------------------------------------------------------- Date: Sat, 17 Oct 87 19:40:30 PDT For your further edification, I enclose an article I wrote to send to BITNET people who want to know what USENET is, and how to get at it. Erik E. Fair ucbvax!fair fair@ucbarpa.berkeley.edu * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * USENET is a store & forward broadcast network of systems that all run the so-called "netnews" software. It can be thought of as a network of bulletin board systems. Or a distributed computer conferencing system. Whatever you call it, USENET has some differences from mailing lists. First, some terms: article - a USENET message (see ARPANET RFC1036 for the format standard. You'll probably want a look at ARPANET RFC822 too [the ARPANET Mail format standard]). newsgroup - a topic under which articles appear. This can be thought of as the separator in our distribution channel, or as the topic name. It is analogous to a mailing list name (or topic). They come in two flavors: unmoderated - anyone anywhere on the network can "post" an article to this newsgroup, and it will go *everywhere* that the newsgroup goes. moderated - only one person on the network can post articles to this newsgroup; anyone wishing to submit an article to this newsgroup has to Email the article to the "moderator" so that he can pass on the suitability of the article to that newsgroup. This mechanism is used to keep high volume newsgroups on topic, and to keep nonsense articles out. USENET distributes articles on a "pass it on" basis; when I post an article on ucbvax in a specific newsgroup, ucbvax will send the article by whatever means to our USENET neighbors who get that newsgroup. They, in turn, will send the article onward to their USENET neighbors who get that newsgroup, and so on, until my message has reached all the sites that get the newsgroup that I posted in. Since most of the USENET transmits articles by dial-up UUCP (UNIX to UNIX CoPy) at 1200 baud in the wee hours of the morning, this process can take up to a week to reach the fringes of the network, although most sites seem to get articles in the world-wide newsgroups within 48 hours of when they were posted. Creating a USENET newsgroup is different from setting up a mailing list in that you don't have to set up a distribution system for the articles; all you do is send out a control message which creates the newsgroup (subject, of course, to the approval of the network community at large). You've already set up the distribution system by setting up USENET in the first place, and a new newsgroup just subdivides the distribution channel one more time. If you're at a BITNET site, and you want to read the material that flows through the USENET, there are several ways of going about it. First and best is to install some implementation of netnews on your system, and ask someone else already on USENET to send a you a USENET feed (that is, all the articles in the list of newsgroups your site is interested in that he gets). There are two implementations of netnews for IBM VM/CMS, one from North Carolina State University (contact Bill Verity WHV@PSUVM), and one from Princeton University Computer Center (contact Irwin Tillman IRWIN@PUCC). The standard UNIX netnews implementation will run under DEC VAX/VMS, if you have the TWG Eunice UNIX emulator, which, unfortunately, costs real money. If you're a UNIX site on BITNET, you're all set (the standard netnews distribution will run on UNIX, of course). Second best is to look at the attached list of ARPANET mailing lists, which are gatewayed in some way to USENET newsgroups. This means that if you subscribe to one of the listed ARPANET mailing lists, you'll also see material coming from USENET. Please check with the folks at the BITNIC (BITNET Network Information Center) before trying to mail off to the ARPANET mailing list administrator. Given the traffic load on the BITNET ARPANET Gateway, it is likely that the mailing list you're interested in already has a BITNET distribution point, through LISTSERV or some equivalent, so that you can subscribe on BITNET, and not add to the load on the ARPANET Gateway. Unfortunately, not all the ARPANET mailing lists are gatewayed into USENET, and neither are all USENET newsgroups sent to the ARPANET community. If you are willing to take on BITNET distribution duties for a newsgroup that is not currently gatewayed into a mailing list, it might be possible for ucbvax to send you the articles in that newsgroup through the UCBJADE ARPANET Gateway. Send requests of this nature to usenet@ucbvax.berkeley.edu. Finally, if you just want to post something to a USENET newsgroup, ucbvax has a mail address for each newsgroup. Newsgroup names are of arbitrary length, with components no longer than 14 characters, separated by dots. Examples: comp.unix.wizards comp.sys.atari.st rec.arts.sf-lovers To form the mail address, translate all dots to dashes, and add an atsign and ucbvax's name. Examples: comp-unix-wizards@ucbvax.berkeley.edu comp-sys-atari-st@ucbvax.berkeley.edu rec-arts-sf-lovers@ucbvax.berkeley.edu Mailing a message to an address of that form with the appropriate newsgroup name will cause the message to be converted into a USENET article and posted to the named newsgroup. Note, however, that you MUST provide a "Subject:" header in the message. If you're trying to post a message to multiple newsgroups, there is a generic address, which if you send it a message with the right header information, will post the message to USENET. The address is post-usenet@ucbvax.berkeley.edu and there are two required header fields: Subject: (some appropriate description of your message) Newsgroups: (list of newsgroups separated by commas) Example: Subject: Some serious thoughts on Philosophy & Politics Newsgroups: talk.politics.misc,talk.philosophy.misc Note the absence of spaces between the newsgroup names. Whew! I hope this explains some of what USENET is about, and what we can and can't do about getting USENET into BITNET. I'm available at the addresses in my signature for answering questions, provided they don't require me to type in another magnum opus like this one to give a proper response (after all, I'm *busy*!!). USENET administrator for ucbvax, providing NNTP service with a :-) Erik E. Fair ucbvax!usenet usenet@ucbvax.berkeley.edu ---------------------------------------------------------------------- enjoy -len might want to ask the USENET newsgroup: If your machine isn't on USENET, I've appended information on how to post via mail. Be sure to say that you need replies by mail, because your machine isn't on USENET. enjoy -len PS: By the way, what do you think of look-and-feel lawsuits? ---------------------------------------------------------------------- Date: Sat, 17 Oct 87 19:40:30 PDT For your further edification, I enclose an article I wrote to send to BITNET people who want to know what USENET is, and how to get at it. Erik E. Fair ucbvax!fair fair@ucbarpa.berkeley.edu * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * USENET is a store & forward broadcast network of systems that all run the so-called "netnews" software. It can be thought of as a network of bulletin board systems. Or a distributed computer conferencing system. Whatever you call it, USENET has some differences from mailing lists. First, some terms: article - a USENET message (see ARPANET RFC1036 for the format standard. You'll probably want a look at ARPANET RFC822 too [the ARPANET Mail format standard]). newsgroup - a topic under which articles appear. This can be thought of as the separator in our distribution channel, or as the topic name. It is analogous to a mailing list name (or topic). They come in two flavors: unmoderated - anyone anywhere on the network can "post" an article to this newsgroup, and it will go *everywhere* that the newsgroup goes. moderated - only one person on the network can post articles to this newsgroup; anyone wishing to submit an article to this newsgroup has to Email the article to the "moderator" so that he can pass on the suitability of the article to that newsgroup. This mechanism is used to keep high volume newsgroups on topic, and to keep nonsense articles out. USENET distributes articles on a "pass it on" basis; when I post an article on ucbvax in a specific newsgroup, ucbvax will send the article by whatever means to our USENET neighbors who get that newsgroup. They, in turn, will send the article onward to their USENET neighbors who get that newsgroup, and so on, until my message has reached all the sites that get the newsgroup that I posted in. Since most of the USENET transmits articles by dial-up UUCP (UNIX to UNIX CoPy) at 1200 baud in the wee hours of the morning, this process can take up to a week to reach the fringes of the network, although most sites seem to get articles in the world-wide newsgroups within 48 hours of when they were posted. Creating a USENET newsgroup is different from setting up a mailing list in that you don't have to set up a distribution system for the articles; all you do is send out a control message which creates the newsgroup (subject, of course, to the approval of the network community at large). You've already set up the distribution system by setting up USENET in the first place, and a new newsgroup just subdivides the distribution channel one more time. If you're at a BITNET site, and you want to read the material that flows through the USENET, there are several ways of going about it. First and best is to install some implementation of netnews on your system, and ask someone else already on USENET to send a you a USENET feed (that is, all the articles in the list of newsgroups your site is interested in that he gets). There are two implementations of netnews for IBM VM/CMS, one from North Carolina State University (contact Bill Verity WHV@PSUVM), and one from Princeton University Computer Center (contact Irwin Tillman IRWIN@PUCC). The standard UNIX netnews implementation will run under DEC VAX/VMS, if you have the TWG Eunice UNIX emulator, which, unfortunately, costs real money. If you're a UNIX site on BITNET, you're all set (the standard netnews distribution will run on UNIX, of course). Second best is to look at the attached list of ARPANET mailing lists, which are gatewayed in some way to USENET newsgroups. This means that if you subscribe to one of the listed ARPANET mailing lists, you'll also see material coming from USENET. Please check with the folks at the BITNIC (BITNET Network Information Center) before trying to mail off to the ARPANET mailing list administrator. Given the traffic load on the BITNET ARPANET Gateway, it is likely that the mailing list you're interested in already has a BITNET distribution point, through LISTSERV or some equivalent, so that you can subscribe on BITNET, and not add to the load on the ARPANET Gateway. Unfortunately, not all the ARPANET mailing lists are gatewayed into USENET, and neither are all USENET newsgroups sent to the ARPANET community. If you are willing to take on BITNET distribution duties for a newsgroup that is not currently gatewayed into a mailing list, it might be possible for ucbvax to send you the articles in that newsgroup through the UCBJADE ARPANET Gateway. Send requests of this nature to usenet@ucbvax.berkeley.edu. Finally, if you just want to post something to a USENET newsgroup, ucbvax has a mail address for each newsgroup. Newsgroup names are of arbitrary length, with components no longer than 14 characters, separated by dots. Examples: comp.unix.wizards comp.sys.atari.st rec.arts.sf-lovers To form the mail address, translate all dots to dashes, and add an atsign and ucbvax's name. Examples: comp-unix-wizards@ucbvax.berkeley.edu comp-sys-atari-st@ucbvax.berkeley.edu rec-arts-sf-lovers@ucbvax.berkeley.edu Mailing a message to an address of that form with the appropriate newsgroup name will cause the message to be converted into a USENET article and posted to the named newsgroup. Note, however, that you MUST provide a "Subject:" header in the message. If you're trying to post a message to multiple newsgroups, there is a generic address, which if you send it a message with the right header information, will post the message to USENET. The address is post-usenet@ucbvax.berkeley.edu and there are two required header fields: Subject: (some appropriate description of your message) Newsgroups: (list of newsgroups separated by commas) Example: Subject: Some serious thoughts on Philosophy & Politics Newsgroups: talk.politics.misc,talk.philosophy.misc Note the absence of spaces between the newsgroup names. Whew! I hope this explains some of what USENET is about, and what we can and can't do about getting USENET into BITNET. I'm available at the addresses in my signature for answering questions, provided they don't require me to type in another magnum opus like this one to give a proper response (after all, I'm *busy*!!). USENET administrator for ucbvax, providing NNTP service with a :-) Erik E. Fair ucbvax!usenet usenet@ucbvax.berkeley.edu ---------------------------------------------------------------------- enjoy -len
Technical Details
Message-ID:
<9205220353.AA18995@raisin-nut>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ai.mit.edu!gnulistsReferences:
<9205211038.AA17508@life.ai.mit.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,c9cdab769696912a,start
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1992-05-21 18:00:12 PST
Newsgroups: gnu.gcc.help
Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ai.mit.edu!gnulists
From: gnulists@ai.mit.edu (GNU Mailing List Maintenance)
Subject: GCC 2.1 Documentation
Message-ID: <9205220353.AA18995@raisin-nut>
Sender: gnulists@ai.mit.edu
Reply-To: gnu@prep.ai.mit.edu
Organization: Project GNU, Free Software Foundation, 675 Mass. Ave., Cambridge,
MA 02139, USA +1 (617) 876-3296
References: <9205211038.AA17508@life.ai.mit.edu>
Distribution: gnu
Date: Fri, 22 May 1992 03:53:10 GMT
Lines: 335