https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • b
    @David Sandilands ARM workstations are mote and more common so I think it makes sense to introducr aarch64 next to amd64 for each release
    đź’Ż 2
  • s
    This message was deleted.
    c
    y
    c
    • 4
    • 18
  • c
    is there a way to enforce noop mode only at the module level? meaning all classes only in that specific custom module will be in noop - but all others are still in enforce mode
  • s
    This message was deleted.
    d
    s
    b
    • 4
    • 3
  • s
    This message was deleted.
    s
    h
    • 3
    • 2
  • s
    This message was deleted.
    s
    c
    r
    • 4
    • 4
  • r
    Hello, everyone. I’m wondering if anyone is experiencing a similar problem. I have 
    .gitlab-ci.yml
    and it worked perfect until yesterday. All of a sudden, the following error appeared:
    Copy code
    /opt/puppetlabs/puppet/lib/ruby/2.7.0/mkmf.rb:471:in `try_do': The compiler
failed to generate an executable file. (RuntimeError)
You have to install development tools first.
	from /opt/puppetlabs/puppet/lib/ruby/2.7.0/mkmf.rb:564:in `try_link0'
	from /opt/puppetlabs/puppet/lib/ruby/2.7.0/mkmf.rb:582:in `try_link'
	from /opt/puppetlabs/puppet/lib/ruby/2.7.0/mkmf.rb:684:in `try_ldflags'
	from /opt/puppetlabs/puppet/lib/ruby/2.7.0/mkmf.rb:1851:in `pkg_config'
	from extconf.rb:9:in `system_libffi_usable?'
	from extconf.rb:42:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can
be found here:

/home/gitlab-runner/builds/9X6pv1Yx/0/csstaff/puppet/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0/ffi-1.15.5/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in
/home/gitlab-runner/builds/9X6pv1Yx/0/csstaff/puppet/vendor/bundle/ruby/2.7.0/gems/ffi-1.15.5
for inspection.
Results logged to
/home/gitlab-runner/builds/9X6pv1Yx/0/csstaff/puppet/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0/ffi-1.15.5/gem_make.out

An error occurred while installing ffi (1.15.5), and Bundler cannot continue.
Make sure that `gem install ffi -v '1.15.5' --source '<https://rubygems.org/>'`
succeeds before bundling.

In Gemfile:
  puppet was resolved to 7.26.0, which depends on
    facter was resolved to 4.4.3, which depends on
      sys-filesystem was resolved to 1.4.3, which depends on
        ffi
    After looking into this further, facter’s latest gem was updated from 4.4.2 to 4.4.3, which seems to be causing the problem.
  • r
    I’ve been trying to specify facter gem to 4.4.2 in Gemfile, but, so far, it has been ignored.
  • c
    @runlolarun Since Facter 4.4.2 a new run-time dependency is required, 
    sys-filesystem
    (it was missing in the 
    .gemspec
    of 4.4.2, 4.4.3 fixed that). 
    sys-filesystem
    in turn requires 
    ffi
    which a C extension, and therefore requires a C compiler to build, which might be missing on your build system. But 
    mkmk.log
    should contain more precise details.
  • r
    Funny thing is that i USED to be able to see that mkmf.log file. It’s no longer there.
  • c
    If you had used Facter 4.4.2 before it should have basically worked, but wasn't able to resolve the 
    mountpoints
    fact.
  • r
    Yesterday, when I did see it, it was looking for a library that was already installed. I’ll look further now.
  • r
    Yes, it worked with 4.4.2/
  • r
    I just looked again and 
    vendor
    directory is missing, thus where can i find that mkmf.log file? 
    find
    is not producing anything either.
  • r
    I believe 
    libffi
    and 
    libffi-devel
    are required for `ffi`gem. They are installed.
  • c
    And what about that 
    gem_make.out
    ?
  • r
    Well, it seems like it’s looking for 
    /usr/share/include/ruby.h
    , while 
    ruby-devel
    provides 
    /usr/include/ruby/ruby.h
  • r
    i tried installing ffi gem manually and got an error message that it’s looking for ruby.h
  • r
    /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0/ffi-1.15.5/gem_make.out
    seems “clean”
  • r
    I made a symbolic link (i know, it’s a half ass solution), and now the following is in the log file:
  • r
    Copy code
    "pkg-config --exists libffi"
| pkg-config --libs libffi
=> "-lffi \n"
"gcc -o conftest -I/usr/include -I/usr/include/ruby/backward -I/usr/include -I.    -O2 -g -pipe -Wall -Werror=forma
t-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-swi
tches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -mtune=generic -
fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC conftest.c  -L. -L/usr/lib64 -L. -Wl,-z,
relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -fstack-protector-strong -rdynamic -Wl,-export-dyna
mic  -m64   -lruby  -lm   -lc"
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */
  • c
    To me it looks like you are using a mixture of the Ruby provided by the operating system (or why 
    ruby-devel
    ?) and the Ruby provided by the Puppet stack, to be honest.
  • r
    Let me try removing ruby-devel. I just installed it for testing.
  • r
    Copy code
    $ locate ruby.h
/opt/puppetlabs/puppet/include/ruby-2.7.0/ruby.h
/opt/puppetlabs/puppet/include/ruby-2.7.0/ruby/ruby.h
  • r
    I will try to figure it out on my own before bugging you more.
  • c
    Because I'm not sure why it's looking for 
    /usr/share/include/ruby.h
    because Puppet's Ruby should look at the right spot for include files
    Copy code
    /opt/puppetlabs/puppet/bin/ruby -rrbconfig -e 'puts RbConfig::CONFIG["rubyhdrdir"]'
/opt/puppetlabs/puppet/include/ruby-2.7.0
  • r
    Yes, i have the same setting.
  • b
    @runlolarun which command do you run in the gitlab pipeline?
  • r
    Copy code
    bundle install --without system_tests --without development --path vendor/bundle --jobs $(nproc)
  • r
    Is this what you’re asking?
1...409410411...428Latest