Date: Sun, 5 Dec 1999 12:03:37 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp AT delorie DOT com cc: serenkov AT gsu DOT unibel DOT by Subject: Re: Some questions In-Reply-To: <944167327@p25.f21.n452.z2.FIDOnet.ftn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, 2 Dec 1999, Alexey Gaev wrote: > About info.exe: it seems to work, shows some topics, but when I press 'h' to > start tutorial (I REALLY love tutorials ;), it shows me the message at the > bottom of my screen about ENOENT. What file does it miss? It needs the file `info.info'. This file comes with the txi312b.zip distribution and should already be in your `info' subdirectory. Perhaps you have some installation snafu; see section 6.9 of the DJGPP FAQ list. > Second question: Is there any kind of Language Reference in the package? For > example, I want to know if I can tell the compiler to pass values to > functions in specified registers, like I did in WATCOM: #pragma aux > MyFunc parm [eax]... Type "info gcc invoking submodel i386" and read the description of the option -mregparm. Warning: if you compile some of your sources with this switch, you cannot call library functions from those source files! A better way of achieving the same goal is to use the GCC inline assembly facilities; see section 18.13 of the FAQ for more details. > Third: is there any way to link programs on DJGPP with .obj files, created, > for example, by TASM? No; see section 17.5 of the DJGPP FAQ list. > Fourth: where to search for djgpp.env file format explanation? Type "info know hidden djgpp" and read there. > I think I should change it to add some options for compiler so I > don't have to type them every now and then. Please don't do that! DJGPP.ENV is very central to the smooth operation of the package, and it is very easy to break your installation by editing it. You should NOT need to edit DJGPP.ENV at all; it is already set in a way that allows to solve almost every problem without touching DJGPP.ENV. If you have specific problems that you think require you to edit DJGPP.ENV, please describe those problems here. It is almost certain those problems can be solved by other means. > And, finally: don't you > think that 104 Kb for "Hello, world" program, even with debug > information, is too much? ;) No, we don't; and neither should you. See section 8.13 of the DJGPP FAQ list for the explanation and remedies. > WATCOM C gives me 31 Kb in the same conditions (of course, not > counting dos4gw.exe ;). Why don't you count dos4gw.exe? Please *do* count it, if you want the comparison be fair. Anyway, using the simple techniques described in section 8.13 of the FAQ, I can make "Hello world" be 28KB on disk. > Please answer to serenkov AT gsu DOT unibel DOT by. Please in the future make the small effort to include your correct address in the message. Some of us reply to way too many message, and cannot afford manually editing the headers.