Skip to content
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

Attempting to build omnibus-toolchain on ppc64le fails #54

Open
drhey opened this issue Mar 20, 2017 · 5 comments
Open

Attempting to build omnibus-toolchain on ppc64le fails #54

drhey opened this issue Mar 20, 2017 · 5 comments

Comments

@drhey
Copy link

drhey commented Mar 20, 2017

I am attempting to build the omnibus-toolchain on a RHEL ppc64le system. I've installed the needful packages (autoconf bison flex gcc gcc-c++ kernel-devel make m4 patch gettext-devel ncurses-devel openssl-devel readline-devel zlib-devel git rpmdevtools libffi libffi-devel fakeroot).

When I run sudo ~/.rbenv/shims/bundle exec omnibus build omnibus-toolchain I am met with the following error:

Error:

    configure: error: in `/gpfs/gpfs0/hpcstaff/drhey/omnibus-toolchain/local/omnibus/src/gtar/tar-1.28':
configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check)
See `config.log' for more details

I've tried to export the FORCE_UNSAFE_CONFIGURE=1 variable as user running the aforementioned sudo omnibus command (AND as root) to no avail.

I apologize if this isn't the appropriate venue for this. Any help is greatly appreciated.

@schisamo
Copy link
Contributor

/cc @scotthain @jaymalasinha

@scotthain
Copy link
Contributor

@drhey we don't recommend running the build as root. (I haven't had any success doing that personally). We also use bundler to ensure we have the latest omnibus and omnibus-software definitions, which may be required, depending on when you last updated. (https://github.com/chef/omnibus-toolchain/blob/master/Gemfile#L3-L4)

@drhey
Copy link
Author

drhey commented Mar 20, 2017

@scotthain Thanks! I'm currently cloning the omnibus-toolchain repo, and then following the doc for building the toolchain on Fedora/CentOS/RHEL. Are the steps contained therein still applicable? Or should I explicitly try doing something like gem install omnibus ?

As a data point, I was able to make progress doing the following sudo FORCE_UNSAFE_CONFIGURE=1 ~/.rbenv/shims/bundle exec omnibus build omnibus-toolchain (just to see if it would get past the snare; which it did). However, as you mentioned it's not good form to build as root.

@scotthain
Copy link
Contributor

@drhey oh! It looks like those docs may be out of date :( To be honest, the easiest/quickest way (and the way we build it) is to use the omnibus cookbook https://github.com/chef-cookbooks/omnibus to set up your builder and simply override the toolchain_name attribute here https://github.com/chef-cookbooks/omnibus/blob/master/attributes/default.rb#L22 to angry-omnibus-toolchain This will set up the paths appropriately and you can use the tools in the (separately namespaced) toolchain to build the toolchain.

@drhey
Copy link
Author

drhey commented Mar 20, 2017

@scotthain Thanks! And no worries. I'm not a Ruby pro by any stretch of the imagination. I came to the omnibus stuff by way of Sensu who leverages the omnibus for their packaging. I'm becoming more acquainted with the intricacies of ruby on-the-fly. It appears that the last bit of info you gave me viz. the two gems (omnibus, and omnibus-software) tool chain are yielded some results. I am now failing the omnibus HealthCheck. It mentions licensing and unsafe dependencies. Any thoughts there? It does mention the packages that are experiencing these snares, e.g.

          [HealthCheck] E | 2017-03-20T14:06:14-04:00 | The following binaries have unsafe or unmet dependencies:
    --> /opt/omnibus-toolchain/embedded/bin/tar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants