-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
MySQL 5.7 fails to build recently #35692
Comments
To help you, MySQLs started to fail after gcc: 6 -> 7. |
Why would that be strange? You want to refer to a path that isn't (validly) in nix store yet. |
@vcunat Thanks, that makes sense. I didn't know how much "magic" the interpreter does for stuff in So, how does one override the gcc version? was trying something like I also saw some truly ancient documentation here about overrideGCC. |
I had tried building with gcc overridden to gcc6 – via the usual |
@vcunat Indeed, if I try that I get the following output still:
|
{pkgs, ...}: {
services.mysql.enable = true;
services.mysql.package = pkgs.mysql57.override {
stdenv = pkgs.overrideCC pkgs.stdenv pkgs.gcc6;
};
} Seems to build correctly with GCC 6.4 for me (running nixos-unstable). |
Issue description
MySQL 5.7 fails to build recently:
mysql57_build_error.txt
default.nix
for me. This worked at one time, without issue.
Steps to reproduce
You can use the attached default.nix with nix-shell, or perhaps just try installing the mysql57 package. One thing that really confuses me, by the way, is that if you comment out
mysql57
in default.nix, it still seems to try to build mysql. Seemingly it does this based on a reference in the shellHook, but this seems strange to me.Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste theresults.
"x86_64-linux"
Linux 4.13.0-32-generic, Ubuntu, 16.04.3 LTS (Xenial Xerus)
no
no
nix-env (Nix) 1.11.16
"nixpkgs-18.03pre129212.098c7f3d945, nixos-18.03pre129076.831ef4756e3"
/nix/var/nix/profiles/per-user/brandon/channels/nixpkgs
The text was updated successfully, but these errors were encountered: