Gambit-list Février 2015

gambit-list@iro.umontreal.ca

24 participants
33 discussions

ICFP 2015: Final Call for Papers
by David Van Horn 13 Fév '15

13 Fév '15

===================================================================== 20th ACM SIGPLAN International Conference on Functional Programming ICFP 2015 Vancouver, Canada, August 31 - September 2, 2015 http://www.icfpconference.org/icfp2015 ===================================================================== Important Dates ~~~~~~~~~~~~~~~ Submissions due: Friday, February 27 2015, 23:59 UTC-11 https://icfp15.hotcrp.com/ Author response: Tuesday, April 21, 2015 through Thursday, 23 April, 2015 Notification: Friday, May 1, 2015 Final copy due: Friday, June 12, 2015 Scope ~~~~~ ICFP 2015 seeks original papers on the art and science of functional programming. Submissions are invited on all topics from principles to practice, from foundations to features, and from abstraction to application. The scope includes all languages that encourage functional programming, including both purely applicative and imperative languages, as well as languages with objects, concurrency, or parallelism. Topics of interest include (but are not limited to): * Language Design: concurrency, parallelism, and distribution; modules; components and composition; metaprogramming; type systems; interoperability; domain-specific languages; and relations to imperative, object-oriented, or logic programming. * Implementation: abstract machines; virtual machines; interpretation; compilation; compile-time and run-time optimization; garbage collection and memory management; multi-threading; exploiting parallel hardware; interfaces to foreign functions, services, components, or low-level machine resources. * Software-Development Techniques: algorithms and data structures; design patterns; specification; verification; validation; proof assistants; debugging; testing; tracing; profiling. * Foundations: formal semantics; lambda calculus; rewriting; type theory; monads; continuations; control; state; effects; program verification; dependent types. * Analysis and Transformation: control-flow; data-flow; abstract interpretation; partial evaluation; program calculation. * Applications: symbolic computing; formal-methods tools; artificial intelligence; systems programming; distributed-systems and web programming; hardware design; databases; XML processing; scientific and numerical computing; graphical user interfaces; multimedia and 3D graphics programming; scripting; system administration; security. * Education: teaching introductory programming; parallel programming; mathematical proof; algebra. * Functional Pearls: elegant, instructive, and fun essays on functional programming. * Experience Reports: short papers that provide evidence that functional programming really works or describe obstacles that have kept it from working. If you are concerned about the appropriateness of some topic, do not hesitate to contact the program chair. Abbreviated instructions for authors ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * By Friday, 27 February 2015, 23:59 UTC-11, submit a full paper of at most 12 pages (6 pages for an Experience Report) in standard ACM conference format, including bibliography, figures, and appendices. The deadlines will be strictly enforced and papers exceeding the page limits will be summarily rejected. * Authors have the option to attach supplementary material to a submission, on the understanding that reviewers may choose not to look at it. * Each submission must adhere to SIGPLAN's republication policy, as explained on the web at http://www.sigplan.org/Resources/Policies/Republication * Authors of resubmitted (but previously rejected) papers have the option to attach an annotated copy of the reviews of their previous submission(s), explaining how they have addressed these previous reviews in the present submission. If a reviewer identifies him/herself as a reviewer of this previous submission and wishes to see how his/her comments have been addressed, the program chair will communicate to this reviewer the annotated copy of his/her previous review. Otherwise, no reviewer will read the annotated copies of the previous reviews. Overall, a submission will be evaluated according to its relevance, correctness, significance, originality, and clarity. It should explain its contributions in both general and technical terms, clearly identifying what has been accomplished, explaining why it is significant, and comparing it with previous work. The technical content should be accessible to a broad audience. Functional Pearls and Experience Reports are separate categories of papers that need not report original research results and must be marked as such at the time of submission. Detailed guidelines on both categories are on the conference web site. Proceedings will be published by ACM Press. Authors of accepted submissions will have a choice of one of three ways to manage their publication rights. These choices are described at http://authors.acm.org/main.html Presentations will be videotaped and released online if the presenter consents. The proceedings will be freely available for download from the ACM Digital Library from one week before the start of the conference until two weeks after the conference. Formatting: Submissions must be in PDF format printable in black and white on US Letter sized paper and interpretable by Ghostscript. Papers must adhere to the standard ACM conference format: two columns, nine-point font on a ten-point baseline, with columns 20pc (3.33in) wide and 54pc (9in) tall, with a column gutter of 2pc (0.33in). A suitable document template for LaTeX is available at http://www.sigplan.org/Resources/Author/ Submission: Submissions will be accepted on the web using a link that will be posted at https://icfp15.hotcrp.com/ Improved versions of a paper may be submitted at any point before the submission deadline using the same web interface. Author response: Authors will have a 72-hour period, starting at 0:00 UTC on Tuesday, 21 April 2015, to read reviews and respond to them. ACM Author-Izer is a unique service that enables ACM authors to generate and post links on either their home page or institutional repository for visitors to download the definitive version of their articles from the ACM Digital Library at no charge. Downloads through Author-Izer links are captured in official ACM statistics, improving the accuracy of usage and impact measurements. Consistently linking the definitive version of ACM article should reduce user confusion over article versioning. After your article has been published and assigned to your ACM Author Profile page, please visit http://www.acm.org/publications/acm-author-izer-service to learn how to create your links for free downloads from the ACM DL. Publication date: The official publication date of accepted papers is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. General Chair: Kathleen Fisher Tufts University (USA) Program Chair: John Reppy University of Chicago (USA) Program Committee: Amal Ahmed Northeastern University (USA) Jean-Philippe Bernardy Chalmers University of Technology (Sweden) Matthias Blume Google (USA) William Byrd University of Utah (USA) Andy Gill University of Kansas (USA) Neal Glew Google (USA) Fritz Henglein University of Copenhagen (Denmark) Gabriele Keller University of New South Wales and NICTA (Australia) Andrew Kennedy Microsoft Research Cambridge (UK) Neelakantan Krishnaswami Birmingham University (UK) Daan Leijen Microsoft Research Redmond (USA) Keiko Nakata FireEye Dresden (Germany) Mike Rainey INRIA Rocquencourt (France) Andreas Rossberg Google (Germany) Manuel Serrano INRIA Sophia Antipolis (France) Simon Thompson University of Kent (UK) David Van Horn University of Maryland (USA) Stephanie Weirich University of Pennsylvania (USA)

