-
Notifications
You must be signed in to change notification settings - Fork 30
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
Heroku 18 build not working #11
Comments
@RickEaton without knowing more about your situation, it's hard to know
|
@bf4 Thank you for the response.
mote: -----> [2020-04-12 13:46:58] Building FreeTDS against OpenSSL OpenSSL 1.1.1 11 Sep 2018
Thank you again for your help. |
So, it seems the freetds build may be successful After building without the tiny tds gem, run a bash session and try |
@bf4 Following your instructions and building with tiny_tds gem, tsql -C gives a block of configuration information: Unfortunately, gem install tiny_tds -v '2.1.2' gives:
/app/vendor/ruby-2.7.0/bin/ruby -I /app/vendor/ruby-2.7.0/lib/ruby/2.7.0 -r ./siteconf20200412-34-1ghx6tx.rb extconf.rb Provided configuration options: To see why this extension failed to compile, please check the mkmf.log which can be found here: /app/vendor/ruby-2.7.0/lib/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0/tiny_tds-2.1.2/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /app/vendor/ruby-2.7.0/lib/ruby/gems/2.7.0/gems/tiny_tds-2.1.2 for inspection. |
@bf4 And running gives a series of messages indicating that the expected files are not found: ----------------------- ld /app/vendor/bundle/ruby/2.5.0/gems/tiny_tds-2.1.2/lib/tiny_tds/tiny_tds.so------------------ ld: cannot find /app/vendor/bundle/ruby/2.5.0/gems/tiny_tds-2.1.2/lib/tiny_tds/tiny_tds.so: No such file or directory ----------------------- cat /app/vendor/bundle/ruby/2.7.0/gems/tiny_tds-2.1.2/ext/tiny_tds/Makefile------------------ cat: /app/vendor/bundle/ruby/2.7.0/gems/tiny_tds-2.1.2/ext/tiny_tds/Makefile: No such file or directory ----------------------- cat /app/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0-static/tiny_tds-2.1.2/gem_make.out------------------ cat: /app/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0-static/tiny_tds-2.1.2/gem_make.out: No such file or directory ----------------------- cat /app/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0-static/tiny_tds-2.1.2/mkmf.log------------------ cat: /app/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0-static/tiny_tds-2.1.2/mkmf.log: No such file or directory |
At this point I'm going to ask you to use your programmer skills to read those error messages to look through the compile logs and perhaps reference my debug task to figure out what went wrong 1 look at the files referenced in the output |
@bf4 Thank you for those suggestions. I was able to track this down, which might be helpful. The contents of mkmf.log are: "gcc -o conftest -I/app/vendor/ruby-2.7.0/include/ruby-2.7.0/x86_64-linux -I/app/vendor/ruby-2.7.0/include/ruby-2.7.0/ruby/backward -I/app/vendor/ruby-2.7.0/include/ruby-2.7.0 -I. -I/usr/local/include -I/usr/local/include/freetds -O3 -g -Wall -Wextra -Wdeprecated-declarations -Wduplicated-cond -Wimplicit-function-declaration -Wimplicit-int -Wmisleading-indentation -Wpointer-arith -Wwrite-strings -Wimplicit-fallthrough=0 -Wmissing-noreturn -Wno-cast-function-type -Wno-constant-logical-operand -Wno-long-long -Wno-missing-field-initializers -Wno-overlength-strings -Wno-packed-bitfield-compat -Wno-parentheses-equality -Wno-self-assign -Wno-tautological-compare -Wno-unused-parameter -Wno-unused-value -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wunused-variable -fPIC conftest.c -L. -L/app/vendor/ruby-2.7.0/lib -Wl,-rpath,/app/vendor/ruby-2.7.0/lib -L/usr/local/lib -Wl,-rpath,/usr/local/lib -L/usr/local/lib/freetds -Wl,-rpath,/usr/local/lib/freetds -L. -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,-rpath,'/../lib' -Wl,-rpath,'/../lib' -lruby -lm -lc" It looks like somehow the path to the std libraries has been messed up since stdio.h was not found. |
seems you'll want to confirm gcc is working a google search points out you can run in bash of course, Or maybe something in tiny_tds? @metaskills how are your spleunking skills on stuff like this? on one of my heroku 16 instances I see
|
@bf4 I was able to spend more time on this and have narrowed down the problem to release 2.1.0 of tiny_tds. I am able to successfully deploy using:
I will close this issue and open one for tiny_tds |
@RickEaton great job narrowing it down! If you're feeling particularly adventurous, and you'd don't already know how to bisect a gem to find the breaking commit and would like to learn, I can show you. |
Thanks. I definitely don’t how to do that, but could put some time into it and would appreciate the instruction.
Rick Eaton
Eaton Nonprofit Solutions
916-718-5063
http://www.eatonnpsolutions.com<http://www.eatonnpsolutions.com/>
From: Benjamin Fleischer <[email protected]>
Reply-To: rails-sqlserver/heroku-buildpack-freetds <[email protected]>
Date: Monday, April 20, 2020 at 8:56 PM
To: rails-sqlserver/heroku-buildpack-freetds <[email protected]>
Cc: Rick Eaton <[email protected]>, Mention <[email protected]>
Subject: Re: [rails-sqlserver/heroku-buildpack-freetds] Heroku 18 build not working (#11)
@RickEaton<https://github.com/RickEaton> great job narrowing it down!
If you're feeling particularly adventurous, and you'd don't already know how to bisect a gem to find the breaking commit and would like to learn, I can show you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHIDY6SCTDAOGUAUHOVXCDRNUKM3ANCNFSM4MFTTX3A>.
|
The TinyTDS gem does not load when deploying to Heroku with the Heroku-18 stack. I have specified heroku-buildpack-freetds as the first buildpack in the sequence, followed by the standard heroku/ruby pack.
The app is running Rails 6, but I encountered the same error with 5.8. I've attached a copy of the trace of the push.
trace.txt
The text was updated successfully, but these errors were encountered: