This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-2.95.1 configure patch for sco unix 3.2v4.0
- To: William Bader <william at nscs dot fast dot net>
- Subject: Re: gcc-2.95.1 configure patch for sco unix 3.2v4.0
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 29 Aug 1999 03:13:20 -0600
- cc: bug-gcc at gnu dot org
- Reply-To: law at cygnus dot com
In message <9908271759.aa20422@mip486.nscs.fast.net>you write:
> Fri Aug 27 14:27:50 1999 William Bader (william@nscs.fast.net)
>
> * configure: sco unix 3.2v4.0 supports long file names, so
> configure should not set truncate_target. When truncate_target=yes,
> target becomes i486-pc-sco3.2 while host remains i486-pc-sco3.2v4.0,
> and gcc thinks that it is cross-compiling. (I realize that configure
> is built from configure.in, but I don't think that I have the tools
> to rebuild it on my system.)
>
> --- gcc-2.95.1/gcc/configure- Mon Aug 16 05:16:39 1999
> +++ gcc-2.95.1/gcc/configure Fri Aug 27 14:27:50 1999
> @@ -3729,7 +3729,10 @@
> tmake_file=i386/t-crtstuff
> extra_parts="crtbegin.o crtend.o"
> fi
> - truncate_target=yes
> + # The default EAFS filesystem supports long file names.
> + # Truncating the target makes $host != $target which
> + # makes gcc think it is doing a cross-compile.
> + # truncate_target=yes
> ;;
> i[34567]86-*-sco*) # 80386 running SCO system
> xm_file=i386/xm-sco.h
First, do not send diffs to generated files. Always send diffs relative to the
source file (in this case configure.in).
Second, a ChangeLog entry just notes what changed, not why. If the "why" is
complicated enough that you feel the need to explain it do so as comments
in the source.
ie:
* configure.in (i[34567]86-*-sco3.2v4*): Target does not truncate
filenames.
* configure: Rebuilt.
I've fixed up your patch and installed.
Thanks,
jeff