1 0

[TFP 2015] 2nd call for papers
by Peter Achten 13 Fév '15

13 Fév '15

----------------------------- S E C O N D C A L L F O R P A P E R S ----------------------------- ======== TFP 2015 =========== 16th Symposium on Trends in Functional Programming June 3-5, 2015 Inria Sophia Antipolis, France http://tfp2015.inria.fr/ The symposium on Trends in Functional Programming (TFP) is an international forum for researchers with interests in all aspects of functional programming, taking a broad view of current and future trends in the area. It aspires to be a lively environment for presenting the latest research results, and other contributions (see below). Authors of draft papers will be invited to submit revised papers based on the feedback receive at the symposium. A post-symposium refereeing process will then select a subset of these articles for formal publication. The selected revised papers will be published as a Springer Lecture Notes in Computer Science (www.springer.com/lncs) volume. TFP 2015 will be the main event of a pair of functional programming events. TFP 2015 will be accompanied by the International Workshop on Trends in Functional Programming in Education (TFPIE), which will take place on June 2nd. The TFP symposium is the heir of the successful series of Scottish Functional Programming Workshops. Previous TFP symposia were held in * Edinburgh (Scotland) in 2003; * Munich (Germany) in 2004; * Tallinn (Estonia) in 2005; * Nottingham (UK) in 2006; * New York (USA) in 2007; * Nijmegen (The Netherlands) in 2008; * Komarno (Slovakia) in 2009; * Oklahoma (USA) in 2010; * Madrid (Spain) in 2011; * St. Andrews (UK) in 2012; * Provo (Utah, USA) in 2013; * and in Soesterberg (The Netherlands) in 2014. For further general information about TFP please see the TFP homepage. (http://www.tifp.org/). == INVITED SPEAKER == TFP is pleased to announce a talk by the following invited speaker: * Laurence Rideau is a researcher at INRIA and is interested in the semantics of programming languages , the formal methods, and the verification tools for programs and mathematical proofs. She participated in the beginnings of the Compcert project (certified compiler), and is part of the Component Mathematical team in the MSR-INRIA joint laboratory, who performed the formalization of the Feit-Thompson theorem successfully. Thirty years ago, computers barged in mathematics with the famous proof of the Four Color Theorem. Initially limited to simple calculation, their role is now expanding to the reasoning whose complexity is beyond the capabilities of most humans, as the proof of the classification of finite simple groups. We present our large collaborative adventure around the formalization of the Feit-Thompson theorem (http://en.wikipedia.org/wiki/Feit%E2%80%93Thompson_theorem) that is a first step to the classification of finite groups and that uses a palette of methods and techniques that range from formal logic to software (and mathematics) engineering. == SCOPE == The symposium recognizes that new trends may arise through various routes. As part of the Symposium's focus on trends we therefore identify the following five article categories. High-quality articles are solicited in any of these categories: Research Articles: leading-edge, previously unpublished research work Position Articles: on what new trends should or should not be Project Articles: descriptions of recently started new projects Evaluation Articles: what lessons can be drawn from a finished project Overview Articles: summarizing work with respect to a trendy subject Articles must be original and not simultaneously submitted for publication to any other forum. They may consider any aspect of functional programming: theoretical, implementation-oriented, or experience-oriented. Applications of functional programming techniques to other languages are also within the scope of the symposium. Topics suitable for the symposium include: Functional programming and multicore/manycore computing Functional programming in the cloud High performance functional computing Extra-functional (behavioural) properties of functional programs Dependently typed functional programming Validation and verification of functional programs Debugging and profiling for functional languages Functional programming in different application areas: security, mobility, telecommunications applications, embedded systems, global computing, grids, etc. Interoperability with imperative programming languages Novel memory management techniques Program analysis and transformation techniques Empirical performance studies Abstract/virtual machines and compilers for functional languages (Embedded) domain specific languages New implementation strategies Any new emerging trend in the functional programming area If you are in doubt on whether your article is within the scope of TFP, please contact the TFP 2015 program chair, Manuel Serrano. == BEST PAPER AWARDS == To reward excellent contributions, TFP awards a prize for the best paper accepted for the formal proceedings. TFP traditionally pays special attention to research students, acknowledging that students are almost by definition part of new subject trends. A student paper is one for which the authors state that the paper is mainly the work of students, the students are listed as first authors, and a student would present the paper. A prize for the best student paper is awarded each year. In both cases, it is the PC of TFP that awards the prize. In case the best paper happens to be a student paper, that paper will then receive both prizes. == SPONSORS == TFP is financially supported by <to be announced> == PAPER SUBMISSIONS == Acceptance of articles for presentation at the symposium is based on a lightweight peer review process of extended abstracts (4 to 10 pages in length) or full papers (20 pages). The submission must clearly indicate which category it belongs to: research, position, project, evaluation, or overview paper. It should also indicate which authors are research students, and whether the main author(s) are students. A draft paper for which ALL authors are students will receive additional feedback by one of the PC members shortly after the symposium has taken place. We use EasyChair for the refereeing process. Papers must be submitted at: https://easychair.org/conferences/?conf=tfp2015 Papers must be written in English, and written using the LNCS style. For more information about formatting please consult the Springer LNCS web site: http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0 == IMPORTANT DATES == Submission of draft papers: March 17, 2015 Notification: March 24, 2015 Registration: April 7, 2015 TFP Symposium: June 3-5, 2015 Student papers feedback: June 9, 2015 Submission for formal review: July 1, 2015 Notification of acceptance: September 8, 2015 Camera ready paper: October 8, 2015 == PROGRAM COMMITTEE == Janis Voigtländer University of Bonn, DE Scott Owens University of Kent, UK Neil Sculthorpe Swansea University, UK Colin Runciman University of York, UK Manuel Serrano Inria (PC chair), FR Rinus Plasmeijer University of Nijmegen, NL Tomas Petricek University of Cambridge, UK Marco T. Morazan Seton Hall University, USA Wolfgang De Meuter Vrije Universiteit Brussel, BE Michel Mauny Ensta ParisTech, FR Sam Lindley The University of Edinburgh, UK Daan Leijen Microsoft, USA Jurriaan Hage Utrecht University, NL Andy Gill University of Kansas, USA Thomas Gazagnaire University of Cambrige, UK Lars-Ake Fredlund Universidad Politécnica de Madrid, ES Jean-Christophe Filliatre Université Paris Sud Orsay, FR Marc Feeley Université de Montréal, CA Olaf Chitil University of Kent, UK Edwin Brady University of St Andrews, UK

