Re: [Chicken-users] Windows 10, mingw-w64, chicken 4.11, "invalid encoded numeric literal"

2016-08-23 Thread Dan Leslie
I think you should raise this bug in chicken-hackers; it sounds like
it's a platform issue not caught by the automated tests.

-Dan

On 2016-08-23 07:25 PM, Claude Marinier wrote:
> On Thu, 18 Aug 2016, Dan Leslie wrote:
>> I have used it successfully with MSys2 and Mingw-w64; the details are
> here:
>>
>> http://wiki.call-cc.org/msys2
> 
> Hi Dan,
> 
> I uninstalled MinGW-W64 & MSYS2, rebooted, and installed MSYS2 according
> to your instructions. The result is similar: the build works but check
> fails line this.
> 
> 
> Note: in toplevel procedure `doloop765':
>   (lolevel-tests.scm:184) in procedure call to `locative?', the
> predicate is called with an argument of type `locative' and will always
> return true
> ""gcc" "a.c" -o "a.o" -c  -fno-strict-aliasing -fwrapv
> -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os
> -IC:/msys64/home/claude/chicken-4.11.0/tests/..
> -IC:\\msys64\\usr\\local\\include\\chicken\\"
> rm a.c
> ""gcc" "a.o" -o "a.out" -Wl,--enable-auto-import
> -LC:/msys64/home/claude/chicken-4.11.0/tests/..
> -LC:\msys64\usr\local\lib\ -lchicken -lm -lws2_32"
> rm a.o
> [panic] invalid encoded numeric literal - execution terminated
> 
> make: *** [rules.make:663: check] Error 1
> 
> 
> I am running Windows 10, 64-bit on an old HP EliteBook.
> 
> Is there a known problem with gcc 6.1.0? Or are HP laptops quirky?
> 
> Thanks.
> 
> -- 
> Claude Marinier
> 
> 
> ___
> Chicken-users mailing list
> Chicken-users@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/chicken-users
> 



signature.asc
Description: OpenPGP digital signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Windows 10, mingw-w64, chicken 4.11, "invalid encoded numeric literal"

2016-08-23 Thread Claude Marinier
On Thu, 18 Aug 2016, Dan Leslie wrote:
> I have used it successfully with MSys2 and Mingw-w64; the details are
here:
>
> http://wiki.call-cc.org/msys2

Hi Dan,

I uninstalled MinGW-W64 & MSYS2, rebooted, and installed MSYS2 according to
your instructions. The result is similar: the build works but check fails
line this.


Note: in toplevel procedure `doloop765':
  (lolevel-tests.scm:184) in procedure call to `locative?', the predicate
is called with an argument of type `locative' and will always return true
""gcc" "a.c" -o "a.o" -c  -fno-strict-aliasing -fwrapv
-DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os
-IC:/msys64/home/claude/chicken-4.11.0/tests/..
-IC:\\msys64\\usr\\local\\include\\chicken\\"
rm a.c
""gcc" "a.o" -o "a.out" -Wl,--enable-auto-import
-LC:/msys64/home/claude/chicken-4.11.0/tests/.. -LC:\msys64\usr\local\lib\
-lchicken -lm -lws2_32"
rm a.o
[panic] invalid encoded numeric literal - execution terminated

make: *** [rules.make:663: check] Error 1


I am running Windows 10, 64-bit on an old HP EliteBook.

Is there a known problem with gcc 6.1.0? Or are HP laptops quirky?

Thanks.

-- 
Claude Marinier
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users