Nabble - Gnu - Prolog

Re: Minor setup packaging error in setup-gprolog-1.3.1.exe.

2009-12-05T09:58:19Z

Thanks for this report. Will be fixed in next version.

Daniel

L Anderson a écrit :

> I downloaded and installed 'setup-gprolog-1.3.1.exe' onto my 'E:'
> drive into folder 'E:/GNU-Prolog'. The setup process creates:
>
> GNU Prolog.lnk -> E:/GNU-Prolog/bin/gprolog.exe
> Help.lnk -> E:/GNU-Prolog/doc/manual.chm <<<<<=============******
> Html Manual.lnk -> E:/GNU-Prolog/doc/html_node/index.html
> The GNU Prolog Web Site.lnk -> E:/GNU-Prolog/gprolog.url
> Uninstall GNU Prolog.lnk -> E:/GNU-Prolog/unins000.exe
>
> in 'C:\Documents and Settings\All Users\Start Menu\Programs\GNU Prolog'.
>
> There is no 'manual.chm' in 'E:/GNU-Prolog/doc/'; but there is a
> 'gprolog.chm'. This appears to be a setup packaging error where
>
> 'Help.lnk -> E:/GNU-Prolog/doc/gprolog.chm'<<<<<=============******
>
> is probably what is wanted. The other links work as expected.
>
> Regards,
>
> Lowell Anderson
>
> ----[cut-patch, perhaps]-----
> ->diff -up gp-setup.iss.in gp-setup.iss-1.in
> --- gp-setup.iss.in 2009-01-23 03:15:02.000000000 -0800
> +++ gp-setup.iss-1.in 2009-12-02 14:01:28.937500000 -0800
> @@ -41,7 +41,7 @@ Filename: "{app}\gprolog.url"; Section:
>
> [Icons]
> Name: "{group}\GNU Prolog"; Filename: "{app}\bin\gprolog.exe"
> -Name: "{group}\Help"; Filename: "{app}\doc\manual.chm"
> +Name: "{group}\Help"; Filename: "{app}\doc\gprolog.chm"
> Name: "{group}\Html Manual"; Filename: "{app}\doc\html_node\index.html"
> Name: "{group}\The GNU Prolog Web Site"; Filename: "{app}\gprolog.url"
> Name: "{group}\Uninstall GNU Prolog"; Filename: "{uninstallexe}"
>
>
>
> _______________________________________________
> Bug-prolog mailing list
> Bug-prolog@...
> http://lists.gnu.org/mailman/listinfo/bug-prolog
>

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Re: nth in latest unstable version

2009-12-04T10:02:59Z

Hi Daniel
OK, that fixed it, but I have another one...in the following examples
the variables A,B,C,D,E are not being bound to the list elements when
they are matched. They are still free when the call exits.

$ gprolog
GNU Prolog 1.3.2
By Daniel Diaz
Copyright (C) 1999-2009 Daniel Diaz
| ?- append(Z,[A,B,C,D,E],[48,48,48,48,48,48,48,48,49]).

Z = [48,48,48,48]

yes
| ?- trace.
The debugger will first creep -- showing everything (trace)

yes
{trace}
| ?- append(Z,[A,B,C,D,E],[48,48,48,48,48,48,48,48,49]).
1 1 Call:
append(_16,[_17,_18,_19,_20,_21],[48,48,48,48,48,48,48,48,...]) ?
1 1 Exit:
append([48,48,48,48],[_17,_18,_19,_20,_21],[48,48,48,48,48,48,48,48,...]) ?

Z = [48,48,48,48]

yes
{trace}

...also I am having to make it --without-c-flags because if I allow the
build system to use -O3 then I get an error during build:
. . . .
make[1]: Entering directory `/home/jaspert/Build/gprolog-1.3.2/src/Fd2C'
gplc -c --fast-math fd2c.pl

Fatal Error: Segmentation Violation
compilation failed
make[1]: *** [fd2c.o] Error 1
make[1]: Leaving directory `/home/jaspert/Build/gprolog-1.3.2/src/Fd2C'
make: *** [all] Error 1

Thanks for your help
--Jasper

Daniel Diaz wrote:

> Oups...
>
> fixed (I hope :-)) in last snapshot:
> http://gprolog.univ-paris1.fr/unstable/gprolog-20091204.tgz
>
> Daniel
>
>
> Jasper Taylor a écrit :
>> nth and nth0 do not work when the position is a number but the list
>> is free. Examples (on Ubuntu but MacOS is same I think):
>>
>> jaspert@spacehopper:~$ gprolog
>> GNU Prolog 1.3.2
>> By Daniel Diaz
>> Copyright (C) 1999-2009 Daniel Diaz
>> | ?- nth(1,B,c).
>>
>> no
>> | ?- nth0(0,B,c).
>>
>> no
>>
>> Working examples:
>>
>> | ?- nth(A,B,c).
>>
>> A = 1
>> B = [c|_] ? ;
>>
>> A = 2
>> B = [_,c|_] ? ;
>>
>> A = 3
>> B = [_,_,c|_] ?
>>
>> yes
>> | ?- nth0(A,B,c).
>>
>> A = 0
>> B = [c|_] ?
>>
>> yes
>>
>> Cheers
>> --Jasper
>>
>>
>>
>> _______________________________________________
>> Bug-prolog mailing list
>> Bug-prolog@...
>> http://lists.gnu.org/mailman/listinfo/bug-prolog
>>
>
>

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Re: nth in latest unstable version

2009-12-04T09:10:19Z

Oups...

fixed (I hope :-)) in last snapshot:
http://gprolog.univ-paris1.fr/unstable/gprolog-20091204.tgz

Daniel

Jasper Taylor a écrit :

> nth and nth0 do not work when the position is a number but the list is
> free. Examples (on Ubuntu but MacOS is same I think):
>
> jaspert@spacehopper:~$ gprolog
> GNU Prolog 1.3.2
> By Daniel Diaz
> Copyright (C) 1999-2009 Daniel Diaz
> | ?- nth(1,B,c).
>
> no
> | ?- nth0(0,B,c).
>
> no
>
> Working examples:
>
> | ?- nth(A,B,c).
>
> A = 1
> B = [c|_] ? ;
>
> A = 2
> B = [_,c|_] ? ;
>
> A = 3
> B = [_,_,c|_] ?
>
> yes
> | ?- nth0(A,B,c).
>
> A = 0
> B = [c|_] ?
>
> yes
>
> Cheers
> --Jasper
>
>
>
> _______________________________________________
> Bug-prolog mailing list
> Bug-prolog@...
> http://lists.gnu.org/mailman/listinfo/bug-prolog
>

--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

nth in latest unstable version

2009-12-04T08:52:13Z

nth and nth0 do not work when the position is a number but the list is
free. Examples (on Ubuntu but MacOS is same I think):

jaspert@spacehopper:~$ gprolog
GNU Prolog 1.3.2
By Daniel Diaz
Copyright (C) 1999-2009 Daniel Diaz
| ?- nth(1,B,c).

no
| ?- nth0(0,B,c).

no

Working examples:

| ?- nth(A,B,c).

A = 1
B = [c|_] ? ;

A = 2
B = [_,c|_] ? ;

A = 3
B = [_,_,c|_] ?

yes
| ?- nth0(A,B,c).

A = 0
B = [c|_] ?

yes

Cheers
--Jasper

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Logtalk 2.38.0 released

2009-12-03T18:06:56Z

Hi,

Logtalk 2.38.0 is now available for downloading:

http://logtalk.org/

Logtalk is an object-oriented logic programming language that can use most Prolog implementations as a back-end compiler. As a multi-paradigm language, it includes support for both prototypes and classes, protocols (interfaces), component-based programming through category-based composition, event-driven programming, and high-level multi-threading programming.

Noteworthy changes since the previous major release (2.37.0) are:

* Support for lambda expressions.
* Support for object and category multifile predicates and grammar rules.
* Improved compiler error and warning reporting.
* New and improved compiler flags.
* Compatibility updates for most back-end Prolog compilers.
* Improved installation and Prolog integration scripts.
* Improved installers.
* Improved compatibility with Prolog module libraries.
* Improved support for text editors and syntax highlighters.
* Improved compilation of Prolog modules as objects.
* Improved conditional compilation support.
* New programming examples.
* Improved libraries.
* Fixes for all know bugs.
* Minor performance improvements.

For details and a complete list of changes, please consult the release notes:

http://logtalk.org/releasenotes.html

Happy logtalking!

Paulo

-----------------------------------------------------------------
Paulo Jorge Lopes de Moura, PhD
Assistant Professor
Dep. of Computer Science, University of Beira Interior
6201-001 Covilhã, Portugal

Office 3.18 Ext. 3276
Phone: +351 275319891 Fax: +351 275319899
Email: <mailto:pmoura@...>

Home page: <http://www.di.ubi.pt/~pmoura>
Research: <http://logtalk.org/> Blog: <http://blog.logtalk.org/>
-----------------------------------------------------------------

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog

From forum: Gnu - Prolog - Users

Re: Snow Leopard woes contd

2009-12-03T08:39:44Z

On 2009/12/03, at 16:19, Jasper Taylor wrote:

> Hi Daniel etc
> I am still having trouble building under Snow Leopard. I guessed the version gprolog-20091123.tgz might include your fix to this problem, but when I try to build it the configure script runs OK but when I try to make I get:
> jasper-taylors-macbook:src jaspert$ make
> (cd EnginePl; make config)
> gcc -m32 -O3 -fomit-frame-pointer -o pl_config pl_config.c
> ./pl_config
> Bad Value of WORD_SIZE - should be 32
> make[1]: *** [wam_regs.h] Error 1
> make: *** [all] Error 2
> Any suggestions?

Try running "autoconf" in the "src" directory before running "configure".

Cheers,

Paulo

-----------------------------------------------------------------
Paulo Jorge Lopes de Moura, PhD
Assistant Professor
Dep. of Computer Science, University of Beira Interior
6201-001 Covilhã, Portugal

Office 3.18 Ext. 3276
Phone: +351 275319891 Fax: +351 275319899
Email: <mailto:pmoura@...>

Home page: <http://www.di.ubi.pt/~pmoura>
Research: <http://logtalk.org/> Blog: <http://blog.logtalk.org/>
-----------------------------------------------------------------

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Snow Leopard woes contd

2009-12-03T08:19:50Z

Hi Daniel etc
I am still having trouble building under Snow Leopard. I guessed the
version gprolog-20091123.tgz might include your fix to this problem, but
when I try to build it the configure script runs OK but when I try to
make I get:
jasper-taylors-macbook:src jaspert$ make
(cd EnginePl; make config)
gcc -m32 -O3 -fomit-frame-pointer -o pl_config pl_config.c
./pl_config
Bad Value of WORD_SIZE - should be 32
make[1]: *** [wam_regs.h] Error 1
make: *** [all] Error 2
Any suggestions?
--Jasper

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Minor setup packaging error in setup-gprolog-1.3.1.exe.

2009-12-02T14:12:32Z

I downloaded and installed 'setup-gprolog-1.3.1.exe' onto my 'E:' drive
into folder 'E:/GNU-Prolog'. The setup process creates:

GNU Prolog.lnk -> E:/GNU-Prolog/bin/gprolog.exe
Help.lnk -> E:/GNU-Prolog/doc/manual.chm <<<<<=============******
Html Manual.lnk -> E:/GNU-Prolog/doc/html_node/index.html
The GNU Prolog Web Site.lnk -> E:/GNU-Prolog/gprolog.url
Uninstall GNU Prolog.lnk -> E:/GNU-Prolog/unins000.exe

in 'C:\Documents and Settings\All Users\Start Menu\Programs\GNU Prolog'.

There is no 'manual.chm' in 'E:/GNU-Prolog/doc/'; but there is a
'gprolog.chm'. This appears to be a setup packaging error where

'Help.lnk -> E:/GNU-Prolog/doc/gprolog.chm'<<<<<=============******

is probably what is wanted. The other links work as expected.

Regards,

Lowell Anderson

----[cut-patch, perhaps]-----
->diff -up gp-setup.iss.in gp-setup.iss-1.in
--- gp-setup.iss.in 2009-01-23 03:15:02.000000000 -0800
+++ gp-setup.iss-1.in 2009-12-02 14:01:28.937500000 -0800
@@ -41,7 +41,7 @@ Filename: "{app}\gprolog.url"; Section:

[Icons]
Name: "{group}\GNU Prolog"; Filename: "{app}\bin\gprolog.exe"
-Name: "{group}\Help"; Filename: "{app}\doc\manual.chm"
+Name: "{group}\Help"; Filename: "{app}\doc\gprolog.chm"
Name: "{group}\Html Manual"; Filename: "{app}\doc\html_node\index.html"
Name: "{group}\The GNU Prolog Web Site"; Filename: "{app}\gprolog.url"
Name: "{group}\Uninstall GNU Prolog"; Filename: "{uninstallexe}"

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Minor setup packaging error in setup-gprolog-1.3.1.exe.

2009-12-01T19:45:24Z

From forum: Gnu - Prolog - Bugs

Re: Snow Leopard (MacOS X 10.6) port

2009-11-20T07:48:38Z

Hi Paulo,

this is fixed in next release (not yet ready). Here is the current
snapshot including the fix (for the moment gprolog is compiled in
32-bits mode). The tarball is in the unstable directory:

http://gprolog.univ-paris1.fr/unstable/gprolog-20091120.tgz

Paulo let me know if it is OK.

I'm interested in feedbacks about the stability of this version (since I
have changed some important things like list manipulation predicates,
e.g. the basic append/3 should be around 3 times faster). You can report
success/problems here on the list or directly by email at
Daniel.Diaz@....

Thank you

Daniel

Paulo Moura a écrit :