1 0

Re: [gambit-list] Dump a .c file into another program's structure and compile it from another compiler?
by Mikael 12 Fév '15

12 Fév '15

Great. Remember to write up your findings on the Wiki. 2015-02-12 8:43 GMT+05:30 Colin Gilbert <colingilbert86(a)gmail.com>: > Hi, I would like to add a quick addition to method #2: you need to add > "-lm" at the end or else you'll get endless compiler errors about undefined > references to standard math libraries. The full command is: > > ``` > gcc -O1 -DHAVE_ERRNO_H -DHAVE_STDLIB_H -DHAVE_STRING_H > -D___VOIDSTAR_WIDTH=8 -D___MAX_CHR=0x10ffff -D___BOOL=int -D___SINGLE_VM > -D___SINGLE_THREADED_VMS -D___USE_NO_THREAD_SYSTEM > -D___NO_THREAD_LOCAL_STORAGE_ > CLASS -D___LABEL_ACCESS_OLD -D___SINGLE_HOST > -D___GAMBCDIR='"/usr/local/Gambit-C"' *.c -o hello.exe -lm > > ``` > > On 11 February 2015 at 18:38, Colin Gilbert <colingilbert86(a)gmail.com> > wrote: > >> Dr Feeley, >> >> Your prompt reply is very much appreciated. >> >> Once request I'd like to make, however: If you used C99 to compile your >> resulting files (or Gambit itself), would it automatically use C99's >> built-in types and not require __VOIDSTAR_WIDTH? >> >> >> Thank you. >> >> Colin, if you wanted to put a link to this Mailing list archive page on >>> the Wiki would be great, thanks. >>> >>> >>> >>> 2015-02-11 20:01 GMT+05:30 Marc Feeley <feeley(a)iro.umontreal.ca>: >>> >>>> >>>> > On Feb 10, 2015, at 11:40 PM, Colin Gilbert <colingilbert86(a)gmail.com> >>>> wrote: >>>> > >>>> > Hi, >>>> > >>>> > Pardon the silly noob question, but I've been trying to use Gambit to >>>> quickly write up a small submodule, and then use each target's native >>>> compiler to embed it into the build. Unfortunately, I am getting link >>>> errors: >>>> > >>>> > Is my my mini program: >>>> > hello.scm: (display "hello") (newline) >>>> > >>>> > Here is what happens when I try to use it. >>>> > >>>> > >> gsc -c hello.scm >>>> > *** INFO -- loading syntax expander >>>> > >>>> > >> gcc hello.c >>>> > >>>> > cc hello.c >>>> > /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.3/../../../../lib64/crt1.o: In >>>> function `_start': >>>> > (.text+0x20): undefined reference to `main' >>>> > /tmp/ccpGbiFh.o: In function `___H__20_hello': >>>> > hello.c:(.text+0x8d): undefined reference to `___gstate0' >>>> > hello.c:(.text+0xd4): undefined reference to `___gstate0' >>>> > hello.c:(.text+0xee): undefined reference to `___G_display' >>>> > hello.c:(.text+0x132): undefined reference to `___G_display' >>>> > hello.c:(.text+0x144): undefined reference to `___gstate0' >>>> > hello.c:(.text+0x176): undefined reference to `___gstate0' >>>> > hello.c:(.text+0x194): undefined reference to `___G_newline' >>>> > hello.c:(.text+0x1d5): undefined reference to `___G_newline' >>>> > hello.c:(.text+0x1e7): undefined reference to `___gstate0' >>>> > /tmp/ccpGbiFh.o: In function `___setup_mod': >>>> > hello.c:(.text+0x25c): undefined reference to `___G__20_hello' >>>> > /tmp/ccpGbiFh.o: In function `___init_mod': >>>> > hello.c:(.text+0x26f): undefined reference to `___gstate0' >>>> > hello.c:(.text+0x281): undefined reference to `___G__20_hello' >>>> > /tmp/ccpGbiFh.o: In function `____20_hello': >>>> > hello.c:(.text+0x29b): undefined reference to `___S_hello' >>>> > collect2: error: ld returned 1 exit status >>>> > >>>> > I tried using -link, -flat,-link -flat but no real difference. >>>> > >>>> > What files need to be present before you can compile the code >>>> natively? >>>> >>>> The default Gambit-C build procedure is designed for building on the >>>> same type of platform where the executable will be run. For portability to >>>> different platforms, the build procedure uses a "configure" script that >>>> determines various properties of the platform (the existence of various >>>> system header files, the width of pointers, the type of operating system, >>>> etc). The "configure" script will adapt the makefiles and also fill in >>>> some blanks in include/gambit.h.in to generate the Gambit header file >>>> include/gambit.h (and similarly for include/config.h.in). >>>> >>>> In a situation with multiple target platforms, the configure script >>>> would have to be run on each target platform to determine the properties of >>>> the platform and adapt the include/gambit.h.in file and the include/ >>>> config.h.in file accordingly for compiling on that platform. >>>> >>>> I sense that you are looking for a different approach. I assume in the >>>> following that you want to compile a Scheme app into a set of .c and .h >>>> files that you can compile on multiple target platforms with little or no >>>> changes and no configure script or equivalent procedure. >>>> >>>> Here are two approches. The first assumes that your target platforms >>>> share similar characteristics with the development platform (same OS, same >>>> processor word size) so that the gambit.h and config.h files produced by >>>> the configure script are OK. The second approach uses options on the C >>>> compiler's command line to fill in the information that the configure >>>> script normally determines. >>>> >>>> So we start with compiling Gambit on the development platform: >>>> >>>> % mkdir embed >>>> % cd embed >>>> % git clone http://github.com/feeley/gambit.git >>>> % cd gambit >>>> % ./configure --enable-single-host >>>> % make from-scratch >>>> % make install >>>> % cd .. >>>> >>>> Now we use the first approach that reuses the development platform's >>>> gambit.h and config.h files. Note that we compile all the .c files (from >>>> the Gambit library and the Scheme app) in one call of the C compiler (this >>>> could be changed to a seperate compilation of each .c file). In any case >>>> it takes less than a minute to compile everything (this is with GNU gcc >>>> 4.9.2 on a fast machine with an SSD). >>>> >>>> % mkdir test1 >>>> % cd test1 >>>> % echo '(println "hello!")' > hello.scm >>>> % gsc -c hello.scm # generate hello.c from hello.scm >>>> % gsc -link hello.c # generate hello_.c from hello.c >>>> % cp ../gambit/include/stamp.h . >>>> % cp ../gambit/include/gambit.h . >>>> % cp ../gambit/include/config.h . >>>> % cp ../gambit/lib/*.c . >>>> % cp ../gambit/lib/*.h . >>>> % time gcc -O1 -DHAVE_CONFIG_H *.c -o hello.exe >>>> >>>> real 0m47.653s >>>> user 0m46.124s >>>> sys 0m1.443s >>>> % ./hello.exe >>>> hello! >>>> % cd test1 >>>> % ls -l hello.exe >>>> -rwxr-xr-x+ 1 feeley staff 5187576 Feb 11 08:09 hello.exe >>>> % strip hello.exe >>>> % ls -l hello.exe >>>> -rwxr-xr-x+ 1 feeley staff 4566440 Feb 11 08:09 hello.exe >>>> % cd .. >>>> >>>> Now for the second approach. Note that the gambit.h file is simply a >>>> copy of the gambit.h.in file. The "blanks" in that file (normally >>>> filled in by the configure script) are filled in with C compiler options >>>> (-D___VOIDSTAR_WIDTH=8 for a 64 bit processor, D___MAX_CHR=0x10ffff for >>>> full Unicode support, etc). Similarly, the information in the config.h >>>> file is specified with C compiler options (-DHAVE_ERRNO_H to indicate that >>>> errno.h is available, etc). >>>> >>>> % mkdir test2 >>>> % cd test2 >>>> % echo '(println "hello!")' > hello.scm >>>> % gsc -c hello.scm # generate hello.c from hello.scm >>>> % gsc -link hello.c # generate hello_.c from hello.c >>>> % cp ../gambit/include/gambit.h.in gambit.h >>>> % cp ../gambit/include/stamp.h . >>>> % cp ../gambit/lib/*.c . >>>> % cp ../gambit/lib/*.h . >>>> % time gcc -O1 -DHAVE_ERRNO_H -DHAVE_STDLIB_H -DHAVE_STRING_H >>>> -D___VOIDSTAR_WIDTH=8 -D___MAX_CHR=0x10ffff -D___BOOL=int -D___SINGLE_VM >>>> -D___SINGLE_THREADED_VMS -D___USE_NO_THREAD_SYSTEM >>>> -D___NO_THREAD_LOCAL_STORAGE_CLASS -D___LABEL_ACCESS_OLD -D___SINGLE_HOST >>>> -D___GAMBCDIR='"/usr/local/Gambit-C"' *.c -o hello.exe >>>> >>>> real 0m48.342s >>>> user 0m46.860s >>>> sys 0m1.387s >>>> % ./hello.exe >>>> hello! >>>> % ls -l hello.exe >>>> -rwxr-xr-x+ 1 feeley staff 5150656 Feb 11 08:42 hello.exe >>>> % strip hello.exe >>>> % ls -l hello.exe >>>> -rwxr-xr-x+ 1 feeley staff 4532824 Feb 11 08:43 hello.exe >>>> % cd .. >>>> >>>> So once compiled, a Scheme app can be seen as a set of .c and .h files >>>> and building the app requires a bit of knowledge of the characteristics of >>>> the target platform (but not very much, in fact the only critical one is >>>> ___VOIDSTAR_WIDTH = sizeof(void*), which has to be known at C macro >>>> expansion time to adapt some of the macros defined in gambit.h). >>>> >>>> Note that the need to specify -D___LABEL_ACCESS_OLD and >>>> -D___GAMBCDIR='"/usr/local/Gambit-C"' (and maybe a few others) will go away >>>> in a future release of Gambit as they could have default values. >>>> >>>> Marc >>>> >>>> >>>> _______________________________________________ >>>> Gambit-list mailing list >>>> Gambit-list(a)iro.umontreal.ca >>>> https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list >>>> >>>> >>> >> >

