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
tcl/tk: 8.6.6 -> 8.6.8 and create library symlink #35069
Conversation
I'll try to get things moving a bit. First off, built on top of current Verified using @GrahamcOfBorg build gitAndTools.gitFull Also if you have any ideas of other tcl/tk, especially fiddly or non-trivial ones to test this on, I'm all ears. There were questions about |
Timed out, unknown build status on x86_64-darwin (full log) Attempted: gitAndTools.gitFull Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: gitAndTools.gitFull Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gitAndTools.gitFull Partial log (click to expand)
|
@GrahamcOfBorg build tcl tk scid-vs-pc |
Success on x86_64-linux (full log) Attempted: tcl, tk, scid-vs-pc Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: tcl, tk, scid-vs-pc Partial log (click to expand)
|
This package seems ready to be merged apart from the conflicting file? EDIT: I see that there now already is a 64bit option available: https://github.com/nixos/nixpkgs/blob/969149302c3ad1a0fddcb19811ac674ebbbfe676/pkgs/development/interpreters/tcl/generic.nix#L29 This PR is not needed anymore, apart from the version bump. Should the version bump be based on staging or master? Should this PR be closed? |
Conflict aside, 8.6.9 has since been released so this PR is obsolete. Agree that it should be closed. |
tcl/tk were out of date. Also, I tried to compile something with
gcc -ltcl -ltk
and it complained about not being able to find those libraries - turnsout, the symlinks for them are never made, so I had to use
gcc -ltcl8.6 -ltk8.6
. Most distros make these themselves, so I added another line.There seems to be some oddness with the sha256 sum - the package built
successfully even when I forgot to update it (it's up to date in this commit); I
don't know what's going on here, but someone more experienced than me should
probably check it out.
I also enabled the
--enable-64bit
flag; this is probably not contentious, Ijust saw that other distros were doing it too.
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)