Jira (PUP-10584) puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions

[Ciprian Badescu (Jira)]

Title: Message Title

Ciprian Badescu created an issue   Puppet / PUP-10584 puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions Issue Type: Bug Assignee: Ciprian Badescu Created: 2020/07/14 6:33 AM Environment: Running on Puppet 6 environment. Puppet-Agent version of 6.0.2 Puppet Gem version of 2.5.0 Running on a Centos 7 machine Priority: Normal Reporter: Ciprian Badescu Based on bellow issue on using /opt/puppetlabs/puppet/bin/gem, we will update puppet_gem package provider to be able to handle rugged installation with puppet: puppet resource package rugged ensure=present provider=puppet_gem ------   When installing R10K, if you install Rugged with the following method `/opt/puppetlabs/puppet/bin/gem install rugged` It will build as intended, but will then cause SegV to occur on running R10K even no matter what provider you have it set to use. If you first set your pkgconfig env with `export PKG_CONFIG_PATH=/opt/puppetlabs/puppet/lib/pkgconfig` And then install Rugged, it will then build and run as intended. The Puppet Gem environment should probably handle making sure gems built use vendored components. Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.365792.1594733596000.106786.1594733640240%40Atlassian.JIRA.