2 1

Problem building univ-lib for JS
by Blake McBride 11 Fév '15

11 Fév '15

Greetings, I built the latest Gambit and pulled univ-lib. The makefile in univ-lib first compiles ap.scm to app.js. It then tries to run ap.js with d8. Two things: 1. Could we use node instead of d8? 2. When I run it with node I get: /home/gambit.git/univ-lib/app.js:533 gambit_r1 = Gambit_js2scm(jsfn); ^ ReferenceError: Gambit_js2scm is not defined at gambit_bb1__20_app (/home/blake/z/gambit.git/univ-lib/app.js:533:15) at gambit_trampoline (/home/blake/z/gambit.git/univ-lib/app.js:333:10) at Object.<anonymous> (/home/blake/z/gambit.git/univ-lib/app.js:778:1) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:929:3 I can't find any definition for Gambit_js2scm(). Not sure what to do. Thanks. Blake McBride

3 6

Dump a .c file into another program's structure and compile it from another compiler?
by Colin Gilbert 11 Fév '15

11 Fév '15

Hi, Pardon the silly noob question, but I've been trying to use Gambit to quickly write up a small submodule, and then use each target's native compiler to embed it into the build. Unfortunately, I am getting link errors: Is my my mini program: hello.scm: (display "hello") (newline) Here is what happens when I try to use it. >> gsc -c hello.scm *** INFO -- loading syntax expander >> gcc hello.c cc hello.c /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.3/../../../../lib64/crt1.o: In function `_start': (.text+0x20): undefined reference to `main' /tmp/ccpGbiFh.o: In function `___H__20_hello': hello.c:(.text+0x8d): undefined reference to `___gstate0' hello.c:(.text+0xd4): undefined reference to `___gstate0' hello.c:(.text+0xee): undefined reference to `___G_display' hello.c:(.text+0x132): undefined reference to `___G_display' hello.c:(.text+0x144): undefined reference to `___gstate0' hello.c:(.text+0x176): undefined reference to `___gstate0' hello.c:(.text+0x194): undefined reference to `___G_newline' hello.c:(.text+0x1d5): undefined reference to `___G_newline' hello.c:(.text+0x1e7): undefined reference to `___gstate0' /tmp/ccpGbiFh.o: In function `___setup_mod': hello.c:(.text+0x25c): undefined reference to `___G__20_hello' /tmp/ccpGbiFh.o: In function `___init_mod': hello.c:(.text+0x26f): undefined reference to `___gstate0' hello.c:(.text+0x281): undefined reference to `___G__20_hello' /tmp/ccpGbiFh.o: In function `____20_hello': hello.c:(.text+0x29b): undefined reference to `___S_hello' collect2: error: ld returned 1 exit status I tried using -link, -flat,-link -flat but no real difference. What files need to be present before you can compile the code natively?

3 3

Re: [gambit-list] Dump a .c file into another program's structure and compile it from another compiler?
by Mikael 11 Fév '15

11 Fév '15

Sure. I think the solution is really simple. So what is it you want to do, you have a file xyz.scm that you want to compile to >1 target platforms? If so, just to the GAMBC_CC_VERBOSE thing I suggested to get the gcc + ld commands for your local platform. Then just adapt those for your respective target platforms. To then get the full set of C files for xyz.scm, do (compile-file "xyz.scm") and then I think (link-incremental "mylinkfile.c" '("xyz")) in the same directory, and the full set of C files for your program will bemylinkfile.c + xyz.c . To compile those, gcc needs -I with your Gambit-C/include directory, and ld needs something like -lgsc , and maybe some define is needed - again the GAMBC_CC_VERBOSE thing clarifies that. I believe compile-file corresponds to the -c gsc option, and perhaps link-incremental is the -incremental option. Note that the link file production procedure requires both the total set of C file inputs, and the output filename for the link file, so (at least) two arguments. However, I wanted to express my gratitude for this quick reply; it will > definitely be a pleasure to write an article about this problem's solution, > if I find the solution. Now, I am confident that this is a problem that > interests a number of people here and I eagerly await your replies. > > As far as gambit is concerned, I poked around the internet and kept on >> trying a few more incantations. Presently, I have a deadline so "real work" >> has to take priority :( >> >> Alvaro (CC) knows how to do this. He's in Europe. I believe he will be >>> able to respond to you the next 3-4 hours. >>> >>> Colin, when you know the answer, please write it up on the wiki. The >>> reason you are experiencing this now is because others before you did not >>> write it up. >>> >>> Where are you? >>> >>> >>> I tried various other variations. No dice. It's a shame such an option >>>> isn't immediately apparent, as Gambit's biggest usecase is embeddding. :( >>>> Could the Mark give us an answer? >>>> >>>> When you figured the answer, please write it up on the wiki for >>>>> instance a new page "How file compilation to C and to binary and link files >>>>> and linking fit together". I believe your issue is either not having >>>>> gambit.h included, or not having gambc linked in, or having your link file >>>>> situation messed up - basically when compiling to binary or dylib (dylib is >>>>> what |load| takes as binary file input), Gambit will produce a link file >>>>> for properly exporting identifiers, and when you try to compile without >>>>> one, you get every possible error. There are examples in the manual. >>>>> >>>>> The Gambit command line arguments for compilation e.g "-c" map >>>>> internally to compile-file-to-c etc., other to link-incremental etc., so >>>>> there are always double ways to do these things. >>>>> >>>>> Hi, >>>>>> >>>>>> Pardon the silly noob question, but I've been trying to use Gambit to >>>>>> quickly write up a small submodule, and then use each target's native >>>>>> compiler to embed it into the build. Unfortunately, I am getting link >>>>>> errors: >>>>>> >>>>>> Is my my mini program: >>>>>> hello.scm: (display "hello") (newline) >>>>>> >>>>>> Here is what happens when I try to use it. >>>>>> >>>>>> >> gsc -c hello.scm >>>>>> *** INFO -- loading syntax expander >>>>>> >>>>>> >> gcc hello.c >>>>>> >>>>>> cc hello.c >>>>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.3/../../../../lib64/crt1.o: In >>>>>> function `_start': >>>>>> (.text+0x20): undefined reference to `main' >>>>>> /tmp/ccpGbiFh.o: In function `___H__20_hello': >>>>>> hello.c:(.text+0x8d): undefined reference to `___gstate0' >>>>>> hello.c:(.text+0xd4): undefined reference to `___gstate0' >>>>>> hello.c:(.text+0xee): undefined reference to `___G_display' >>>>>> hello.c:(.text+0x132): undefined reference to `___G_display' >>>>>> hello.c:(.text+0x144): undefined reference to `___gstate0' >>>>>> hello.c:(.text+0x176): undefined reference to `___gstate0' >>>>>> hello.c:(.text+0x194): undefined reference to `___G_newline' >>>>>> hello.c:(.text+0x1d5): undefined reference to `___G_newline' >>>>>> hello.c:(.text+0x1e7): undefined reference to `___gstate0' >>>>>> /tmp/ccpGbiFh.o: In function `___setup_mod': >>>>>> hello.c:(.text+0x25c): undefined reference to `___G__20_hello' >>>>>> /tmp/ccpGbiFh.o: In function `___init_mod': >>>>>> hello.c:(.text+0x26f): undefined reference to `___gstate0' >>>>>> hello.c:(.text+0x281): undefined reference to `___G__20_hello' >>>>>> /tmp/ccpGbiFh.o: In function `____20_hello': >>>>>> hello.c:(.text+0x29b): undefined reference to `___S_hello' >>>>>> collect2: error: ld returned 1 exit status >>>>>> >>>>>> I tried using -link, -flat,-link -flat but no real difference. >>>>>> >>>>>> What files need to be present before you can compile the code >>>>>> natively? >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Gambit-list mailing list >>>>>> Gambit-list(a)iro.umontreal.ca >>>>>> https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list >>>>>> >>>>>> >>>>> >>>> >>> >> >

