Re: 'CONFIG_HEADER not defined' during sed compile during 'guix pull'

2019-02-03 Thread Nathan Valentine
Just to round this one out, I was able to get things working in a Fedora29 VM by relying on Substitutes. I found the 'Binary Installation' docs to be somewhat misleading but I wrote a BASH script (wrapped in a Vagrantfile) which details my working setup. I'm not sure its worth sharing here since

Re: 'CONFIG_HEADER not defined' during sed compile during 'guix pull'

2019-01-30 Thread Ricardo Wurmus
Hi Nathan, > I have all of the available selinux devel packages installed: […] What you have installed on your system does not affect the build. That’s by design. All builds happen in isolated environments where only declared packages are available. Your system files are not available during

Re: 'CONFIG_HEADER not defined' during sed compile during 'guix pull'

2019-01-30 Thread Nathan Valentine
Thanks for looking at things, Ricardo. > That’s not good but I cannot reproduce this as of Guix > ba123b6dda3afb84c457f9e68c20eeff61e2c740. I ran “guix build --check > sed” to build sed. (Are you running the daemon on a system where > SELinux is enabled?) I get no output and a 0 exit code when