Re: Users-prolog Digest, Vol 35, Issue 1 -- AMD64

Duncan Patton a Campbell <[email protected]>
Newsgroups gmane.comp.gnu.prolog.general
Organization 240am ltd.
Message-ID <[email protected]>
Has anyone tried this out on 64bit (Free)BSD?

Thanks,

Dhu


On Mon, 5 Dec 2005 10:23:06 -0700 (MST)
[email protected] wrote:

> Send Users-prolog mailing list submissions to
> 	[email protected]
> 
> 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
> 	[email protected]
> 
> You can reach the person managing the list at
> 	[email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Users-prolog digest..."
> 
> 
> Today's Topics:
> 
>    1. gprolog-1.2.19.tar.gz (Vic Bancroft)
>    2. Re: gprolog-1.2.19.tar.gz (Geoff Alexander)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 05 Dec 2005 00:23:14 -0500
> From: Vic Bancroft <[email protected]>
> Subject: gprolog-1.2.19.tar.gz
> To: Daniel Diaz <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> Daniel Diaz wrote:
> 
> > It is stable, no problem.
> 
> Does a more recent one better recognize the x86_64 bits from AMD ?
> 
>     -------------------------------
>     --- GNU PROLOG INSTALLATION ---
>     -------------------------------
> 
>     GNU Prolog version: 1.2.19 (Jun 13 2005)
>     Operating system : linux-gnu
>     Processor : x86_64
>     Size of a word : 64 bits
>     C compiler : gcc
>     C flags : -O3 -fomit-frame-pointer
>     C flags machine :
>     Loader flags :
>     Loader libraries : -lm
>     Use line editor : Yes
>     Use piped consult : Yes
>     Use sockets : Yes
>     Use FD solver : Yes
>     Use machine regs. : Yes
>     Used register(s) : r12 r13 r14 r15
> 
> Well, perhaps it is my crummy version of gcc,
> 
>     [bancroft@skolem src]$ gcc -v
>     Using built-in specs.
>     Target: x86_64-redhat-linux
>     Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
>     --infodir=/usr/share/info --enable-shared --enable-threads=posix
>     --enable-checking=release --with-system-zlib --enable-__cxa_atexit
>     --disable-libunwind-exceptions --enable-libgcj-multifile
>     --enable-languages=c,c++,objc,java,f95,ada --enable-java-awt=gtk
>     --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
>     --host=x86_64-redhat-linux
>     Thread model: posix
>     gcc version 4.0.2 20051125 (Red Hat 4.0.2-8)
> 
> In any case, my build fails as follows,
> 
>     gplc -c -C '-O3 -fomit-frame-pointer' engine.c
>     engine.c: In function _Call_Prolog_:
>     engine.c:318: error: invalid lvalue in assignment
>     engine.c:331: error: invalid lvalue in assignment
>     engine.c: In function _Call_Prolog_Next_Sol_:
>     engine.c:351: error: invalid lvalue in assignment
>     engine.c:359: error: invalid lvalue in assignment
>     engine.c: In function _Keep_Rest_For_Prolog_:
>     engine.c:380: error: invalid lvalue in assignment
>     engine.c:386: error: invalid lvalue in assignment
>     compilation failed
>     make[1]: *** [engine.o] Error 1
>     make[1]: Leaving directory `/usr/local/src/gprolog-1.2.19/src/EnginePl'
>     make: *** [all] Error 1
> 
> Has anyone else had better luck with this combination ?
> 
> more,
> l8r,
> v
> 
> -- 
> "The future is here. It's just not evenly distributed yet."
>  -- William Gibson, quoted by Whitfield Diffie
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 5 Dec 2005 08:51:41 -0500
> From: "Geoff Alexander" <[email protected]>
> Subject: Re: gprolog-1.2.19.tar.gz
> To: "Daniel Diaz" <[email protected]>
> Cc: [email protected]
> Message-ID: <000c01c5f9a3$05fc6660$b900a8c0@alexander1>
> Content-Type: text/plain; format=flowed; charset="Windows-1252";
> 	reply-type=response
> 
> Daniel,
> 
> The problem is that gprolog 1.2.19 doesn't compile with gcc 4.0.x.  See the 
> bug I reported in August of this year: 
> http://lists.gnu.org/archive/html/bug-prolog/2005-08/msg00000.html.  My 
> workaround was/is to compile with an earlier version of gcc (i.e. gcc 
> 3.4.x).
> 
> Geoff Alexander
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Users-prolog mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/users-prolog
> 
> 
> End of Users-prolog Digest, Vol 35, Issue 1
> *******************************************
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.