1 0

Problems building Gambit-C
by Steve Graham 10 Fév '15

10 Fév '15

On a Linux Mint 17.1 system, used git to download new version of Gambit. When I run ./configure, I get the following: steve@steve-Satellite-L555D /opt/gambit $ ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/opt/gambit': configure: error: C compiler cannot create executables See `config.log' for more details steve@steve-Satellite-L555D /opt/gambit $ The contents of config.log are: steve@steve-Satellite-L555D /opt/gambit $ cat config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by Gambit-C configure v4.7.4, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = steve-Satellite-L555D uname -m = x86_64 uname -r = 3.13.0-37-generic uname -s = Linux uname -v = #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 /usr/bin/uname -p = x86_64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /usr/local/games ## ----------- ## ## Core tests. ## ## ----------- ## configure:2825: checking build system type configure:2839: result: x86_64-unknown-linux-gnu configure:2859: checking host system type configure:2872: result: x86_64-unknown-linux-gnu configure:2892: checking target system type configure:2905: result: x86_64-unknown-linux-gnu configure:3143: checking for gcc configure:3159: found /usr/bin/gcc configure:3170: result: gcc configure:3399: checking for C compiler version configure:3408: gcc --version >&5 gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3419: $? = 0 configure:3408: gcc -v >&5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) configure:3419: $? = 0 configure:3408: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:3419: $? = 4 configure:3408: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion' gcc: fatal error: no input files compilation terminated. configure:3419: $? = 4 configure:3439: checking whether the C compiler works configure:3461: gcc conftest.c >&5 /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find -lc /usr/bin/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status configure:3465: $? = 1 configure:3503: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "Gambit-C" | #define PACKAGE_TARNAME "gambc-v4_7_4" | #define PACKAGE_VERSION "v4.7.4" | #define PACKAGE_STRING "Gambit-C v4.7.4" | #define PACKAGE_BUGREPORT "gambit(a)iro.umontreal.ca" | #define PACKAGE_URL "" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3508: error: in `/opt/gambit': configure:3510: error: C compiler cannot create executables See `config.log' for more details ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_build=x86_64-unknown-linux-gnu ac_cv_env_CCC_set= ac_cv_env_CCC_value= ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_CXXCPP_set= ac_cv_env_CXXCPP_value= ac_cv_env_CXXFLAGS_set= ac_cv_env_CXXFLAGS_value= ac_cv_env_CXX_set= ac_cv_env_CXX_value= ac_cv_env_LDFLAGS_set= ac_cv_env_LDFLAGS_value= ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_XMKMF_set= ac_cv_env_XMKMF_value= ac_cv_env_build_alias_set= ac_cv_env_build_alias_value= ac_cv_env_host_alias_set= ac_cv_env_host_alias_value= ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_host=x86_64-unknown-linux-gnu ac_cv_prog_ac_ct_CC=gcc ac_cv_target=x86_64-unknown-linux-gnu ## ----------------- ## ## Output variables. ## ## ----------------- ## AR='' BAT_EXTENSION='' BAT_EXTENSION_BAT='' BAT_EXTENSION_MF='' BAT_EXTENSION_SH='' BUILD_DYN='' BUILD_DYN_BAT='' BUILD_DYN_ECHO='' BUILD_DYN_ECHO_BAT='' BUILD_DYN_MF='' BUILD_DYN_SH='' BUILD_EXE='' BUILD_EXE_BAT='' BUILD_EXE_ECHO='' BUILD_EXE_ECHO_BAT='' BUILD_EXE_MF='' BUILD_EXE_SH='' BUILD_LIB='' BUILD_LIB_BAT='' BUILD_LIB_ECHO='' BUILD_LIB_ECHO_BAT='' BUILD_LIB_MF='' BUILD_LIB_SH='' BUILD_OBJ='' BUILD_OBJ_BAT='' BUILD_OBJ_ECHO='' BUILD_OBJ_ECHO_BAT='' BUILD_OBJ_MF='' BUILD_OBJ_SH='' CC='gcc' CFLAGS='' COMPILATION_OPTIONS='' CONF_BOOL='' CONF_MAX_CHR='' CONF_SINGLE_MULTIPLE_THREADED_VMS='' CONF_SINGLE_MULTIPLE_VMS='' CONF_THREAD_LOCAL_STORAGE_CLASS='' CONF_THREAD_SYSTEM='' CONF_VOIDSTAR_WIDTH='' CPP='' CPPFLAGS='' CXX='' CXXCPP='' CXXFLAGS='' C_COMPILER='' C_COMPILER_BAT='' C_COMPILER_MF='' C_COMPILER_SH='' C_COMP_CLANG='' C_COMP_GNUC='' C_COMP_LLVM='' C_COMP_VISUALC='' C_PREPROC='' C_PREPROC_BAT='' C_PREPROC_MF='' C_PREPROC_SH='' DASH_G='' DASH_KPIC='' DASH_O1='' DASH_O2='' DASH_OPT_IEEE_NaN_inf_ON='' DASH_OPT_IEEE_comparisons_ON='' DASH_OPT_Olimit_0='' DASH_TENV_large_GOT='' DASH_W='' DASH_Wall='' DASH_Wno_unused='' DASH_Wno_write_strings='' DASH_b='' DASH_bundle='' DASH_call_shared='' DASH_dynamiclib='' DASH_expect_unresolved='' DASH_fPIC='' DASH_fbranch_probabilities='' DASH_flat_namespace_undefined_suppress='' DASH_fmodulo_sched='' DASH_fno_common='' DASH_fno_keep_inline_dllexport='' DASH_fno_math_errno='' DASH_fno_move_loop_invariants='' DASH_fno_strict_aliasing='' DASH_fno_trapping_math='' DASH_fomit_frame_pointer='' DASH_fpic='' DASH_fprofile_arcs='' DASH_freschedule_modulo_scheduled_loops='' DASH_fschedule_insns2='' DASH_ftest_coverage='' DASH_fullwarn='' DASH_fwrapv='' DASH_g='' DASH_ieee='' DASH_mieee='' DASH_mieee_fp='' DASH_mieee_with_inexact='' DASH_no_cpp_precomp='' DASH_p='' DASH_pg='' DASH_rdynamic='' DASH_shared='' DASH_woff_1110_1174_1209_1552_3201='' DASH_xO2='' DEFS='' DEFS_BAT='' DEFS_DYN='-D___DYNAMIC' DEFS_DYN_BAT='' DEFS_DYN_MF='' DEFS_DYN_SH='' DEFS_EXE='' DEFS_EXE_BAT='' DEFS_EXE_MF='' DEFS_EXE_SH='' DEFS_LIB='' DEFS_LIB_BAT='' DEFS_LIB_MF='' DEFS_LIB_SH='' DEFS_MF='' DEFS_OBJ='' DEFS_OBJ_BAT='' DEFS_OBJ_MF='' DEFS_OBJ_SH='' DEFS_SH='' ECHO_C='' ECHO_N='-n' ECHO_T='' EGREP='' ENABLE_ABSOLUTE_SHARED_LIBS='' ENABLE_COMPILER_NAME='' ENABLE_GUIDE='' ENABLE_INTERPRETER_NAME='' ENABLE_MULTIPLE_VERSIONS='' ENABLE_SHARED='' ENABLE_SYMLINKS='' ENABLE_VERSIONED_SHARED_LIBS='' EXEEXT='' EXE_EXTENSION='' EXE_EXTENSION_BAT='' EXE_EXTENSION_MF='' EXE_EXTENSION_SH='' FIXLIB='' FLAGS_DYN='' FLAGS_DYN_BAT='' FLAGS_DYN_MF='' FLAGS_DYN_SH='' FLAGS_EXE='' FLAGS_EXE_BAT='' FLAGS_EXE_MF='' FLAGS_EXE_SH='' FLAGS_LIB='' FLAGS_LIB_BAT='' FLAGS_LIB_MF='' FLAGS_LIB_SH='' FLAGS_OBJ='' FLAGS_OBJ_BAT='' FLAGS_OBJ_MF='' FLAGS_OBJ_SH='' GAMBCGSCLIB='' GAMBCGSCLIB_BAT='' GAMBCGSCLIB_MF='' GAMBCGSCLIB_SH='' GAMBCGSILIB='' GAMBCGSILIB_BAT='' GAMBCGSILIB_MF='' GAMBCGSILIB_SH='' GAMBCLIB='' GAMBCLIB_BAT='' GAMBCLIB_DEFS='' GAMBCLIB_DEFS_BAT='' GAMBCLIB_DEFS_MF='' GAMBCLIB_DEFS_SH='' GAMBCLIB_MF='' GAMBCLIB_SH='' GCC_42_OR_43='' GIT='' GREP='' HAVE_SPECIAL_CC='' HAVE_SPECIAL_CXX='' HELP_BROWSER='' HG='' INSTALL='' INSTALL_DATA='' INSTALL_LIB='' INSTALL_PROGRAM='' LDFLAGS='' LIBOBJS='' LIBS='' LIBS_BAT='' LIBS_MF='' LIBS_SH='' LIB_EXTENSION='' LIB_EXTENSION_BAT='' LIB_EXTENSION_MF='' LIB_EXTENSION_SH='' LIB_MAJOR_VERSION_SUFFIX='' LIB_PREFIX='' LIB_PREFIX_BAT='' LIB_PREFIX_MF='' LIB_PREFIX_SH='' LIB_VERSION_SUFFIX='' LINK='' LINK_FOR_INSTALL='' LINK_FOR_INSTALL_GSC_LIBS='' LINK_FOR_INSTALL_GSI_LIBS='' LN_S='' LTLIBOBJS='' MAKE_LIBRARY='' MAKE_LIBRARY_FOR_INSTALL='' MAKE_LIBRARY_FOR_INSTALL_LIBS='' OBJEXT='' OBJ_EXTENSION='' OBJ_EXTENSION_BAT='' OBJ_EXTENSION_MF='' OBJ_EXTENSION_SH='' OS_WIN32='' PACKAGE_BUGREPORT='gambit(a)iro.umontreal.ca' PACKAGE_NAME='Gambit-C' PACKAGE_SHORTNAME='gambc' PACKAGE_STRING='Gambit-C v4.7.4' PACKAGE_TARNAME='gambc-v4_7_4' PACKAGE_URL='' PACKAGE_VERSION='v4.7.4' PATH_SEPARATOR=':' POSSIBLE_LLVM_GCC_LABEL_VALUES_BUG='' QTINCPATH='' RANLIB='' RC='' RTLIBSUBSYS='' SETDLPATH='' SETDLPATHBOOT='' SET_MAKE='' SHELL='/bin/bash' XMKMF='' X_CFLAGS='' X_EXTRA_LIBS='' X_FLAGS='' X_LIBS='' X_PRE_LIBS='' ac_ct_CC='gcc' ac_ct_CXX='' bat='' bindir='${exec_prefix}/bin' build='x86_64-unknown-linux-gnu' build_alias='' build_cpu='x86_64' build_os='linux-gnu' build_vendor='unknown' datadir='${datarootdir}' datarootdir='${prefix}/share' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' dvidir='${docdir}' emacsdir='' exe='' exec_prefix='NONE' host='x86_64-unknown-linux-gnu' host_alias='' host_cpu='x86_64' host_os='linux-gnu' host_vendor='unknown' htmldir='${docdir}' includedir='${prefix}/include' infodir='${datarootdir}/info' libdir='${exec_prefix}/lib' libexecdir='${exec_prefix}/libexec' localedir='${datarootdir}/locale' localstatedir='${prefix}/var' mandir='${datarootdir}/man' obj='' oldincludedir='/usr/include' pdfdir='${docdir}' prefix='NONE' program_transform_name='s,x,x,' psdir='${docdir}' sbindir='${exec_prefix}/sbin' sharedstatedir='${prefix}/com' srcdirpfx='' sysconfdir='${prefix}/etc' target='x86_64-unknown-linux-gnu' target_alias='' target_cpu='x86_64' target_os='linux-gnu' target_vendor='unknown' ## ----------- ## ## confdefs.h. ## ## ----------- ## /* confdefs.h */ #define PACKAGE_NAME "Gambit-C" #define PACKAGE_TARNAME "gambc-v4_7_4" #define PACKAGE_VERSION "v4.7.4" #define PACKAGE_STRING "Gambit-C v4.7.4" #define PACKAGE_BUGREPORT "gambit(a)iro.umontreal.ca" #define PACKAGE_URL "" configure: exit 77 What am I doing wrong? Steve

