-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
freebsd gmake error : Unbound variable: macro-gc-hash-table-flag-weak-keys #1276
Comments
interesting, is this with the pinned gambit version or some other version? |
Just did a git clone & git pull. |
Clone from when? Pull from when? Did you pull right after a clone? Why do
that? :)
Or: What version of Gambit are you using to build? Is it the pinned
version?
Here's how to find out, in the gerbil source directory.
First, this is what the tag should be:
$ grep default_gambit_tag= ./configure
readonly default_gambit_tag=09335d95cab6931791c0a8497cbe915053ff8af3
If you've already configured this it should have cloned and checked out the
same tag. It was updated in April.
IE: https://github.com/mighty-gerbils/gerbil/blob/master/configure#L75
$ echo $(cd src/gambit; git log -1 | head -n1)
commit 09335d95cab6931791c0a8497cbe915053ff8af3
If those are both the same and both the same number that matches the tag
then it's an issue on our side and/or gambit's freebsd config.
If not, try `rm -rf build-env.sh src/gambit/* && ./configure` to make sure
you're not trying to mix old and new.
…--drewc
On Sun, Oct 27, 2024 at 2:06 AM Alain De Vos ***@***.***> wrote:
Just did a git clone & git pull.
—
Reply to this email directly, view it on GitHub
<#1276 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADVTXMSKPGPRLWATXAYW2DZ5SNKFAVCNFSM6AAAAABQVQV6SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZHEYTOMJQHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
After rm -rf build-env.sh src/gambit/* && ./configure i got the same error. |
Did you `make clean` beforehand? Regardless, try that, try a fresh clone
checkout, and make sure there's no existing gambit or gerbil anywhere in
your $PATH.
What version of freebsd? If it fails with a fresh clone on a fresh system
with clean $PATHs I'll fire up a FreeBSD VM and we can go from there.
…On Mon, Oct 28, 2024 at 5:19 AM Alain De Vos ***@***.***> wrote:
After rm -rf build-env.sh src/gambit/* && ./configure i got the same error.
My guess it's not the gerbil version but some sort of incompatibility
between freebsd & gerbil which was introduced recently.
—
Reply to this email directly, view it on GitHub
<#1276 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADVTXJJHAJOZ6CIMHFAQZ3Z5YMUBAVCNFSM6AAAAABQVQV6SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBRGQZTEMRUGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
These are my steps
gsi -v uname -a |
@ober as the bsd czar, any idea what is going on here? |
https://gist.github.com/ober/642cf0aee95a29fbb8a14391a2511508 This is how I build it. No gmake, and no -jN. |
Thanks. That worked. |
gmake -j4 fails on freebsd with the error :
I used to compile fine previously
The text was updated successfully, but these errors were encountered: