Date:	Mon, 20 Oct 1997 11:07:32 +1100
From:	Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject:	Re: Possibly make problem
In-reply-to:	<Pine.ULT.3.95.971015183832.11040C-100000@manes.vse.cz>
To:	Michal Mertl <xmerm05 AT manes DOT vse DOT cz>
Cc:	djgpp AT delorie DOT com
Message-id:	<199710192204.LAA07090@teleng1.tait.co.nz gatekeeper.tait.co.nz>
Organization:	Tait Electronics Limited
MIME-version:	1.0
Comments:	Authenticated sender is <billc AT blackmagic DOT tait DOT co DOT nz>

On 15 Oct 97 at 19:06, Michal Mertl wrote:

> I downloaded libsocket.0.5 and tried to compile it on my computer.
> Then I wanted to take a look on it as it's running so I wanted to
> compile it with -g. There is a file makefile.cfg in which there are
> only CC=gcc CFLAGS=-O2 -m486 .... and makefile just reads this in.
> So I added to CFLAGS -g. In process of building the library make
> changes dir to different source directories in which are makefiles
> which define CFLAGS += something (like -I..). In first level down
> directory it compiles the objects with -g but not in the second one.
> It seems that it knows in this directory only about CFLAGS are in
> local makefile (with +=).

It's a bug in the makefile in protoresolve.  Just put a "include 
../../Makfile.cfg" at the top.

> 
> I also have problems with lfns; I have read Eli wrote that DJGPP
> 2.02 will have lfn=y as default setting, but wan't it cause problems
> when it runs on plain dos? Is the djgpp long to short name
> conversion the same as W95's with NameNumericTail=0 ? 

Actually djgpp just passes the file name to dos and dos just 
truncates in the appropriate places.

> I get to this problem because to be able to try libsocket I had to
> enable lfns. If I set lfn=y I can't use info because I have my info
> files gzipped. It seems to me that gzip (from djgpp archives) never
> use lfns, am I correct, it always creates files with only one dot in
> name?

You CAN force it: try (eg) "gzip -S .gz tarfile.tar." (Note the 
trailing '.').


> Also I had some problems trying to use gzipped info files, e.g.
> files gcc.i1-gcc.i20 can't be compressed because gzip adds z to the
> end of the extension so gcc.i1 becomes gcc.i1z aswell as gcc.i11-19.
> So I had to rename the files to gcc1-20 and accordingly change the
> section filenames in gcc.inf file. Maybe in next gcc distibution
> they could be name gcc.1-20 but I know this extension is usually
> used for man pages.

Using the above methode (or renaming the file) would help a lot here.
Bill
--
Leave others their otherness.

- Raw text -