John Emmas wrote: > This all suggests that there's something abnormal or unconventional about > Cygwin's make file. Has anyone seen this kind of behaviour before? It's a > new one on me. More importantly, is there any way I can force the project > to be built "normally" ?
Not sure what "normally" means in this context. I suggest you try: $ cygport jack-audio-connection-kit-0.109.2-1.cygport prep $ cygport jack-audio-connection-kit-0.109.2-1.cygport compile $ cygport jack-audio-connection-kit-0.109.2-1.cygport install $ cygport jack-audio-connection-kit-0.109.2-1.cygport package If this succeeds, this exactly reproduces the way that Yaakov build the source and binary packages. If you want to ./configure && make the package yourself, then you are on your own, and will have to deal with the issues that arise because cygwin isn't linux yourself. :-) You might look at the contents of the .cygport file, though, because I imagine Yaakov has already encountered and addressed these issues. Just from in a brief look at the .cygport file I notice there is a patch called "0.109.2-no-undefined.patch" which is certainly suggestive given the problem you are reporting (although I have no idea if it's actually relevant or not) :-) ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
