delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/05/14/02:52:09

Date: Mon, 14 May 2001 09:53:50 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Fileutils 4.0 and symlinks
In-Reply-To: <3AFEE27F.33C3BD51@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1010514095316.24166E@is>
MIME-Version: 1.0
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Sun, 13 May 2001, Richard Dawe wrote:

> I had a lot of trouble building Fileutils against DJGPP CVS. I found some
> rather strange problems. At first I tried to configure using:
> 
>     CFLAGS="-g -O2 -nostdinc -I$CVSDIR/include" \
>         LDFLAGS="-g -O2 -nostdlib -L$CVSDIR/lib" \
>         LIBS=-lc \
>         ./configure --disable-nls
> 
> (I realise that this would not include stubs, etc. in the link stage and
> that this is the wrong thing to do.) This caused the DOS box to GPF.

Did some DJGPP program GPFault?  If so, please post the crash message.

> In the end I settled on putting the include and library directories for
> the DJGPP CVS area ahead of the default ones.
> 
> CFLAGS="-g -O2 -I$CVSDIR/include" \
>     LDFLAGS="-g -O2 -L$CVSDIR/lib" \
>     ./configure --disable-nls
> 
> I still encountered some a weird problem. When I tried to link programs, I
> got errors about '-lgcc' or '-lc' not being found. This was strange
> because adding '-g' to the gcc line showed that the directories containing
> libgcc.a and libc.a were in the search path.

You could add -v to the compiler switches and then see where did it
try to look for files.  It's possible that it still looks at $DJDIR in
preference to some of the command-line switches that try to override
that; if so, it's important to know which switches are not honored.

> I think the problem was that there were too many open files, because
> another program generated the "too many files open" error. It turned
> out that restarting Windows solved the problem.

You can enlarge the maximum number of files by editing SYSTEM.INI; see
section 9.7 of the FAQ for details.  (Btw, this seems to be the _only_ 
way to control that on Windows ME.)

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019