-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dave Korn wrote: > The only patches I have are the ones attached to that post; the cygport file > as I currently have it is attached here for reference. (Or did you want the > src.patch?)
Sorry for not being clear; I meant the src.patch(es). > Effectively, GCC is *also* an original source of this file! Not really, it just uses a forked version that we need to deal with. > GCC uses a forked libtool and ltmain.sh is not autogenerated. Hence I need > to ship it, and if I want to modify it, I have to make sure the diffs end up > in the src.patch. Oh, a forked libtool. Lovely. Please tell me they're not still using some ancient version too. > <shrugs> It is what it is. fixincludes/configure was accidentally > regenerated with the wrong version just before the 4.3 branch was cut. The > next time it was regenerated it got fixed back to 2.59 on mainline, but by > then it was too late for 4.3 branch. > > Quite possibly so, which is why I sent the patch for discussion. Maybe I > should just reconfigure the fixincludes dir with 2.59 and then it won't > matter, but I can't do that unless I can ship the diffs to the generated > configure file. So I guess that if I can have the facility proposed in the > as-yet-hypothetical fourth patch, I wouldn't need the horrible kludge in the > third patch. If it will build with 2.59, then this may be a bit easier. > Nope, I haven't had any need to do that so far as I'm only modifying > configure.ac and Makefile.am files to any extent. None of the other excludes > have affected me (apart from the previously mentioned ltmain.sh). OK. > I figure that autoconf isn't going to be necessary for most people who want > to build the package from source because they mostly won't be patching the > sources at all, and of those who do, most of them aren't likely to be patching > the configure/build system. Your .cygport shows only two directories need autoconf; they both need 2.59? > So, I've attached my working .cygport as it is at the moment. As you can > see in src_compile(), I'm obliged to autoconf a couple of dirs and just hope > it works for the user. If I could skip this step it wouldn't matter what > version of autoconf the user had installed (unless of course they wanted to > patch configure.ac themselves). As you say, automake doesn't have this > problem, since the Cygwin distro includes all versions, it's just that > __pkg_diff(), in excluding generated files, assumes that there's going to be > an autoreconf step during the build stage, and for GCC that can't easily be > the case. I think the solution will depend on the extent of the patches to the two configures. Yaakov Cygwin Ports -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkldeB8ACgkQpiWmPGlmQSM5oACcC29AU1mdmc9f4Kv34/G+CRW8 sjEAoJ8Us0uRbWO8siPMbm4LMilqJNIy =i0rX -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
