Hello,
I have compiled with cygwin the latest gambit version (4.6.0). Was used sequence
./configure --enable-single-host make make install
The "make check" stop in infinity loop after: ../gsi/gsi -:h4000,~~bin=../bin,~~lib=../lib,~~include=../include -f error.scm < error.scm > test2.out
Anyway. After installation the "gsi" works. "gsc -c" also.
But "gsi -obj" or "gsc -exe" dying in infinity loop (can be terminated by ctrl+c with message *** INTERRUPTED IN ##make-device-port-from-single-device)
If try compile file .c file by gcc there is error: undefined reference to `_WinMain@16'
Also log has allot of /tmp/cco0Sj28.o:test.c:(.text+0x71): undefined reference to `____gstate' /tmp/cco0Sj28.o:test.c:(.text+0x84): undefined reference to `____G_fac' /tmp/cco0Sj28.o:test.c:(.text+0xbc): undefined reference to `____gstate' /tmp/cco0Sj28.o:test.c:(.text+0xd4): undefined reference to `____G_fac' ....
Any ideas?
-- Valeriya
Afficher les réponses par date
The problem appears to be in the implementation of shell-command (which in turn calls open-process).
I don't have a fix yet. Unfortunately, as part of the compilation process, "gsc -obj" and "gsc -exe" need to call open-process (to run the script gambc-cc.bat which actually calls the C compiler).
I will investigate.
Also, to compile the .c files you need to pass a bunch of options to the C compiler. That information is found in bin/gambc-cc.bat . You can also read the manual, but it may contain stale information regarding cygwin.
Marc
On 2011-03-17, at 2:25 PM, Valeriya Pudova wrote:
Hello,
I have compiled with cygwin the latest gambit version (4.6.0). Was used sequence
./configure --enable-single-host make make install
The "make check" stop in infinity loop after: ../gsi/gsi -:h4000,~~bin=../bin,~~lib=../lib,~~include=../include -f error.scm < error.scm > test2.out
Anyway. After installation the "gsi" works. "gsc -c" also.
But "gsi -obj" or "gsc -exe" dying in infinity loop (can be terminated by ctrl+c with message *** INTERRUPTED IN ##make-device-port-from-single-device)
If try compile file .c file by gcc there is error: undefined reference to `_WinMain@16'
Also log has allot of /tmp/cco0Sj28.o:test.c:(.text+0x71): undefined reference to `____gstate' /tmp/cco0Sj28.o:test.c:(.text+0x84): undefined reference to `____G_fac' /tmp/cco0Sj28.o:test.c:(.text+0xbc): undefined reference to `____gstate' /tmp/cco0Sj28.o:test.c:(.text+0xd4): undefined reference to `____G_fac' ....
Any ideas?
-- Valeriya _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Marc,
Is the readtable API that is documented in the Gambit manual the full extent of Gambit's support for customizing the reader?
One of my projects is a novel Lisp implementation. I have a working reader, but it occurred to me that piggybacking on the mature and well-debugged Gambit reader might be a sensible approach. I thought it might mean fewer bugs to fix with less work than maintaining my own reader.
I don't see how to support the lexical syntax I need using only the documented API, though.
If the reader's full API is as documented, I'll just continue to maintain my own reader, but if it's possible to make additional modifications, I might switch to relying on Gambit's reader with my mods.
(Before anyone helpfully suggests various lexing and parsing tools, I'm already aware of them, thanks.)
--me
There is much more extensibility in the Gambit reader. Much of it is not documented because the API is not simple. If you tell me what you want to do I'll give you instructions.
Marc
On 2011-03-18, at 2:41 PM, mikel evins wrote:
Marc,
Is the readtable API that is documented in the Gambit manual the full extent of Gambit's support for customizing the reader?
One of my projects is a novel Lisp implementation. I have a working reader, but it occurred to me that piggybacking on the mature and well-debugged Gambit reader might be a sensible approach. I thought it might mean fewer bugs to fix with less work than maintaining my own reader.
I don't see how to support the lexical syntax I need using only the documented API, though.
If the reader's full API is as documented, I'll just continue to maintain my own reader, but if it's possible to make additional modifications, I might switch to relying on Gambit's reader with my mods.
(Before anyone helpfully suggests various lexing and parsing tools, I'm already aware of them, thanks.)
--me
On Mar 18, 2011, at 2:04 PM, Marc Feeley wrote:
There is much more extensibility in the Gambit reader. Much of it is not documented because the API is not simple. If you tell me what you want to do I'll give you instructions.
Somehow I suspected as much. :-)
I'll reply off-list, because I doubt my requirements are of general interest.
Thanks!
--me
On Fri, Mar 18, 2011 at 02:06:16PM -0500, mikel evins wrote:
On Mar 18, 2011, at 2:04 PM, Marc Feeley wrote:
There is much more extensibility in the Gambit reader. Much of it is not documented because the API is not simple. If you tell me what you want to do I'll give you instructions.
Somehow I suspected as much. :-)
I'll reply off-list, because I doubt my requirements are of general interest.
Actually, I'm pretty interested in that sort of thing! It's far more interesting to me than iPhone-related apps or problems, for example. Not that I mind those terribly; it's just an example of legitimate list traffic of limited interest.
-Joe
Actually, I'm pretty interested in that sort of thing! It's far more interesting to me than iPhone-related apps or problems, for example. Not that I mind those terribly; it's just an example of legitimate list traffic of limited interest.
I second that.
Thank You Marc. Please tell me in future if you will have any success with cygwin issue.
I also played with little .sh file. export GAMBCDIR_INCLUDE=/usr/local/Gambit-C/include/ export GAMBCDIR_LIB=/usr/local/Gambit-C/lib sh gambc-cc.bat exe test.c
That returns only `_WinMain@16' error
On Fri, Mar 18, 2011 at 8:58 PM, Marc Feeley feeley@iro.umontreal.cawrote:
The problem appears to be in the implementation of shell-command (which in turn calls open-process).
I don't have a fix yet. Unfortunately, as part of the compilation process, "gsc -obj" and "gsc -exe" need to call open-process (to run the script gambc-cc.bat which actually calls the C compiler).
I will investigate.
Also, to compile the .c files you need to pass a bunch of options to the C compiler. That information is found in bin/gambc-cc.bat . You can also read the manual, but it may contain stale information regarding cygwin.
Marc
On 2011-03-17, at 2:25 PM, Valeriya Pudova wrote:
Hello,
I have compiled with cygwin the latest gambit version (4.6.0). Was used
sequence
./configure --enable-single-host make make install
The "make check" stop in infinity loop after: ../gsi/gsi -:h4000,~~bin=../bin,~~lib=../lib,~~include=../include -f
error.scm < error.scm > test2.out
Anyway. After installation the "gsi" works. "gsc -c" also.
But "gsi -obj" or "gsc -exe" dying in infinity loop (can be terminated by ctrl+c with message *** INTERRUPTED IN
##make-device-port-from-single-device)
If try compile file .c file by gcc there is error: undefined reference to `_WinMain@16'
Also log has allot of /tmp/cco0Sj28.o:test.c:(.text+0x71): undefined reference to `____gstate' /tmp/cco0Sj28.o:test.c:(.text+0x84): undefined reference to `____G_fac' /tmp/cco0Sj28.o:test.c:(.text+0xbc): undefined reference to `____gstate' /tmp/cco0Sj28.o:test.c:(.text+0xd4): undefined reference to `____G_fac' ....
Any ideas?
-- Valeriya _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
-
Jeremie Lasalle Ratelle -
Joe Doyle Ardent -
Marc Feeley -
mikel evins -
Valeriya Pudova