> Hi!
>
> I updated to Snow Leopard (MacOS X 10.6) and I'm trying, without success so far, to compile the latest unstable version of GNU Prolog (dated from September 2). Any hints? I'm getting the error (already reported by others):
>
> (cd EnginePl; make config)
> gcc -march=i486 -O3 -fomit-frame-pointer -o pl_config pl_config.c
> pl_config.c:1: error: CPU you selected does not support x86-64 instruction set
> pl_config.c:1: error: CPU you selected does not support x86-64 instruction set
> make[1]: *** [pl_config] Error 1
> make: *** [all] Error 2
>
> Hacked march=x86-64 but that gives another error:
>
> gplc -c foreign.wam
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:4:32-bit absolute addressing is not supported for x86-64
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:4:cannot do signed 4 byte relocation
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:9:32-bit absolute addressing is not supported for x86-64
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:9:cannot do signed 4 byte relocation
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:14:32-bit absolute addressing is not supported for x86-64
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:14:cannot do signed 4 byte relocation
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:18:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:19:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:31:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:32:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:36:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:37:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:44:32-bit absolute addressing is not supported for x86-64
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:44:cannot do signed 4 byte relocation
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:48:32-bit absolute addressing is not supported for x86-64
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:48:cannot do signed 4 byte relocation
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:52:32-bit absolute addressing is not supported for x86-64
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:52:cannot do signed 4 byte relocation
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:70:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:71:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:75:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:76:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:79:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:80:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:84:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:85:suffix or operands invalid for `push'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:88:suffix or operands invalid for `pop'
> /var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:89:suffix or operands invalid for `pop'
> compilation failed
> make[1]: *** [foreign.o] Error 1
> make: *** [all] Error 1
>
> There is already a port to x86_64/bsd so it should not be difficult to solve the problem above. Your feedback is appreciated.
>
> Cheers,
>
> Paulo
>
>
> -----------------------------------------------------------------
> Paulo Jorge Lopes de Moura, PhD
> Assistant Professor
> Dep. of Computer Science, University of Beira Interior
> 6201-001 Covilhã, Portugal
>
> Office 3.18 Ext. 3276
> Phone: +351 275319891 Fax: +351 275319899
> Email: <mailto:pmoura@...>
>
> Home page: <http://www.di.ubi.pt/~pmoura>
> Research: <http://logtalk.org/> Blog: <http://blog.logtalk.org/>
> -----------------------------------------------------------------
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Users-prolog mailing list
> Users-prolog@...
> http://lists.gnu.org/mailman/listinfo/users-prolog
>
>

--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog

From forum: Gnu - Prolog - Users

Snow Leopard (MacOS X 10.6) port

2009-11-20T07:17:19Z

Hi!

I updated to Snow Leopard (MacOS X 10.6) and I'm trying, without success so far, to compile the latest unstable version of GNU Prolog (dated from September 2). Any hints? I'm getting the error (already reported by others):

(cd EnginePl; make config)
gcc -march=i486 -O3 -fomit-frame-pointer -o pl_config pl_config.c
pl_config.c:1: error: CPU you selected does not support x86-64 instruction set
pl_config.c:1: error: CPU you selected does not support x86-64 instruction set
make[1]: *** [pl_config] Error 1
make: *** [all] Error 2

Hacked march=x86-64 but that gives another error:

gplc -c foreign.wam
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:4:32-bit absolute addressing is not supported for x86-64
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:4:cannot do signed 4 byte relocation
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:9:32-bit absolute addressing is not supported for x86-64
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:9:cannot do signed 4 byte relocation
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:14:32-bit absolute addressing is not supported for x86-64
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:14:cannot do signed 4 byte relocation
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:18:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:19:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:31:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:32:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:36:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:37:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:44:32-bit absolute addressing is not supported for x86-64
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:44:cannot do signed 4 byte relocation
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:48:32-bit absolute addressing is not supported for x86-64
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:48:cannot do signed 4 byte relocation
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:52:32-bit absolute addressing is not supported for x86-64
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:52:cannot do signed 4 byte relocation
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:70:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:71:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:75:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:76:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:79:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:80:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:84:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:85:suffix or operands invalid for `push'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:88:suffix or operands invalid for `pop'
/var/folders/sY/sY2-SVlw2RWEKk+8ZReZU++++TI/-Tmp-/gplci6MwUc.s:89:suffix or operands invalid for `pop'
compilation failed
make[1]: *** [foreign.o] Error 1
make: *** [all] Error 1

There is already a port to x86_64/bsd so it should not be difficult to solve the problem above. Your feedback is appreciated.

Cheers,

Paulo

-----------------------------------------------------------------
Paulo Jorge Lopes de Moura, PhD
Assistant Professor
Dep. of Computer Science, University of Beira Interior
6201-001 Covilhã, Portugal

Office 3.18 Ext. 3276
Phone: +351 275319891 Fax: +351 275319899
Email: <mailto:pmoura@...>

Home page: <http://www.di.ubi.pt/~pmoura>
Research: <http://logtalk.org/> Blog: <http://blog.logtalk.org/>
-----------------------------------------------------------------

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog

From forum: Gnu - Prolog - Users

Cygwin --- interpreter exits after invoking

2009-11-19T13:15:29Z

Hi, I'm having problems getting GNU Prolog (stable and unstable) to run under Cygwin... bug report follows.

* The type of machine you are using (use uname -a under Unix) --- A Cygwin PC
* GNU Prolog version (use gprolog --version). --- I tried 1.3.1 and 1.3.2
* The operands given to the `configure' and the output of the configuration if the bug concerns the compilation/installation phase. -- none, I simply typed "./configure && make && make install"
* The complete text of any files needed to reproduce the bug. Try to obtain a minimal example showing the bug.

[tbrannon@Ghostdc7600] [/usr/local/gprolog-1.3.2/bin] ./gprolog.exe
GNU Prolog 1.3.2
By Daniel Diaz
Copyright (C) 1999-2009 Daniel Diaz
| ?-

Report bugs to bug-prolog@....
[tbrannon@Ghostdc7600] [~/prg/cygwin/gnuprolog/GNU-Prolog-1.3.1-1-src/src] /usr/local/gprolog-1.3.1/bin/gprolog --init-goal write(before), nl --entry-goal write(inside), nl --query-goal append([a,b],[c,d],X)
sh: syntax error near unexpected token `('
[tbrannon@Ghostdc7600] [~/prg/cygwin/gnuprolog/GNU-Prolog-1.3.1-1-src/src] /usr/local/gprolog-1.3.1/bin/gprolog.exe
GNU Prolog 1.3.1
By Daniel Diaz
Copyright (C) 1999-2009 Daniel Diaz
| ?-

[tbrannon@Ghostdc7600] [~/prg/cygwin/gnuprolog/GNU-Prolog-1.3.1-1-src/src]

* A description of what behavior you observe that you believe is incorrect --- the interpreter exits upon being invoked, instead of staying in a read - eval - execute loop.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

bug with cyrillic symbols

2009-11-19T01:24:39Z

Hello, Bug-prolog.

Cyrillic symbol 'м', 'я' and 'Ё' not visible in console, but it
working.

--
mailto:prokopchuk@...

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog

From forum: Gnu - Prolog - Bugs

Re: Compiling GNU Prolog under Windows 7 with MSVC++ 2008

2009-11-18T07:37:15Z

Hello James,

thank you for this bug + workaround report.
I'll look at it in details later and see how to include your patch.

Thanks again.

Daniel

James Gate a écrit :

Hi,

* I am running GNU Prolog on an x86 running the 32-bit version of Windows 7.
* My compiler is Microsoft Visual C++ 2008 Express Edition - i.e. the free one.
* I have the latest version of the Windows SDK installed - i.e. the one with Windows 7 support.
* The following is about GNU Prolog Version 1.3.1.

If I download the GNU Prolog windows installer package (for MSVC), the interpreter works fine but the compiler fails to link due to the library 'libcp.lib' having been renamed to 'libc.lib' in the move from VC++ 2005 to 2008.

Therefore I decided to compile GNU Prolog from source using VC++ 2008. I did this as follows:
1. Extract archive.
2. Open up VC++ 2008 command prompt and 'cd' into C:\<extract location>\gprolog-1.3.1\src
3. Execute the command 'sh configure --with-msvc --with-install-dir=/c/Dev/GProlog'
4. Execute 'make'
5. Execute 'make install'

* The command 'sh' comes from MSys 1.0, whose 'bin' directory is in my PATH environment variable.

* Initially step 3 failed because there was no 'mingw-as.exe' in my path, but 'as.exe' (from MinGW 5.1.4) was, so I simply copied 'as.exe' to 'mingw-as.exe' in MinGW's 'bin' directory.

* Step 4 failed with the following error:
(cd ../TopComp; make gplc.exe)
make[2]: Entering directory `/c/Users/James/Desktop/gprolog-1.3.1/src/TopComp'
cl -nologo -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -O2 -EHsc -Feg
plc.exe top_comp.c advapi32.lib user32.lib ws2_32.lib
top_comp.c
C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\stdio.h(272) : error C31
63: 'getc': attributes inconsistent with previous declaration
C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\stdio.h(214) : s
ee declaration of 'getc'
make[2]: *** [gplc.exe] Error 2
make[2]: Leaving directory `/c/Users/James/Desktop/gprolog-1.3.1/src/TopComp'
make[1]: *** [wam_regs.h] Error 2
make[1]: Leaving directory `/c/Users/James/Desktop/gprolog-1.3.1/src/EnginePl'
make: *** [all] Error 2

Which can be fixed in the file 'EnginePl\arch_dep.h' by either commenting out the block:
#ifndef HAVE_FGETC
#define fgetc getc
#endif
Or adding the line
#define HAVE_FGETC
before the block.

Everything seems to be running as per normal and I can successfully compile and link programs. I assume the above problem in 'arch_dep.h' is something to do with the 'configure' script, but I have zero experience with these so any fix I produce will most likely only work on my platform!

Kind Regards,

James Gate,
PhD Student, Algorithms and Complexity Resarch Group, University of Durham, UK.

--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
_______________________________________________ Bug-prolog mailing list Bug-prolog@... http://lists.gnu.org/mailman/listinfo/bug-prolog

--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: number_codes breaks if handling unmatched-doublequote error

2009-11-18T02:07:18Z
Thank you Jasper for your detailed report (very precise).
Il is fixed and will be available in the next version (coming soon as a
beta).

Daniel

Jasper Taylor a écrit :

