Date:	Tue, 17 Jun 2003 12:19:34 +0200
Message-Id:	<200306171019.MAA19703@acp3bf.physik.rwth-aachen.de>
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
To:	djgpp AT delorie DOT com
Subject:	Re: Makefile Help
X-Newsgroups:	comp.os.msdos.djgpp
In-Reply-To:	<bcm2d0$6c6$1@blue.rahul.net>
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

In article <bcm2d0$6c6$1 AT blue DOT rahul DOT net> you wrote:
> --- filefn.cpp.ori	2003-05-15 01:37:58.000000000 -0700
> +++ filefn.cpp	2003-06-16 20:03:28.000000000 -0700
> @@ -173,6 +173,7 @@
>    return(1457664);
>  #elif defined(_EMX)
>    int Drive=(!isalpha(FileName[0]) || FileName[1]!=':') ? 0:toupper(FileName[0])-'A'+1;
> +#ifndef _DJGPP
>    if (_osmode == OS2_MODE)
>    {
>      FSALLOCATE fsa;

This change looks like a red herring, to me.  this is inside an #if
defined(_EMX) block, already, so DJGPP will never be defined.  Or
rather: if it were, something else, elsewhere in the source, is badly
mixed up.

And while at it: the source sould always test for actual predefined
platform macros, like __DJGPP__, not self-defined ones like _DJGPP,
which it is forbidden to define on its own by the C standard.

>  # Linux using GCC
> -CXX=g++
> -CXXFLAGS=-O2
> -DEFINES=-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> +CXX=gpp
> +CXXFLAGS=-O2 -W -Wall
> +DEFINES=-D_FILE_OFFSET_BITS=64

_FILE_OFFSET_BITS may also be a bad idea.  Better make sure the source
code compiled doesn't refer to it.

> @@ -290,6 +290,7 @@
>      strcpy(RARFileName,FullName);
>      return;
>    }
> +#ifndef _DJGPP

This looks like the same red herring from above, again.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -