On Thu, Jul 8, 2010 at 12:08 PM, Dave Korn wrote:
>> GCC 4.5.x branch and the 4.6.x branch ABI changed for win64, I'm trying
>> to avoid breaking user's self-built packages, so 4.5.0 and earlier is
>> out of the question. The current 4.3.4 is too old for mingw-w64.
>
> Going with 4.5.1 seems the
On Thu, Jul 8, 2010 at 8:25 AM, Charles Wilson
wrote:
> Well, the 64bit build of w32api provides over 2000 import libraries. The
> 32bit build has only about 225. Apparently this is because the .def
> files that each are generated from are maintained separately, vetted on
> each system, and their
Please leave 1.2.0-2 as previous.
wget -x -nH --cut-dirs=2 \
http://home.comcast.net/~david.rothenberger/cygwin/vorbis-tools/vorbis-tools-1.4.0-1-src.tar.bz2
\
http://home.comcast.net/~david.rothenberger/cygwin/vorbis-tools/vorbis-tools-1.4.0-1.tar.bz2
\
http://home.comcast.net/~david.ro
On 07/07/2010 02:47, JonY wrote:
> I'm working on the mingw-w64 GCC package on Cygwin. Normally, anything
> cygwin gets installed to /usr, however, with gcc 4.6, the locales data
> clashes.
> Yaakov suggested installing to /usr, but there are some problems with it.
>
> This makes GCC look in /us
On 06/07/2010 16:59, JonY wrote:
> On 7/6/2010 23:36, Charles Wilson wrote:
>> I found the problem: configure.ac is patched, but there's no mechanism
>> to ensure that the corresponding change to configure is included in the
>> patch (by default, cygport *assumes* you will run autoreconf, and so
>
On 05/07/2010 18:38, Charles Wilson wrote:
> However, the DLLs don't appear to be in the correct locations.
>
> opt/mingw64/bin/libobjc-2.dll
> opt/mingw64/bin32/libgcc_s_sjlj-1.dll
> opt/mingw64/bin64/libgcc_s_sjlj-1.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/libgfortran-3.dll
> opt/m
On 07/07/2010 02:47, JonY wrote:
> Hello,
>
> Can I ask what will be the next version of GCC be in Cygwin?
4.5.0-1 if I'm snappy. 4.5.1-1 if I'm not. I plan to get back to it at the
start of next week.
> This makes GCC look in /usr/mingw regardless of what the toolchain
> target is (anything
On 7/8/2010 3:22 AM, Corinna Vinschen wrote:
> On Jul 7 18:24, Christopher Faylor wrote:
>> [...]
>> Whether we use w32api in the cygwin tree or from somewhere else really
>> doesn't matter as long as Cygwin builds.
>
> That's why I'd like to know if Cygwin builds with w32api from the
> mingw64 p
On Jul 7 21:17, Charles Wilson wrote:
> On 7/7/2010 8:39 AM, Corinna Vinschen wrote:
> > On Jul 7 08:08, Charles Wilson wrote:
> >> I hope I have summed up the various competing proposals fairly, and that
> >> this edition of my patented War and Peace emails helps move the
> >> discussion along t
On Jul 7 18:24, Christopher Faylor wrote:
> On Wed, Jul 07, 2010 at 06:12:23PM -0400, Charles Wilson wrote:
> >On 7/7/2010 5:03 PM, Christopher Faylor wrote:
> >> or as a cross-compiler.
> >
> >Huh? Do you mean that we use cygwin's gcc as a code generator, and turn
> >off everything that makes i
10 matches
Mail list logo
