>> Right. I applied it the traditional way. > > Ah, you have to understand this about cygport patches: they only contain > patches for the source files, not the autogenerated ones. So they have > patches for e.g. Makefile.am, configure.ac; but not for configure or even > Makefile.in. It's vitally necessary to autoreconf after applying a patch that > you get from a cygport-based package. >
OK, that's it. >> As a want to come a hybrid of Cygwin and Gentoos Emerge installer, I >> rather have to figure out one of those hidden ways. > > Well, if you're doing it in a POSIX-compatible environment, you should be > able to run cygport - with maybe a few minor bugs cropping up, but basically > it's just a bunch of shell scripts that invoke the autotools, gcc and > binutils, so they should be relatively easy to port to any similar > environment. > > I did once try running cygport on a linux box (with a cross-compiler). I > don't remember exactly what went wrong, it didn't work directly out of the > box, but it shouldn't be hard to fix. > This sounds like a real alternative. Very interesting! It would definitly be worth it's own project group. Then it would be a choice. Al -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
