2010/6/5 Ruben Van Boxem <[email protected]>

> Thank you for fixing the underscore business.
> There is a new problem though:
> The 1.0.0a release will not complete the build because configure does not
> copy (several?) files to where they should be. One example is "md2test.c".
> When make gets there, it is an empty file, and ld produces an error. I can
> say 100% sure that the 1.0.0-STABLE-20100331 snapshot does not have this
> problem, but can't pinpoint it after that. The underscoring fix has nothing
> to do with it (I tried an old underscored mingw-w64 toolchain on the 1.0.0a
> release without the underscore fix in the perl script, and it has exactly
> the same problem.
>
> I hope this can be solved soon. Thanks
>
> 2010/6/2 Andy Polyakov via RT <[email protected]>
>
> According to our records, your request has been resolved. If you have any
>> further questions or concerns, please respond to this message.
>>
>
> This is becoming a bad habit, but after some more testing, the above
problem only occurs when using MSYS+1.0.0a release. It does not occur when
using linux to crosscompile, or in any of the daily stable snapshots
available. I will await the next release to see if there is any issue
remaining.


2010/6/5 Ruben Van Boxem <[email protected]>
Thank you for fixing the underscore business.
There is a new problem though:
The 1.0.0a release will not complete the build because configure does not copy (several?) files to where they should be. One example is "md2test.c". When make gets there, it is an empty file, and ld produces an error. I can say 100% sure that the 1.0.0-STABLE-20100331 snapshot does not have this problem, but can't pinpoint it after that. The underscoring fix has nothing to do with it (I tried an old underscored mingw-w64 toolchain on the 1.0.0a release without the underscore fix in the perl script, and it has exactly the same problem.

I hope this can be solved soon. Thanks

2010/6/2 Andy Polyakov via RT <[email protected]>

According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.

This is becoming a bad habit, but after some more testing, the above problem only occurs when using MSYS+1.0.0a release. It does not occur when using linux to crosscompile, or in any of the daily stable snapshots available. I will await the next release to see if there is any issue remaining.

Reply via email to