The --with-guile-site flag has been restored for the build, and I updated the package to the latest version.
If anyone has any insight into why --with-guile-site was removed originally, I would be interested to know...
Git Clone URL: | https://aur.archlinux.org/guile-lib.git (read-only, click to copy) |
---|---|
Package Base: | guile-lib |
Description: | Repository of useful code written in Guile Scheme |
Upstream URL: | http://www.nongnu.org/guile-lib/ |
Licenses: | GPL-3.0-or-later AND LGPL-3.0-or-later |
Submitter: | tantalum |
Maintainer: | pnorcks (holos) |
Last Packager: | pnorcks |
Votes: | 26 |
Popularity: | 0.000000 |
First Submitted: | 2008-09-17 22:05 (UTC) |
Last Updated: | 2024-11-12 05:30 (UTC) |
The --with-guile-site flag has been restored for the build, and I updated the package to the latest version.
If anyone has any insight into why --with-guile-site was removed originally, I would be interested to know...
@zhaose I think so, yes. See my comment below from 2 October 2022...
@bidulock Can you comment about the rationale for removing --with-guile-site in the most recent commit? If its removal was intentional, I'm not entirely sure how I should adapt my package to build correctly against guile-lib.
Should "--with-guile-site=yes" be used here? I am wondering if these packages installed by the system package manager should be at the default load path guile could find.
Builds for Manjaro when I say GUILE=/usr/bin/guile3 instead of /usr/bin/guile though
"configure: error: found development files for Guile 3.0, but /usr/bin/guile has effective version 2.2"
(pasting in the "prepare()..." and changing the "./configure" line didn't work)
What was the reason for removing the --with-guile-site configure flag in guile-lib-0.2.7-2 (currently the latest commit)?
I am asking about this because my package guile-dsv depends on guile-lib, and it fails to build at the moment. When I build/install guile-lib using --with-guile-site, guile-dsv builds cleanly again.
Can it be modified to install files in the standard locations instead of its own /usr/lib/guile-lib directory? This can be done by adding 'moddir=/usr/share/guile/site/2.2 godir=/usr/lib/guile/2.2/site-ccache' to make command line. Currently Guix 1.3.0 cannot find guile-lib even if the package is installed.
checking if (htmlprag) exports `%strict-tokenizer?'... no
configure: WARNING: The Guile-Lib requirement was not satisfied (>= 0.2.7);
Some features such as the Go importer will not be usable.
However, values recorded in the .pc file doesn't change if we modify the installation path by make command line.
The following patch allows this to build properly for guile 2.2.
diff --git a/PKGBUILD b/PKGBUILD
index a1f409e..228ae2a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -13,7 +13,7 @@ md5sums=('6457b08133e4baa54a438a11b18e9c30')
build(){
cd ${pkgname}-${pkgver}
- ./configure --prefix=/usr
+ GUILE=/usr/bin/guile ./configure --prefix=/usr
make
}
Adding this clause to PKGBUILD allows it to compile
prepare() {
cd ${pkgname}-${pkgver}
sed -i 's/ 2.2/ /g' configure
}
failed to build due to the following error:
configure: error: found development files for Guile 2.2, but /usr/bin/guile2.0 has effective version 2.0
Pinned Comments
pnorcks commented on 2024-11-12 00:33 (UTC) (edited on 2024-11-12 00:48 (UTC) by pnorcks)
The --with-guile-site flag has been restored for the build, and I updated the package to the latest version.
If anyone has any insight into why --with-guile-site was removed originally, I would be interested to know...