Hello Gambit developers-
I have successfully built, packaged and installed gambit on cygwin. The build system I used - cygport - defaults to an out-of-source build, which is supported by gambit's configure (or so it claims). It very quickly became apparent that out-of-source builds are broken, but I stubbornly patched the makefiles until it worked. What I've got now is a bit kludged, but should be fairly simple to maintain as long as the future gambit build system doesn't change drastically.
However, having come this far... I would be willing to further my work on patching configure.ac and the makefile.in's so gambit supports out-of-source builds and DESTDIR style installs. I can test on cygwin, RHEL, debian and solaris. I figure I'm about 1/3rd of the way there and I don't want to chew up any more of my time unless you are interested in accepting patches. Are you?
regards, Nate T
BTW, I haven't installed mercurial yet, so I haven't looked at the source repository, only the v4.2.8 release source.
Afficher les réponses par date
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nathan Thern wrote:
Hello Gambit developers-
I have successfully built, packaged and installed gambit on cygwin. The build system I used - cygport - defaults to an out-of-source build, which is supported by gambit's configure (or so it claims). It very quickly became apparent that out-of-source builds are broken, but I stubbornly patched the makefiles until it worked. What I've got now is a bit kludged, but should be fairly simple to maintain as long as the future gambit build system doesn't change drastically.
However, having come this far... I would be willing to further my work on patching configure.ac and the makefile.in's so gambit supports out-of-source builds and DESTDIR style installs. I can test on cygwin, RHEL, debian and solaris. I figure I'm about 1/3rd of the way there and I don't want to chew up any more of my time unless you are interested in accepting patches.
Hi Nathan,
I would be very interested in a fixed build system which supports DESTDIR style installs. Where can I find your patches?
Marijn
- -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML http://www.gentoo.org/proj/en/lisp/, #gentoo-{lisp,ml} on FreeNode
Yes, I will accept patches. The makefiles definitely need some refactoring and proper support for DESTDIR. But please keep it clean. To preserve a consistent layout of the makefiles (actually the set of makefile.in) in the past I have used sed scripts to modify all the makefiles together. Obviously some file specific modifications will be needed also.
Moreover, some people on this list (maintainers for different packagings of Scheme) may be interested in contributing and I urge you to work together on this so that everyone is happy. We could temporarily work in a new branch (forked off of 4.2.8) and when the makefiles are satisfactory, we will apply the patches to the main branch.
Marc
On 24-Jun-08, at 4:58 PM, Nathan Thern wrote:
Hello Gambit developers-
I have successfully built, packaged and installed gambit on cygwin. The build system I used - cygport - defaults to an out-of-source build, which is supported by gambit's configure (or so it claims). It very quickly became apparent that out-of-source builds are broken, but I stubbornly patched the makefiles until it worked. What I've got now is a bit kludged, but should be fairly simple to maintain as long as the future gambit build system doesn't change drastically.
However, having come this far... I would be willing to further my work on patching configure.ac and the makefile.in's so gambit supports out-of-source builds and DESTDIR style installs. I can test on cygwin, RHEL, debian and solaris. I figure I'm about 1/3rd of the way there and I don't want to chew up any more of my time unless you are interested in accepting patches. Are you?
regards, Nate T
BTW, I haven't installed mercurial yet, so I haven't looked at the source repository, only the v4.2.8 release source. _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
OK, here's my first go at it. In the source directory I applied the sed script as follows:
$ find -name makefile.in | xargs sed --in-place -f ../fix_gambc.sed
The rest of the changes were all hand edits and are encapsulated in gambc-v4.2.8_post_sed.patch.
gambc-v4.2.8.patch applies all the changes in one smash.
The patches work for the 4.2.8 source release and the latest repo tree. I haven't had time to test compiling the patched source on anything other than cygwin yet. This is my first time submitting changes to a project source code - let me know if I've done something stupid, or committed a faux pas.
regards, NT
On Wed, Jun 25, 2008 at 7:01 AM, Marc Feeley feeley@iro.umontreal.ca wrote:
Yes, I will accept patches. The makefiles definitely need some refactoring and proper support for DESTDIR. But please keep it clean. To preserve a consistent layout of the makefiles (actually the set of makefile.in) in the past I have used sed scripts to modify all the makefiles together. Obviously some file specific modifications will be needed also.
Moreover, some people on this list (maintainers for different packagings of Scheme) may be interested in contributing and I urge you to work together on this so that everyone is happy. We could temporarily work in a new branch (forked off of 4.2.8) and when the makefiles are satisfactory, we will apply the patches to the main branch.
Marc
On 24-Jun-08, at 4:58 PM, Nathan Thern wrote:
Hello Gambit developers-
I have successfully built, packaged and installed gambit on cygwin. The build system I used - cygport - defaults to an out-of-source build, which is supported by gambit's configure (or so it claims). It very quickly became apparent that out-of-source builds are broken, but I stubbornly patched the makefiles until it worked. What I've got now is a bit kludged, but should be fairly simple to maintain as long as the future gambit build system doesn't change drastically.
However, having come this far... I would be willing to further my work on patching configure.ac and the makefile.in's so gambit supports out-of-source builds and DESTDIR style installs. I can test on cygwin, RHEL, debian and solaris. I figure I'm about 1/3rd of the way there and I don't want to chew up any more of my time unless you are interested in accepting patches. Are you?
regards, Nate T
BTW, I haven't installed mercurial yet, so I haven't looked at the source repository, only the v4.2.8 release source. _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nathan Thern wrote:
OK, here's my first go at it. In the source directory I applied the sed script as follows:
$ find -name makefile.in | xargs sed --in-place -f ../fix_gambc.sed
The rest of the changes were all hand edits and are encapsulated in gambc-v4.2.8_post_sed.patch.
gambc-v4.2.8.patch applies all the changes in one smash.
The patches work for the 4.2.8 source release and the latest repo tree. I haven't had time to test compiling the patched source on anything other than cygwin yet. This is my first time submitting changes to a project source code - let me know if I've done something stupid, or committed a faux pas.
regards, NT
Hi Nathan,
I tested your patch but it doesn't solve the following problem:
$ gsi gsi: error while loading shared libraries: /var/tmp/portage/dev-scheme/gambit-4.2.8/image//usr/lib/libgambcgsi.so: cannot open shared object file: No such file or directory
$ equery f gambit | grep libgambcgsi.so /usr/lib/libgambcgsi.so
The /var/tmp/portage/dev-scheme/gambit-4.2.8/image/ is DESTDIR and somehow it is encoded in the binaries, but I don't know how exactly this happens.
I used the following:
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man - --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc - --localstatedir=/var/lib --enable-shared --disable-single-host - --disable-gcc-opts --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu
note the --enable-shared.
Marijn
- -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML http://www.gentoo.org/proj/en/lisp/, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Marijn Schouten (hkBst) wrote:
Nathan Thern wrote:
OK, here's my first go at it. In the source directory I applied the sed script as follows:
$ find -name makefile.in | xargs sed --in-place -f ../fix_gambc.sed
The rest of the changes were all hand edits and are encapsulated in gambc-v4.2.8_post_sed.patch.
gambc-v4.2.8.patch applies all the changes in one smash.
The patches work for the 4.2.8 source release and the latest repo tree. I haven't had time to test compiling the patched source on anything other than cygwin yet. This is my first time submitting changes to a project source code - let me know if I've done something stupid, or committed a faux pas.
regards, NT
Hi Nathan,
I tested your patch but it doesn't solve the following problem:
$ gsi gsi: error while loading shared libraries: /var/tmp/portage/dev-scheme/gambit-4.2.8/image//usr/lib/libgambcgsi.so: cannot open shared object file: No such file or directory
$ equery f gambit | grep libgambcgsi.so /usr/lib/libgambcgsi.so
The /var/tmp/portage/dev-scheme/gambit-4.2.8/image/ is DESTDIR and somehow it is encoded in the binaries, but I don't know how exactly this happens.
I used the following:
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-shared --disable-single-host --disable-gcc-opts --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu
note the --enable-shared.
Marijn
When using --disable-shared gambit tries to install the non-directory file DESTDIR/usr/lib64, so that is unusable too.
Marijn
- -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML http://www.gentoo.org/proj/en/lisp/, #gentoo-{lisp,ml} on FreeNode
"Nathan Thern" nthern@gmail.com writes:
Hello Gambit developers-
[...]
Are you?
Nate,
I'm interested, although I'm not a [Gambit-C] developer, but a user that would like to make packages instead of installing "in place." I now have Gambit installed in /usr/local/Gambit-C instead of making it into a Slackware package (that can be easily removed or upgraded).
HOWEVER, I would love to hear Professor Feeley's rationale for the installation directory structure, especially since I noticed that Snow works the same way.
Thanks for bringing it up, Joel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Joel J. Adamson wrote:
I'm interested, although I'm not a [Gambit-C] developer, but a user that would like to make packages instead of installing "in place." I now have Gambit installed in /usr/local/Gambit-C instead of making it into a Slackware package (that can be easily removed or upgraded).
HOWEVER, I would love to hear Professor Feeley's rationale for the installation directory structure, especially since I noticed that Snow works the same way.
Speaking about Snow. In May I sent 3 patches among which a DESTDIR patch for snow to the snow user list and have heard nothing since.[1]
Marijn
[1]:https://webmail.iro.umontreal.ca/pipermail/snow-users-list/2008-May/thread.h...
- -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML http://www.gentoo.org/proj/en/lisp/, #gentoo-{lisp,ml} on FreeNode
"Marijn Schouten (hkBst)" hkBst@gentoo.org writes:
Joel J. Adamson wrote:
I'm interested, although I'm not a [Gambit-C] developer, but a user that would like to make packages instead of installing "in place." I now have Gambit installed in /usr/local/Gambit-C instead of making it into a Slackware package (that can be easily removed or upgraded).
HOWEVER, I would love to hear Professor Feeley's rationale for the installation directory structure, especially since I noticed that Snow works the same way.
Speaking about Snow. In May I sent 3 patches among which a DESTDIR patch for snow to the snow user list and have heard nothing since.[1]
Yes, it's a low-traffic list. I stopped using Snow for other reasons.
Joel
On Tue, Jun 24, 2008 at 03:58:05PM -0500, Nathan Thern wrote :
I would be willing to further my work on patching configure.ac and the makefile.in's so gambit supports out-of-source builds and DESTDIR style installs. I can test on cygwin, RHEL, debian and solaris. I figure I'm about 1/3rd of the way there and I don't want to chew up any more of my time unless you are interested in accepting patches. Are you?
As the (new) maintainer of Gambit on FreeBSD, I would really enjoy we work that out...
I believe that the wiki should be the right place to clearly define all the options that we want to consider, such as where and how to install everything. Plus, there are some constraints that appear only for certain people: - Some want to be able to have several versions of gambit installed - gsi/gsc can conflict with ghostscript binaries - Some operating systems have a strict hierarchy that has got to be stuck to. - Emacs's site-lisp can be anywhere
So, yes I'm interested in helping (within the limits of my spare time). Any VCS set up for the source modifications ?
Adrian
On Thu, Jun 26, 2008 at 02:33:09PM -0400, Adrien Pierard wrote :
I believe that the wiki should be the right place to clearly define all the options that we want to consider, such as where and how to install everything.
I set up this page: http://dynamo.iro.umontreal.ca/~gambit/wiki/index.php/Installer You can access it from "How to contribute" => "Port to new platforms" in case you don't remember the URL.
Feel free to comment, modify...
Cheers,
P!
-
adamsonj＠email.unc.edu -
Adrien Pierard -
Marc Feeley -
Marijn Schouten (hkBst) -
Nathan Thern