On Sun, Aug 19, 2012 at 3:46 PM, Juan Jose Garcia-Ripoll
wrote:
> On Sun, Aug 19, 2012 at 11:56 AM, Gabriel Dos Reis
> wrote:
>>
>> Unfortunately, it failed to execute properly, apparently for the
>> same reasons as 2 years ago.
>
>
> There were not so many things to fix after all:
>
> * the typo
On Sun, Aug 19, 2012 at 10:46 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@gmail.com> wrote:
> With all these, ECL seems to build fine on mingw32.
I should have chosen my words with greater care :-) "fine" is not
appropriate, for there are some regressions compared to other ports when
run
On Sun, Aug 19, 2012 at 11:56 AM, Gabriel Dos Reis <
g...@integrable-solutions.net> wrote:
> Unfortunately, it failed to execute properly, apparently for the
> same reasons as 2 years ago.
>
There were not so many things to fix after all:
* the typo you found
* missing :win64 keyword
* typo in _
On Sun, Aug 19, 2012 at 2:27 PM, Juan Jose Garcia-Ripoll
wrote:
> On Sun, Aug 19, 2012 at 9:14 PM, Gabriel Dos Reis
> wrote:
>>
>> No, it wasn't. Browse to the source code for number.d
>>
>>
>> http://ecls.cvs.sourceforge.net/viewvc/ecls/ecl/src/c/number.d?revision=1.102&view=markup
>>
>> Have a
On Sun, Aug 19, 2012 at 9:14 PM, Gabriel Dos Reis <
g...@integrable-solutions.net> wrote:
> No, it wasn't. Browse to the source code for number.d
>
>
> http://ecls.cvs.sourceforge.net/viewvc/ecls/ecl/src/c/number.d?revision=1.102&view=markup
>
> Have a look at lines 308, 326, and 394.
Ok, it se
On Sun, Aug 19, 2012 at 1:44 PM, Juan Jose Garcia-Ripoll
wrote:
> On Sun, Aug 19, 2012 at 11:56 AM, Gabriel Dos Reis
> wrote:
>>
>> After modifying c/symbols_list.h and c/symbols_list2.h to include
>> a definition for :WIN64,
>
>
> I uploaded a fix for this
OK.
>> the build failed again because
On Sun, Aug 19, 2012 at 11:56 AM, Gabriel Dos Reis <
g...@integrable-solutions.net> wrote:
> After modifying c/symbols_list.h and c/symbols_list2.h to include
> a definition for :WIN64,
>
I uploaded a fix for this
> the build failed again because
> the function ecl_make_ulong_long was mistyped
On Sun, Aug 19, 2012 at 8:37 AM, Juan Jose Garcia-Ripoll
wrote:
> I am a bit lost with the mingw64 toolchain, with so may different tarballs
> and options. I must admit I have never managed to get it up and running.
> What do I have to do to use it?
Indeed, there are probably too many options aro
I am a bit lost with the mingw64 toolchain, with so may different tarballs
and options. I must admit I have never managed to get it up and running.
What do I have to do to use it?
On Sun, Aug 19, 2012 at 11:56 AM, Gabriel Dos Reis <
g...@integrable-solutions.net> wrote:
> * fresh check out of CVS
* fresh check out of CVS trunk
* configure option: --build=x86_64-w64-mingw64
First failure appeared while compiling c/ffi.d.
Reason: the symbol :WIN64 appears not to be defined anywhere
so that the '@' translation could do something meaningful. Instead
it replaced it with unknown, which of cour
10 matches
Mail list logo