2 1

Job offer
by Habel Geneviève 09 Fév '15

09 Fév '15

Hi, You consider yourself one of the best in Web Programming and in scheme programming ? By joining us, you will be part of a dynamic team of online courses. Your Mission As programmeur-Intégrateur, you will work in the development of online courses. Your main tasks will be to: - Participate in conception, development, testing, maintenance and documentation of the application; - Online courses production (scheme-html-like code to express the rendering of pages of online courses) - Collaborate with the team to produce development needed in theses courses; - Resolve software defects and discrepancies; - Add new product features and enhancements The position we are offering is that of « concepteur en médiatisation pour les cours en ligne de la FAS » at a salary/wage of P1 (junior position). This position reports to Geneviève Habel, coordonnatrice de la formation en ligne. Your working hours will be 35h/week. This is a seasonal position of a few months. We would like you to start work in march. Please report to Geneviève Habel (genevieve.habel(a)umontreal.ca<mailto:genevieve.habel@umontreal.ca>), for documentation and orientation. We are confident a scheme skilled person would be able to make a significant contribution to the success of our service and look forward to working with you. Geneviève Habel

1 0

[ANN] Gambit-C v4.7.4 released
by gambit＠iro.umontreal.ca 09 Fév '15

09 Fév '15

3 2

Not Emacs
by Marc Feeley 06 Fév '15

06 Fév '15

I’ve just received news that the “Not Emacs” iOS app I’ve been working on has been approved to the app store. Check it out, it’s a free app! Not Emacs is an emacs-like editor that is built with Gambit and the ymacs editor (http://www.ymacs.org). Documents are shared using iCloud, so they are accessible from all devices automatically. Not Emacs also has an embedded Gambit REPL (started using M-x run_scheme). The app is best used with an external bluetooth keyboard, but the extended virtual keyboard has a bunch of extra keys to make editing possible if you don’t have an external keyboard. An update of the Gambit REPL app which includes the emacs-like editor is also available. Marc

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Gambit-list Février 2015