Hi Yaakov, and everybody, First, Happy Christmas and New Year!
Here are a few mods which I found useful when building GCC-4. They're
diff'd against the 1.5-distro version of cygport that I've been working with
but I could port them up to SVN if they're OK; I see that cygconf() has moved
to the autotools class file.
First up: how about adding "-p" to the diff options? It makes the
generated source patches more easily human readable.
Secondly: I need to ship a patched ltmain.sh with GCC-4, so I'd like it to
be added to the section where automake and libtool get a smaller set of
default_excludes. This should be uncontroversial.
Thirdly (and fourthly, but I don't have a patch for it yet): GCC-4 is a bit
of a pain. Most of the subdirectories are configured with autoconf-2.59, but
one uses 2.61. The directories that use 2.59 absolutely require 2.59, which
is no longer part of the cygwin distro; I haven't investigated if the one that
uses 2.61 would be ok with 2.59.
This has two implications: firstly, that there is no single set of
command-line options for specifying the datadir that can work correctly in all
subdirs, and secondly that autoreconf() isn't an easy solution to the problem.
The third patch addresses the first part of this, by allowing me to reduce
the set of prefix-related options passed by cygconf() to the top-level
configure, allowing the sub-configures to correctly default whatever they
respectively call the particular options. It's a bit ugly, and I'm not wedded
to the particular way of doing it, but it seems a shame to copy and paste the
whole of cygconf into my cygport script just to override a couple of lines.
The fourth patch, which I haven't written yet before discussing it here,
would apply to __pkg_diff(), and would allow me to prevent "configure" and
"Makefile.in" from being added to the default_excludes list. This would let
me ship with patched versions of the generated files meaning that users could
build the whole thing without needing autotools or having to worry about
rolling back their autoconf using the Cygwin time machine or similar. Unless
you had a preferred way of doing it, I'd probably just add another variable
definition and test it with ifdef, as in the third patch, but I'll wait to see
what you have to say about all these before doing any more hacking.
cheers,
DaveK
cygport-gcc-support-patch-1.diff
Description: Binary data
cygport-gcc-support-patch-2.diff
Description: Binary data
cygport-gcc-support-patch-3.diff
Description: Binary data
------------------------------------------------------------------------------
_______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
