Dave Korn wrote:
>> I've just updated my repo and will schedule a nightly build
>> of trunk with configure settings taken from the bundled gcc4
>> compiler from Cygwin pack in order to see what will happen.
>
> That's the simplest way to guarantee compatibility.
And now the compiler works correc
On 09/06/2010 17:31, Piotr Wyderski wrote:
>> Are you sure you're picking up the newest version of cyggcc_s-1.dll
>> (and all the other language runtimes) that got built with the compiler,
>> rather than the standard system one(s)?
>
> How can I check that?
Well, verifying your path is correct
Dave,
> Are you sure you're picking up the newest version of cyggcc_s-1.dll
> (and all the other language runtimes) that got built with the compiler,
> rather than the standard system one(s)?
How can I check that?
> You did a full "make install" and put the new $prefix/bin (if not
> using the st
On 09/06/2010 17:10, Dave Korn wrote:
Oh, and an afterthought:
> On 09/06/2010 11:51, Piotr Wyderski wrote:
>> I have a problem with recent builds of GCC4.6 (trunk)
>> on Cygwin 1.7. The compiler itself builds correctly, but
>> when I run it on even the simplest input, e.g.
>>
>>gcc in.c -o
On 09/06/2010 11:51, Piotr Wyderski wrote:
> I have a problem with recent builds of GCC4.6 (trunk)
> on Cygwin 1.7. The compiler itself builds correctly, but
> when I run it on even the simplest input, e.g.
>
>gcc in.c -o a.exe
>
> with in.c = int main() {}, no executable file is created.
> N
Wojciech Meyer wrote:
> Maybe a mismatched cygwin1.dll. Do you have the right version of
> cygwin1.dll on path? e.g the one against which gcc was compiled?.
> Cygwin fails silently to execute the image in case of a mismatched
> dll.
I am not 100% sure that my Cygwin installation is OK, as
it has
On Wed, Jun 9, 2010 at 11:51 AM, Piotr Wyderski
wrote:
> I have a problem with recent builds of GCC4.6 (trunk)
> on Cygwin 1.7. The compiler itself builds correctly, but
> when I run it on even the simplest input, e.g.
>
> gcc in.c -o a.exe
>
> with in.c = int main() {}, no executable file is cr
I have a problem with recent builds of GCC4.6 (trunk)
on Cygwin 1.7. The compiler itself builds correctly, but
when I run it on even the simplest input, e.g.
gcc in.c -o a.exe
with in.c = int main() {}, no executable file is created.
No oputput is created even with the -S and -E options.
The
