Re: [Chicken-users] Strange behavior of Chicken Scheme interpreter on Windows 7
Peter, I found the root cause of my issue, it is not related to Chicken Scheme, it's pretty simple. Actually, it took me a long time to realize there is some kind of sandboxing mechanisms in avast! antivirus. It redirect the input/output to some temporary window during the scanning of the binary file. I am sorry for wasting your time! That doesn't make sense. PREFIX is *never* the current directory on Linux. The PREFIX is where you are going to _install_ the program, not where you're compiling it. I made a mistake when writing the sentence. I now understand there is a big difference between the behavior on Windows and Linux. On Linux PREFIX is an option, you can decide to set it, but the default location is a valid directory. Now I am a little bit confused by your answer. 1. PREFIX looks to be mandatory in Chicken and is an absolute path 2. I want to package everything in an archive file which will be in different places on different computers Do you think it can work out-of-the-box playing with environment variables? What will be the restrictions? Regards, Pascal - Mail original - De: Peter Bex peter@xs4all.nl À: comb...@laposte.net Cc: chicken-users@nongnu.org Envoyé: Jeudi 4 Décembre 2014 16:00:26 Objet: Re: [Chicken-users] Strange behavior of Chicken Scheme interpreter on Windows 7 On Tue, Dec 02, 2014 at 03:20:05PM +0100, comb...@laposte.net wrote: Thank you for your fast answer :) My target is to have a standalone archive file (including Chicken + GCC) that I can copy on my USB key and use on different computers. Usage: portable Chicken scheme development environment for Windows without admin privileges. It probably already exist somewhere, but I didn't find the URL. I'm not aware of anything like that. I got something not so far from my needs with chicken-iup prebuilt files and a small batch script which override CHICKEN_INSTALL_PREFIX and CHICKEN_PREFIX. Cool. Perhaps this has something to do with mingw32-64. Did you read the README instructions to invoke mingw32-make with ARCH=x86-64 and use forward slashes in all paths? If not, does that help? If it doesn't help, is it at all possible to do a 32-bit build on 64-bit Windows? If I don't add the option ARCH=x86-64 the compilation phase fails when compiling ASM instructions for apply-hack function. I guess x64 ASM have a different instruction set from 32 bits. Yes, that's what ARCH is for. I thought you were trying to build a 64 bit binary, hence my suggestion. From what I understand, there is no way to cross-compile for Windows 32 bits from a 64 bits host with ming32-64. If you use ARCH=x86-64 it means both HOST and TARGET are 64 bits. I don't think there's a Windows-to-Windows cross build. Did you use mingw 32 bits? Which version? I would like to try on my side. Yeah, I used the 32-bits mingw. I generally just download the latest from the website. Actually I did read the README, but I didn't follow all the instructions: - I didn't set PREFIX, coming from Linux world, I expect it to be the current directory by default That doesn't make sense. PREFIX is *never* the current directory on Linux. The PREFIX is where you are going to _install_ the program, not where you're compiling it. - Since I override 2 variables at execution level, it should have no issue Anyway, I have just tried again to compile with an absolute PREFIX including drive letter and normal slash /. The issue remains. I tried with the 2 compilers. Did you set PREFIX to the target where you are going to install it, or to the directory where the CHICKEN sources are? If the latter, that's probably what's going wrong. Honestly, I don't understand the needs to have an absolute PREFIX. In the common cases, when you want to use unix tools on Windows, you just have to override the PATH locally with batch script. Can you confirm the PREFIX is not mandatory and can be overridden by environment variables at execution level? No, PREFIX is required and I think it really must be an absolute path. Cheers, Peter -- http://www.more-magic.net ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] First call for papers LOPSTR 2015 -- 25th International Symposium on Logic-Based Program Synthesis and Transformation -- Siena, Italy
25th International Symposium on Logic-Based Program Synthesis and Transformation LOPSTR 2015 http://alpha.diism.unisi.it/lopstr15/ University of Siena, Siena, IT, July 13-15, 2015 DEADLINES Abstract submission: April 6, 2015 Paper/Extended abstract submission: April 13, 2015 The aim of the LOPSTR series is to stimulate and promote international research and collaboration on logic-based program development. LOPSTR is open to contributions in logic-based program development in any language paradigm. LOPSTR has a reputation for being a lively, friendly forum for presenting and discussing work in progress. Formal proceedings are produced only after the symposium so that authors can incorporate this feedback in the published papers. The 25th International Symposium on Logic-based Program Synthesis and Transformation (LOPSTR 2015) will be held at the University of Siena, Siena, Italy; previous symposia were held in Canterbury, Madrid, Leuven, Odense, Hagenberg, Coimbra, Valencia, Lyngby, Venice, London, Verona, Uppsala, Madrid, Paphos, London, Venice, Manchester, Leuven, Stockholm, Arnhem, Pisa, Louvain-la-Neuve, and Manchester. LOPSTR 2015 will be co-located with PPDP 2015 (International ACM SIGPLAN Symposium on Principles and Practice of Declarative Programming). Topics of interest cover all aspects of logic-based program development, all stages of the software life cycle, and issues of both programming-in-the-small and programming-in-the-large. Both full papers and extended abstracts describing applications in these areas are especially welcome. Contributions are welcome on all aspects of logic-based program development, including, but not limited to: * synthesis * transformation * specialization * composition * optimization * inversion * specification * analysis and verification * testing and certification * program and model manipulation * transformational techniques in SE * applications and tools Survey papers that present some aspects of the above topics from a new perspective, and application papers that describe experience with industrial applications are also welcome. Papers must describe original work, be written and presented in English, and must not substantially overlap with papers that have been published or that are simultaneously submitted to a journal, conference, or workshop with refereed proceedings. Work that already appeared in unpublished or informally published workshop proceedings may be submitted (please contact the PC chair in case of questions). Important Dates Abstract submission:April 6, 2015 Paper/Extended abstract submission: April 13, 2015 Notification: May 25, 2015 Camera-ready (for electronic pre-proceedings): June 15, 2015 Symposium: July 13-15, 2015 Submission Guidelines Authors should submit an electronic copy of the paper (written in English) in PDF, formatted in the Lecture Notes in Computer Science style. Each submission must include on its first page the paper title; authors and their affiliations; contact author's email; abstract; and three to four keywords which will be used to assist the PC in selecting appropriate reviewers for the paper. Page numbers should appear on the manuscript to help the reviewers in writing their report. Submissions cannot exceed 15 pages including references but excluding well-marked appendices not intended for publication. Reviewers are not required to read the appendices, and thus papers should be intelligible without them. Papers should be submitted via the Easychair submission website for LOPSTR 2015, which you can access through the website of LOPSTR 2015. Proceedings The formal post-conference proceedings will be published by Springer in the Lecture Notes in Computer Science series (to be confirmed). Full papers can be directly accepted for publication in the formal proceedings, or accepted only for presentation at the symposium and inclusion in informal proceedings. After the symposium, all authors of extended abstracts and full papers accepted only for presentation will be invited to revise and/or extend their submissions in the light of the feedback solicited at the symposium. Then, after another round of reviewing, these revised papers may also be published in the formal proceedings. Special journal issue After the symposium, a selection of the best papers will be invited to a special issue of a primary computer science journal. The submissions to the special issue must be substantial extensions of the proceedings versions and will undergo the usual journal reviewing process. Program Committee Slim AbdennadherGerman University of Cairo, Egypt Maria Alpuente
Re: [Chicken-users] Strange behavior of Chicken Scheme interpreter on Windows 7
On 06 Dec 2014, at 13:16, comb...@laposte.net wrote: 1. PREFIX looks to be mandatory in Chicken and is an absolute path 2. I want to package everything in an archive file which will be in different places on different computers Do you think it can work out-of-the-box playing with environment variables? What will be the restrictions? Regards, Pascal I’ve not followed the thread, but it seems that the environment variable CHICKEN_PREFIX is the thing you are looking for. PREFIX sets the default at compilation time. You may also need to set CHICKEN_REPOSITORY if it is not located at CHICKEN_PREFIX/lib/chicken/version. Adding CHICKEN_PREFIX/bin to PATH may also be needed. In short, something like: @echo off set CHICKEN_PREFIX=%CD% set CHICKEN_REPOSITORY=%CHICKEN_PREFIX%\lib\chicken\7 set PATH=%CHICKEN_PREFIX%\bin;%PATH% Save this as setenv.bat in your portable installation dir, cd into it when needed and run setenv.bat. -- Regards, Oleg Art System ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Difference in behaviour with code compiled with csc and code run with csi.
I was experimenting with a coroutine example which i got from the c2 website. see link below for code. http://paste.call-cc.org/paste?id=cf4489b9de4820b330dc34371ea3b73a18115a4b#a0 I get the expected output when I run the code using csi $ csi -ns coroutines.scm HELLO! WORLD! However when i run the executable which i compiled with csc, i get the following unexpected output. Please let me know what I am doing wrong. $ csc coroutines.scm $ ./coroutines HELLO! WORLD! SORRY, I'M OUT Error: dead-coroutine Call history: coroutines.scm:32: yield coroutines.scm:15: call/cc coroutines.scm:16: return coroutines.scm:39: test-coroutine-1 coroutines.scm:12: call/cc coroutines.scm:17: current coroutines.scm:33: display coroutines.scm:34: yield coroutines.scm:15: call/cc coroutines.scm:16: return coroutines.scm:39: test-coroutine-1 coroutines.scm:12: call/cc coroutines.scm:17: current coroutines.scm:35: display coroutines.scm:39: test-coroutine-1 coroutines.scm:10: error -- ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