> Hi Daniel and everyone.
> I am using gprolog 1.3.2 on Linux and I have this problem. In certain
> circumstances, number_codes is raising an exception when it should
> succeed. This only happens if:
> * number_codes has a string matching a valid number as the 2nd arg and
> a variable as the first
> * number_codes is called in the exception handling clause of 'catch'
> * the exception clause is executing because the goal of 'catch'
> contained a read_term which caused a parse error
> * the parse error was due to an unmatched double quote.
>
> This example produces the bug. It looks like the read_term is
> producing two errors, one of which hangs around and causes an
> exception in number_codes. The string of codes converts to sin("foo).
>
>
> catch(read_from_codes([115,105,110,40,34,102,111,111,41,47], Term),
> Bug,
> number_codes(G, [51,49])).
>
> note that if you replace number_codes with name, the example executes
> and catches the exception correctly, but G gets set to the atom '31'
> rather than the number 31, which I guess is because the implementation
> of name calls number_codes internally, and calls atom_codes when that
> raises an exception.
> Hope you enjoy this challenge!
> --Jasper
>
>
>
> _______________________________________________
> Bug-prolog mailing list
> Bug-prolog@...
> http://lists.gnu.org/mailman/listinfo/bug-prolog
>

--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

number_codes breaks if handling unmatched-doublequote error

2009-11-16T04:50:44Z
Hi Daniel and everyone.
I am using gprolog 1.3.2 on Linux and I have this problem. In certain
circumstances, number_codes is raising an exception when it should
succeed. This only happens if:
* number_codes has a string matching a valid number as the 2nd arg and a
variable as the first
* number_codes is called in the exception handling clause of 'catch'
* the exception clause is executing because the goal of 'catch'
contained a read_term which caused a parse error
* the parse error was due to an unmatched double quote.

This example produces the bug. It looks like the read_term is producing
two errors, one of which hangs around and causes an exception in
number_codes. The string of codes converts to sin("foo).

catch(read_from_codes([115,105,110,40,34,102,111,111,41,47], Term),
Bug,
number_codes(G, [51,49])).

note that if you replace number_codes with name, the example executes
and catches the exception correctly, but G gets set to the atom '31'
rather than the number 31, which I guess is because the implementation
of name calls number_codes internally, and calls atom_codes when that
raises an exception.
Hope you enjoy this challenge!
--Jasper

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Compiling GNU Prolog under Windows 7 with MSVC++ 2008

2009-11-15T05:11:26Z
Hi,

* I am running GNU Prolog on an x86 running the 32-bit version of Windows 7.
* My compiler is Microsoft Visual C++ 2008 Express Edition - i.e. the free one.
* I have the latest version of the Windows SDK installed - i.e. the one with Windows 7 support.
* The following is about GNU Prolog Version 1.3.1.

If I download the GNU Prolog windows installer package (for MSVC), the interpreter works fine but the compiler fails to link due to the library 'libcp.lib' having been renamed to 'libc.lib' in the move from VC++ 2005 to 2008.

Therefore I decided to compile GNU Prolog from source using VC++ 2008. I did this as follows:
1. Extract archive.
2. Open up VC++ 2008 command prompt and 'cd' into C:\<extract location>\gprolog-1.3.1\src
3. Execute the command 'sh configure --with-msvc --with-install-dir=/c/Dev/GProlog'
4. Execute 'make'
5. Execute 'make install'

* The command 'sh' comes from MSys 1.0, whose 'bin' directory is in my PATH environment variable.

* Initially step 3 failed because there was no 'mingw-as.exe' in my path, but 'as.exe' (from MinGW 5.1.4) was, so I simply copied 'as.exe' to 'mingw-as.exe' in MinGW's 'bin' directory.

* Step 4 failed with the following error:
(cd ../TopComp; make gplc.exe)
make[2]: Entering directory `/c/Users/James/Desktop/gprolog-1.3.1/src/TopComp'
cl -nologo -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -O2 -EHsc -Feg
plc.exe top_comp.c advapi32.lib user32.lib ws2_32.lib
top_comp.c
C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\stdio.h(272) : error C31
63: 'getc': attributes inconsistent with previous declaration
C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\stdio.h(214) : s
ee declaration of 'getc'
make[2]: *** [gplc.exe] Error 2
make[2]: Leaving directory `/c/Users/James/Desktop/gprolog-1.3.1/src/TopComp'
make[1]: *** [wam_regs.h] Error 2
make[1]: Leaving directory `/c/Users/James/Desktop/gprolog-1.3.1/src/EnginePl'
make: *** [all] Error 2

Which can be fixed in the file 'EnginePl\arch_dep.h' by either commenting out the block:
#ifndef HAVE_FGETC
#define fgetc getc
#endif
Or adding the line
#define HAVE_FGETC
before the block.

Everything seems to be running as per normal and I can successfully compile and link programs. I assume the above problem in 'arch_dep.h' is something to do with the 'configure' script, but I have zero experience with these so any fix I produce will most likely only work on my platform!

Kind Regards,

James Gate,
PhD Student, Algorithms and Complexity Resarch Group, University of Durham, UK.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

DES 1.7.0 Released

2009-10-30T08:32:48Z
[Apologies for multiple receptions]

Hello.
This is a mail just for informing that the new release

Datalog Educational System version 1.6.2
http://des.sourceforge.net

has been launched on October, 30th, 2009 and ported to

GNU Prolog 1.3.1

The main novelties in this release are: New tabled
aggregate predicates and functions, including count,
sum, avg, min, max, times, and group_by. This allows
to support SQL aggregates with the usual aggregate
functions and grouping clause. SQL statements
including such aggregates are translated into Datalog
rules including a group_by predicate, which, in turn,
may contain aggregate functions in arithmetic
expressions occurring both in the projection list and
in the having condition. In addition, these
aggregates allow solving some optimization problems.
Also, is_null and not_is_null predicates are included
for testing null values in Datalog rules. Domain,
primary key, and referential integrity constraints
for tables created with SQL statements can be
specified, and are checked whenever a fact is
asserted (or a tuple inserted). In addition, a basic
type inferring system for views is provided. For
easing the writing of rules, operands of comparison
operators, the equality in particular, can be
(arithmetic) expressions which are evaluated before
the comparison itself. Finally, a very preliminary
version of a test case generator for SQL views is
included.

Release notes are attached to the end of this message.
Please, see http://des.sourceforge.net/ for details.

Best regards.

==============================================================
Fernando Sáenz Pérez
Profesor Titular de Universidad / Associate Professor
Home Page: http://www.fdi.ucm.es/profesor/fernan
Tel: + 34 913947642. Fax: + 34 913947547
Despacho / Office: 435 (4ª planta / 4th floor)
Dept. Ingeniería del Software e Inteligencia Artificial /
Department of Software Engineering and Artificial Intelligence
Universidad Complutense de Madrid
Facultad de Informática
C/Profesor José García Santesmases, s/n
E - 28040 Madrid. Spain
==============================================================

Version 1.7.0 of DES adds to previous version (1.6.2):

* Enhancements:
o Extended SQL grammar and processor to cope with types as well as table and column constraints (primary key and foreign key)
o Type system for SQL. Primitive types include: char, char(n), varchar(n), varchar, string, int, integer, and real
o Basic type checking/inferring system for SQL views. Inferred types for views are displayed via /dbschema and, for autoviews, in the answer relation. Inferring precision is low (the types of expressions and numbers are not inferred)
o Domain, primary key, and referential integrity constraints for tables created with SQL statements
o Datalog aggregate predicates: group_by/3, count/3, count/2, sum/3, times/3, avg/3, min/3, and max/3
o Datalog aggregate functions: count/0, count/1, sum/1, times/1, avg/1, min/1, and max/1
o Datalog predicate builtins: is_null/1 and is_not_null/1 for determining whether their single argument is a null value or not, respectively
o Test case generation for views
o New commands:
* /test_case View. Generates all test case classes of for the given view
* /p Filename. Shorthand for /process Filename
o Upgraded commands:
* /listing Head. Lists all rules whose heads are subsumed by Head
* /listing Head:-Body. Lists all rules that are subsumed by Head:-Body
o The command process looks for its input filename, allowing to omit the extensions .sql and .ini
o Comparison operators can include arithmetic expressions, as in A<2*B. This also means that equality behaves more generally than is/2, as shown in the query sqrt(2)=X, which returns { sqrt(2) = 1.4142135623730951 }
o Some arithmetic expressions are precomputed when translating SQL statements to Datalog rules
o Displaying the number of tuples in rule listings, retracts, and abolishes
o Adding development flag status to the listing of /status
* Changes:
o A table definition with a CREATE TABLE statement must include a type for each attribute. Former table definitions (up to version 1.6.2) are no longer valid
o Evaluation of an arithmetic expression including a null value returns a null, instead of raising an exception
o Operands of comparison operators are evaluated. Only arithmetic expressions are allowed, up to now. So, X=Y+2 is allowed whenever Y is bound
o The distribution files des1.pl, dessql.pl, and desdebug.pl have been renamed to des_glue.pl, des_sql.pl, and des_debug.pl, respectively
* Fixed bugs:
o Development listings via /dbschema were not displaying compiled Datalog rules
o String constants including only digits were incorrectly parsed as numbers
o Failed to parse SQL set statements involving constants in the projection list
o Nulls were not correctly read from files
o IS NULL and IS NOT NULL in SQL statements were not behaving correctly
o Safety checks involving disjunctions were not always properly performed, as in p(X) :- q(X);r(X)
o The command /operators was never implemented but listed via /help. It has been removed
o Listings of exploded rules were not displaying the correct source variable names in bodies
o Some rules could not been asserted under simplification, as p(X):-X=1;X=2
o Error when a multiply renamed table occurs in a SQL statement, as in select * from t t1,t t2 where t1.a=t2.a
* Caveat:
o Batch processing cannot be nested
* Known bugs:
o The projection list of a natural outer join is not correct in all cases
o Disjunctions in having conditions in the group_by clause may yield to errors which are not

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

Re: Open File Error?

2009-10-23T01:14:34Z
Hello,

this problem comes from the fact under Windows the \ char is the separator inside pathnames. Most built-in predicates handling file names call absolute_file_name/2 which computes the absolute path (resolving for instance variable substitutions, relative path like .\ and ..\, etc). Since gprolog does not yet handle wide chars when it sees a \ it treats it as a separator. Until such an extension is done there is no "clean" way to solve this. However, I'd like to provide a "not too dirty" workaround for the special case of pathnames. The easiest way I see to fix this
is to use an enviroment variable (or a Windows register key) to indicate if a \ preceded by a char >= 128 is not a separator. What do you think ?

Daniel

Yasuhisa Matsumura wrote:

Dear Prof. Daniel Diaz and other GNU-Prolog developers!

Thank you very much for your splendid Prolog compiler.

I would like to report the following 'BUG' (or 'Short-coming') under Windows OS.

I would be very glad as a Japanese user, if you could fix it some time.

Thank you very much, again.

Yasuhisa Matsumura

matsmura@...

OS: Windows Vista
GNU-Prolog version: 1.3.1

The Japanese Windows system encoding (= Shift_JIS) includes such a 2-byte character:

   '\x95\\\' i.e. name('\x95\\\',[149,92]).

%%%%%%%%%%%%%%%%%%%%%

But you can NOT open the file with the file name '\x95\\\.txt', for example,

   test(C) :- see('\x95\\\.txt'),get0(C),seen.

uncaught exception: error(existence_error(source_sink,'\x95\\\.txt'),see/1)

%%%%%%%%%%%%%%%%%%%%%%%%%

In contrast, you CAN open the file with the file name '\x95\[.txt' i.e. name('\x95\[',[149,91]).

   test(C) :- see('\x95\[.txt'), get0(C), seen.

   C = 97     in case you wrote the character 'a' in the file.

%%%%%%%%%%%%%%%%

PS.　　The characters have the following appearance on Windows system:

'\x95\\\'　 =　　'表'.

'\x95\['　   =　　'票'.

But I think you cannot view the character appearance on your French or English Operating System.

--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
_______________________________________________ Bug-prolog mailing list Bug-prolog@... http://lists.gnu.org/mailman/listinfo/bug-prolog

Re: Open File Error? No.2

2009-10-17T20:17:22Z

This is Yasuhisa Matsumura, again.

PS. Please let me add some information to the previous mail ('Open File Error?') of mine.

On Japanese Windows, you cannot create any file with a filename that includes the so called backslash '\\' (= [92]),

but you CAN create a file with such a Japanese filename the character codes for which include the backslash code [92] as its subpart.

For example: you CANNOT directly create a file with the filename 'abc\d.txt'.

But you CAN create a file with the filename '表.txt'.

The character code list for '表.txt' is [149,92 | ".txt"].

Unfortunately, we have lots of such 2-byte characters that include [92].

The preceding code (=149 in the above example) directly before the backslash code [92] is always greater than (>) 128 in the Japanese system.

Yasuhisa Matsumura

matsmura@...

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Open File Error?

2009-10-17T18:12:03Z

Dear Prof. Daniel Diaz and other GNU-Prolog developers!

Thank you very much for your splendid Prolog compiler.

I would like to report the following 'BUG' (or 'Short-coming') under Windows OS.

I would be very glad as a Japanese user, if you could fix it some time.

Thank you very much, again.

Yasuhisa Matsumura

matsmura@...

OS: Windows Vista
GNU-Prolog version: 1.3.1

The Japanese Windows system encoding (= Shift_JIS) includes such a 2-byte character:

   '\x95\\\' i.e. name('\x95\\\',[149,92]).

%%%%%%%%%%%%%%%%%%%%%

But you can NOT open the file with the file name '\x95\\\.txt', for example,

   test(C) :- see('\x95\\\.txt'),get0(C),seen.

uncaught exception: error(existence_error(source_sink,'\x95\\\.txt'),see/1)

%%%%%%%%%%%%%%%%%%%%%%%%%

In contrast, you CAN open the file with the file name '\x95\[.txt' i.e. name('\x95\[',[149,91]).

   test(C) :- see('\x95\[.txt'), get0(C), seen.

   C = 97     in case you wrote the character 'a' in the file.

%%%%%%%%%%%%%%%%

PS.　　The characters have the following appearance on Windows system:

'\x95\\\'　 =　　'表'.

'\x95\['　   =　　'票'.

But I think you cannot view the character appearance on your French or English Operating System.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Negative values in constraint solving

2009-10-12T09:32:00Z
Dear list, dear Daniel,

are negative values in constraint solving planned for some future
release? Such that:

X #< 0

has a solution? It would help a lot for many application scenarios we
use gprolog for (like solving constraints over amounts of money, etc.).

Thanks a lot for gprolog, it does a great job!

Cheers,
Lars

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

Re: gprolog and the 'listing' command

2009-10-12T08:34:48Z
Hello Antonio,

Antonio Maschio wrote:
> Hi all (and especially Daniel),
>
> is it just possible to incorporate, in next versions of gprolog, the
> 'listing' behavior for output in the **current** stream, and not
> **always** to standard output?
Yes I'll do it since many people ask for this.
In gprolog 1.3.2 listing will work on current output stream.
I should be available very soon.

Daniel

--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

gprolog and the 'listing' command

2009-10-12T03:17:15Z
Hi all (and especially Daniel),

is it just possible to incorporate, in next versions of gprolog, the
'listing' behavior for output in the **current** stream, and not
**always** to standard output?

I mean: following the interesting exercises of the "Prolog Programming
in Depth" book by M. Covington et al., there's an exercise
("learner.pl") which makes use of the fact that opening an output file
stream, typing 'listing(pred_whatever/n)' and closing the stream, in the
file there's a complete database of facts for 'pred_whatever' that can
be read successively. through an input stream.

yap and swipl work this way; gprolog, instead, **always** prints the
output to screen.

I know this is not covered in ISO Prolog (at least, AFAIK), but it's
common practice in others, so I guess gprolog should conform to it (or
at least, enable this through some switch).

What's your thought, Daniel?

-- Antonio

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

Re: Snow Leopard Worries

2009-10-08T06:40:12Z
Hi again,
I managed to make the current binary Mac version build executables on
snow leopard by adding an assembler switch to gplc as follows:
gplc -A '-arch i386' test.pl
...however, I still cannot build the Prolog binary
--Jasper

Daniel Diaz wrote:

> Hi Jasper
>
> I have no Snow Leopard on a machine so it is difficult for me to fix
> this (Paulo Moura kindly gave me an access to his mac for the initial
> port on mac os). Can you give me an access to your machine (via ssh) ?
>
> Daniel
>> Hi Daniel and crew,
>> I recently updated my MacBook to Snow Leopard, and now have some
>> problems.
>> While the Prolog executables I built previously with OSX 10.5 still
>> run OK, I cannot build new ones. Here is a simple example to show the
>> sort of errors I am getting. This is using gprolog 1.3.1.
>> File test.pl:
>> main :-
>> write('Hello World!'), nl.
>>
>> jaspert$ gplc test.pl
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:4:32-bit
>> absolute addressing is not supported for x86-64
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:4:cannot
>> do signed 4 byte relocation
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:15:32-bit
>> absolute addressing is not supported for x86-64
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:15:cannot
>> do signed 4 byte relocation
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:17:32-bit
>> absolute addressing is not supported for x86-64
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:17:cannot
>> do signed 4 byte relocation
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:24:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:25:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:37:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:38:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:42:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:43:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:50:32-bit
>> absolute addressing is not supported for x86-64
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:50:cannot
>> do signed 4 byte relocation
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:54:32-bit
>> absolute addressing is not supported for x86-64
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:54:cannot
>> do signed 4 byte relocation
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:57:32-bit
>> absolute addressing is not supported for x86-64
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:57:cannot
>> do signed 4 byte relocation
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:67:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:68:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:72:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:73:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:76:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:77:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:81:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:82:suffix
>> or operands invalid for `push'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:85:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:86:suffix
>> or operands invalid for `pop'
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:102:unknown
>> section type: symbol_stubs
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:102:Rest
>> of line ignored. 1st junk character valued 115 (s).
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:104:Unknown
>> pseudo-op: .indirect_symbol
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:104:Rest
>> of line ignored. 1st junk character valued 95 (_).
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:107:Unknown
>> pseudo-op: .indirect_symbol
>> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:107:Rest
>> of line ignored. 1st junk character valued 95 (_).
>> compilation failed
>>
>> ...so, I attempted to compile it under Snow Leopard to see if a new
>> build would fix the problem. I downloaded the latest 'unstable'
>> source code and ran 'configure' OK, but then:
>>
>> jaspert$ make
>> (cd EnginePl; make config)
>> gcc -march=i486 -O3 -fomit-frame-pointer -o pl_config pl_config.c
>> pl_config.c:1: error: CPU you selected does not support x86-64
>> instruction set
>> pl_config.c:1: error: CPU you selected does not support x86-64
>> instruction set
>> make[1]: *** [pl_config] Error 1
>> make: *** [all] Error 2
>>
>> I had a look at the INSTALL file to see if there was any mention of
>> setting the architecture, and tried configuring with --disable-regs.
>> This made no difference. I would like to be able to build prolog
>> executables on OSX 10.6 that work on 10.5 and 10.4 -- currently even
>> on 10.5 I cannot build one that works on 10.4. I would be quite happy
>> if it was all 32-bit!
>>
>> Any help much appreciated
>> --Jasper
>>
>>
>> _______________________________________________
>> Bug-prolog mailing list
>> Bug-prolog@...
>> http://lists.gnu.org/mailman/listinfo/bug-prolog
>>
>
>

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: Literal quote character causes exception.

2009-10-06T07:54:42Z

On 2009/10/06, at 13:18, Nicolas Pelletier wrote:

> Hello,
>
> On Tue, Oct 6, 2009 at 19:46, Daniel Diaz <Daniel.Diaz@univ-
> paris1.fr> wrote:
>>
>> after looking carefully at the ISO standard, there is no bug here.
>> ISO says
>> the syntax is:
>>
>> 0'<single quoted char>
>>
>> where <single quoted char> is a character that could appear in a
>> quoted
>> string. So if you want to use ' inside either you have to write it
>> twice
>> ('') or to escape it \'
>>
>> You should use one of the valid forms: 0''' or 0'\'
>
> I see... Yes, on re-reading, I was wrong.

I don't have the standard with me right now, but I seem to remember
that the ('') and \' is only used within quoted atoms.

>> I agree the result is not very nice...
>> In 1.3.2 I will relax the lexer to also accept 0'' (to remain
>> compatible
>> with other Prolog systems).
>
> Thank you. Compatibility is indeed how I ran into this case: Logtalk
> includes in its contributions directory a XML parser, which loaded
> fine when used over SWI Prolog, but failed to load when user over GNU
> Prolog. Running further tests now with XSB shows there are varying
> interpretations on what the standard says...

Unfortunately, yes. Nevertheless, GNU Prolog is the first compiler I
have found that chokes on 0''. Relaxing the lexer seems the sensible
thing to do until the standard is clarified/rectified/updated.

Best regards,

Paulo

-----------------------------------------------------------------
Paulo Jorge Lopes de Moura, PhD
Assistant Professor
Dep. of Computer Science, University of Beira Interior
6201-001 Covilhã, Portugal

Office 3.18 Ext. 3276
Phone: +351 275319891 Fax: +351 275319899
Email: <mailto:pmoura@...>

Home page: <http://www.di.ubi.pt/~pmoura>
Research: <http://logtalk.org/> Blog: <http://blog.logtalk.org/>
-----------------------------------------------------------------

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: Literal quote character causes exception.

2009-10-06T05:18:17Z
Hello,

On Tue, Oct 6, 2009 at 19:46, Daniel Diaz <Daniel.Diaz@...> wrote:

>
> after looking carefully at the ISO standard, there is no bug here. ISO says
> the syntax is:
>
> 0'<single quoted char>
>
> where <single quoted char> is a character that could appear in a quoted
> string. So if you want to use ' inside either you have to write it twice
> ('') or to escape it \'
>
> You should use one of the valid forms: 0''' or 0'\'

I see... Yes, on re-reading, I was wrong.

> I agree the result is not very nice...
> In 1.3.2 I will relax the lexer to also accept 0'' (to remain compatible
> with other Prolog systems).

Thank you. Compatibility is indeed how I ran into this case: Logtalk
includes in its contributions directory a XML parser, which loaded
fine when used over SWI Prolog, but failed to load when user over GNU
Prolog. Running further tests now with XSB shows there are varying
interpretations on what the standard says...

Regards,

--
Nicolas

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: Literal quote character causes exception.

2009-10-06T03:46:40Z
Nicolas,

after looking carefully at the ISO standard, there is no bug here. ISO
says the syntax is:

0'<single quoted char>

where <single quoted char> is a character that could appear in a quoted
string. So if you want to use ' inside either you have to write it twice
('') or to escape it \'

You should use one of the valid forms: 0''' or 0'\'

I agree the result is not very nice...
In 1.3.2 I will relax the lexer to also accept 0'' (to remain compatible
with other Prolog systems).

Daniel

Daniel Diaz wrote:

> Thanks for this bug report.
>
> Will be fixed
>
> Daniel
>
> Nicolas Pelletier wrote:
>> Hello,
>>
>> I found the following behaviour both in GNU Prolog 1.3.1 and GNU
>> Prolog 20090310, which I believe is incorrect:
>>
>> nicolas@tamago:~/tmp$ gprolog
>> GNU Prolog 1.3.2
>> By Daniel Diaz
>> Copyright (C) 1999-2009 Daniel Diaz
>> | ?- X = 0''.
>> uncaught exception: error(syntax_error('user_input:1 (char:8) quote
>> character expected here'),read_term/3)
>>
>> I expected the substitution X = 39 as the result of my query. Would
>> you please look into this problem ?
>>
>> Thanks in advance.
>>
>>
>
>

--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: Snow Leopard Worries

2009-09-16T09:10:11Z
Daniel Diaz wrote:
> I have no Snow Leopard on a machine so it is difficult for me to fix
> this (Paulo Moura kindly gave me an access to his mac for the initial
> port on mac os). Can you give me an access to your machine (via ssh) ?
No problem, but I just got a new router, and my ISP only gives
dynamic-IP access. When I figure out how to set up the port forwarding
I'll let you know when you can do the port.
Cheers
--Jasper

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: Snow Leopard Worries

2009-09-16T07:32:28Z
Hi Jasper

I have no Snow Leopard on a machine so it is difficult for me to fix
this (Paulo Moura kindly gave me an access to his mac for the initial
port on mac os). Can you give me an access to your machine (via ssh) ?

Daniel

> Hi Daniel and crew,
> I recently updated my MacBook to Snow Leopard, and now have some
> problems.
> While the Prolog executables I built previously with OSX 10.5 still
> run OK, I cannot build new ones. Here is a simple example to show the
> sort of errors I am getting. This is using gprolog 1.3.1.
> File test.pl:
> main :-
> write('Hello World!'), nl.
>
> jaspert$ gplc test.pl
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:4:32-bit
> absolute addressing is not supported for x86-64
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:4:cannot
> do signed 4 byte relocation
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:15:32-bit
> absolute addressing is not supported for x86-64
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:15:cannot
> do signed 4 byte relocation
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:17:32-bit
> absolute addressing is not supported for x86-64
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:17:cannot
> do signed 4 byte relocation
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:24:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:25:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:37:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:38:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:42:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:43:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:50:32-bit
> absolute addressing is not supported for x86-64
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:50:cannot
> do signed 4 byte relocation
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:54:32-bit
> absolute addressing is not supported for x86-64
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:54:cannot
> do signed 4 byte relocation
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:57:32-bit
> absolute addressing is not supported for x86-64
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:57:cannot
> do signed 4 byte relocation
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:67:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:68:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:72:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:73:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:76:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:77:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:81:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:82:suffix
> or operands invalid for `push'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:85:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:86:suffix
> or operands invalid for `pop'
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:102:unknown
> section type: symbol_stubs
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:102:Rest
> of line ignored. 1st junk character valued 115 (s).
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:104:Unknown
> pseudo-op: .indirect_symbol
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:104:Rest
> of line ignored. 1st junk character valued 95 (_).
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:107:Unknown
> pseudo-op: .indirect_symbol
> /var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:107:Rest
> of line ignored. 1st junk character valued 95 (_).
> compilation failed
>
> ...so, I attempted to compile it under Snow Leopard to see if a new
> build would fix the problem. I downloaded the latest 'unstable' source
> code and ran 'configure' OK, but then:
>
> jaspert$ make
> (cd EnginePl; make config)
> gcc -march=i486 -O3 -fomit-frame-pointer -o pl_config pl_config.c
> pl_config.c:1: error: CPU you selected does not support x86-64
> instruction set
> pl_config.c:1: error: CPU you selected does not support x86-64
> instruction set
> make[1]: *** [pl_config] Error 1
> make: *** [all] Error 2
>
> I had a look at the INSTALL file to see if there was any mention of
> setting the architecture, and tried configuring with --disable-regs.
> This made no difference. I would like to be able to build prolog
> executables on OSX 10.6 that work on 10.5 and 10.4 -- currently even
> on 10.5 I cannot build one that works on 10.4. I would be quite happy
> if it was all 32-bit!
>
> Any help much appreciated
> --Jasper
>
>
> _______________________________________________
> Bug-prolog mailing list
> Bug-prolog@...
> http://lists.gnu.org/mailman/listinfo/bug-prolog
>

--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Snow Leopard Worries

2009-09-15T07:16:48Z
Hi Daniel and crew,
I recently updated my MacBook to Snow Leopard, and now have some problems.
While the Prolog executables I built previously with OSX 10.5 still run
OK, I cannot build new ones. Here is a simple example to show the sort
of errors I am getting. This is using gprolog 1.3.1.
File test.pl:
main :-
write('Hello World!'), nl.

jaspert$ gplc test.pl
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:4:32-bit
absolute addressing is not supported for x86-64
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:4:cannot
do signed 4 byte relocation
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:15:32-bit
absolute addressing is not supported for x86-64
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:15:cannot
do signed 4 byte relocation
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:17:32-bit
absolute addressing is not supported for x86-64
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:17:cannot
do signed 4 byte relocation
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:24:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:25:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:37:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:38:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:42:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:43:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:50:32-bit
absolute addressing is not supported for x86-64
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:50:cannot
do signed 4 byte relocation
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:54:32-bit
absolute addressing is not supported for x86-64
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:54:cannot
do signed 4 byte relocation
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:57:32-bit
absolute addressing is not supported for x86-64
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:57:cannot
do signed 4 byte relocation
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:67:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:68:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:72:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:73:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:76:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:77:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:81:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:82:suffix
or operands invalid for `push'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:85:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:86:suffix
or operands invalid for `pop'
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:102:unknown
section type: symbol_stubs
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:102:Rest
of line ignored. 1st junk character valued 115 (s).
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:104:Unknown
pseudo-op: .indirect_symbol
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:104:Rest
of line ignored. 1st junk character valued 95 (_).
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:107:Unknown
pseudo-op: .indirect_symbol
/var/folders/jd/jdqyw4wAELGd2CMr8XviVU+++TI/-Tmp-/gplcj7Nyge.s:107:Rest
of line ignored. 1st junk character valued 95 (_).
compilation failed

...so, I attempted to compile it under Snow Leopard to see if a new
build would fix the problem. I downloaded the latest 'unstable' source
code and ran 'configure' OK, but then:

jaspert$ make
(cd EnginePl; make config)
gcc -march=i486 -O3 -fomit-frame-pointer -o pl_config pl_config.c
pl_config.c:1: error: CPU you selected does not support x86-64
instruction set
pl_config.c:1: error: CPU you selected does not support x86-64
instruction set
make[1]: *** [pl_config] Error 1
make: *** [all] Error 2

I had a look at the INSTALL file to see if there was any mention of
setting the architecture, and tried configuring with --disable-regs.
This made no difference. I would like to be able to build prolog
executables on OSX 10.6 that work on 10.5 and 10.4 -- currently even on
10.5 I cannot build one that works on 10.4. I would be quite happy if it
was all 32-bit!

Any help much appreciated
--Jasper

_______________________________________________
Bug-prolog mailing list
Bug-prolog@...
http://lists.gnu.org/mailman/listinfo/bug-prolog
From forum: Gnu - Prolog - Bugs

Re: Closing sockets does not free them

2009-09-04T03:54:37Z
Dear Nicolas,

many thanks for this comprehensive answer, it helps a lot! Will try
playing with the options you mentioned.

Cheers,
Lars

Nicolas Pelletier wrote:

> Hello,
>
> On Wed, Sep 2, 2009 at 00:41, Lars Frantzen<lf@...> wrote:
>> I have written a simple server written in GNU Prolog opening a socket
>> for a client. After the job is done I close the streams and terminate
>> the program.
>>
>> However, after terminating, the socket stays blocked for some time (like
>> 2 minutes), I get a:
>>
>> system_error(cannot_catch_throw(error(system_error('Address already in
>> use'),socket_bind/2)))
>
> This is perfectly normal behaviour for a TCP socket. :-)
>
> When a TCP socket is closed, it still lingers for some time to allow
> for traffic that would still be directed at it and "on the fly"
> somewhere in the network to die out before the socket can be
> reallocated. If this were not so, quickly closing and re-opening a
> socket bound to the same address and port would let it received
> traffic that was part of the previous (and now irrelevant) stream.
>
> The recommended, standard, and default time-out is 2 minutes. However,
> when using fast networks and/or many TCP connections, this safety
> time-out may come as a performance bottleneck (It is still quite
> common to mistake the number of TCP connections established per second
> for a measure of the actual TCP stack performance). This parameter is
> usually settable; under Linux, man 7 tcp and the parameters in
> /proc/sys/net/ipv4 will let you tweak this. Specifically,
>
> tcp_tw_recycle (Boolean; default: disabled)
> Enable fast recycling of TIME_WAIT sockets. Enabling
> this option is not recommended since this causes problems when working
> with NAT (Net‐
> work Address Translation).
>
> tcp_tw_reuse (Boolean; default: disabled)
> Allow to reuse TIME_WAIT sockets for new
> connections when it is safe from protocol viewpoint. It should
> not be changed without
> advice/request of technical experts.
>
> However, be prepared to debug strange network behaviour if you turn
> the knobs without knowing what they do.
>
> Hope this helps,
>

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

Re: Closing sockets does not free them

2009-09-04T03:30:39Z
Hello,

On Wed, Sep 2, 2009 at 00:41, Lars Frantzen<lf@...> wrote:

>
> I have written a simple server written in GNU Prolog opening a socket
> for a client. After the job is done I close the streams and terminate
> the program.
>
> However, after terminating, the socket stays blocked for some time (like
> 2 minutes), I get a:
>
> system_error(cannot_catch_throw(error(system_error('Address already in
> use'),socket_bind/2)))

This is perfectly normal behaviour for a TCP socket. :-)

When a TCP socket is closed, it still lingers for some time to allow
for traffic that would still be directed at it and "on the fly"
somewhere in the network to die out before the socket can be
reallocated. If this were not so, quickly closing and re-opening a
socket bound to the same address and port would let it received
traffic that was part of the previous (and now irrelevant) stream.

The recommended, standard, and default time-out is 2 minutes. However,
when using fast networks and/or many TCP connections, this safety
time-out may come as a performance bottleneck (It is still quite
common to mistake the number of TCP connections established per second
for a measure of the actual TCP stack performance). This parameter is
usually settable; under Linux, man 7 tcp and the parameters in
/proc/sys/net/ipv4 will let you tweak this. Specifically,

tcp_tw_recycle (Boolean; default: disabled)
Enable fast recycling of TIME_WAIT sockets. Enabling
this option is not recommended since this causes problems when working
with NAT (Net‐
work Address Translation).

tcp_tw_reuse (Boolean; default: disabled)
Allow to reuse TIME_WAIT sockets for new
connections when it is safe from protocol viewpoint. It should
not be changed without
advice/request of technical experts.

However, be prepared to debug strange network behaviour if you turn
the knobs without knowing what they do.

Hope this helps,

--
Nicolas

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

Re: --query-goal problem with gprolog-1.3.1-mingw

2009-09-03T07:14:41Z
Ok, it's fixed in the snapshot : I recompiled this snapshot and then
gprolog-1.3.1 from the source. Everything works fine with the last snapshot, but
fails with 1.3.1.

Is it planned to announce release 1.3.2 soon ?

Thanks.

> Can you try the last snaphsot please ?
>
> http://gprolog.univ-paris1.fr/unstable/gprolog-20090902.tgz
>
> you need to recompile it under mingw

>> Hello,
>>
>> I'm a fan of gprolog, and I have a problem with gprolog-1.3.1-mingw (ok,
>> I'm not proud of the OS I use...) :
>>
>> prompt> gprolog --init-goal nl
>>
>> works fine, but the following commands crash :
>>
>> prompt> gprolog --entry-goal nl
>> prompt> gprolog --query-goal nl
>>
>> Everything works fine with the MSVC build of gprolog-1.3.1 (but I need
>> mingw).

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users

Re: Users-prolog Digest, Vol 76, Issue 2

2009-09-02T20:57:08Z

Howdy Daniel, all?

I recently aquired a Sparc Ultra 5 on which I've installed
OpenBSD (yes, i know it is not supported, but...). When
I attempt to compile it breaks on BipsPl/foreign.wam as
follows:

[babayaga:/usr/local/src/gprolog-1.3.2/src] # gmake
(cd EnginePl; gmake config)
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/EnginePl'
gmake[1]: Nothing to be done for `config'.
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/EnginePl'
. ./SETVARS;for i in TopComp EnginePl Wam2Ma Ma2Asm Linedit BipsPl Pl2Wam Fd2C EngineFD BipsFD;do (cd $i; gmake) || exit 1; done;\
(cd TopComp; gmake gprolog)
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/TopComp'
gmake[1]: Nothing to be done for `first'.
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/TopComp'
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/EnginePl'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/EnginePl'
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/Wam2Ma'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/Wam2Ma'
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/Ma2Asm'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/Ma2Asm'
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/Linedit'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/Linedit'
gmake[1]: Entering directory `/usr/local/src/gprolog-1.3.2/src/BipsPl'
gplc -c foreign.wam
compilation failed
gmake[1]: *** [foreign.o] Error 1
gmake[1]: Leaving directory `/usr/local/src/gprolog-1.3.2/src/BipsPl'
gmake: *** [all] Error 1
[babayaga:/usr/local/src/gprolog-1.3.2/src] # uname -a
OpenBSD babayaga.neotext.ca 4.5 GENERIC#1898 sparc64
[babayaga:/usr/local/src/gprolog-1.3.2/src] #

I am somewhat at a loss as to whether to even attempt to figure out
what has gone wrong (unsupported OS that usually works ok due to being
intentionally bog-standard): the only clue I have is where it breaks
in BipsPl.

babayaga:/usr/local/src/gprolog-1.3.2/src/BipsPl] # ls -lt | more
total 5160
-rw------- 1 root wheel 591384 Sep 2 21:46 ma2asm.core
-rw-r--r-- 1 root wheel 28160 Sep 2 21:46 bc_supp.o
-rw-r--r-- 1 root wheel 1824 Sep 2 21:46 callinf_supp.o
-rw-r--r-- 1 root wheel 10584 Sep 2 21:46 dynam_supp.o
-rw-r--r-- 1 root wheel 57808 Sep 2 21:46 write_supp.o
-rw-r--r-- 1 root wheel 25024 Sep 2 21:45 parse_supp.o
-rw-r--r-- 1 root wheel 41096 Sep 2 21:45 scan_supp.o
-rw-r--r-- 1 root wheel 43632 Sep 2 21:45 stream_supp.o
-rw-r--r-- 1 root wheel 8968 Sep 2 21:45 term_supp.o
-rw-r--r-- 1 root wheel 3928 Sep 2 21:45 pred_supp.o
-rw-r--r-- 1 root wheel 14864 Sep 2 21:45 foreign_supp.o
-rw-r--r-- 1 root wheel 36520 Sep 2 21:45 c_supp.o
-rw-r--r-- 1 root wheel 44360 Sep 2 21:44 error_supp.o
-rw-r--r-- 1 root wheel 4853 Sep 2 10:43 Makefile
-rw-r--r-- 1 root wheel 1218 Feb 10 2009 all_pl_bips.wam
-rw-r--r-- 1 root wheel 66745 Feb 10 2009 debugger.wam

...

Any suggestions would be appreciated.

Thanks,

Dhu

On Wed, 02 Sep 2009 12:00:32 -0400
users-prolog-request@... wrote:

> Send Users-prolog mailing list submissions to
> users-prolog@...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.gnu.org/mailman/listinfo/users-prolog
> or, via email, send a message with subject or body 'help' to
> users-prolog-request@...
>
> You can reach the person managing the list at
> users-prolog-owner@...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Users-prolog digest..."
>
>
> Today's Topics:
>
> 1. Re: --query-goal problem with gprolog-1.3.1-mingw (Daniel Diaz)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 02 Sep 2009 15:38:39 +0200
> From: Daniel Diaz <Daniel.Diaz@...>
> Subject: Re: --query-goal problem with gprolog-1.3.1-mingw
> To: Fred Bapst <frederic.bapst@...>
> Cc: users-prolog@...
> Message-ID: <4A9E755F.9020108@...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Can you try the last snaphsot please ?
>
> http://gprolog.univ-paris1.fr/unstable/gprolog-20090902.tgz
>
> you need to recompile it under mingw
>
> Daniel
>
>
> Fred Bapst wrote:
> > Hello,
> >
> > I'm a fan of gprolog, and I have a problem with gprolog-1.3.1-mingw (ok,
> > I'm not proud of the OS I use...) :
> >
> > prompt> gprolog --init-goal nl
> >
> > works fine, but the following commands crash :
> >
> > prompt> gprolog --entry-goal nl
> > prompt> gprolog --query-goal nl
> >
> > Everything works fine with the MSVC build of gprolog-1.3.1 (but I need
> > mingw).
> >
> > Thanks in advance.
> >
> >
> > _______________________________________________
> > Users-prolog mailing list
> > Users-prolog@...
> > http://lists.gnu.org/mailman/listinfo/users-prolog
> >
>
>
> --
> Ce message a ete verifie par MailScanner
> pour des virus ou des polluriels et rien de
> suspect n'a ete trouve.
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Users-prolog mailing list
> Users-prolog@...
> http://lists.gnu.org/mailman/listinfo/users-prolog
>
>
> End of Users-prolog Digest, Vol 76, Issue 2
> *******************************************

_______________________________________________
Users-prolog mailing list
Users-prolog@...
http://lists.gnu.org/mailman/listinfo/users-prolog
From forum: Gnu - Prolog - Users