-
Notifications
You must be signed in to change notification settings - Fork 179
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
pg 0.10.0 fails to compile on OpenSolaris #56
Comments
Original comment by Michael Granger (Bitbucket: ged, GitHub: ged). Something about the way the extconf.rb combines the compilation flags from Ruby and Postgres isn't working, it would appear. It's causing trouble on other platforms as well, so I'm thinking I'll remove it and release 0.10.1 with a simpler extconf. |
Original comment by Michael Granger (Bitbucket: ged, GitHub: ged). I've been trying without success to get PostgreSQL 8.4 installed on OpenSolaris so I can test this myself (I'm fairly clueless about Solaris administration), but I'll give up for now and just ask that you try out the prerelease of 0.10.1 I just pushed to rubygems.org:
Once we get this resolved, would you mind lending me your advice on adding an OpenSolaris environment to my bevvy of VirtualBox testing machines? I try to install and run the specs on as many environments as possible, and this is one I don't yet have. Thanks for your help! |
Original comment by Michael Granger (Bitbucket: ged, GitHub: ged). A bit more detail... The relevant portion of the mkmf.log is this:
The two lines with the '>>>' are the clues. The two strategies for compiling the test program are both apparently giving the compiler flags it doesn't understand. With version 0.10.0, I introduced a change to the extconf that added the compiler flags specified by I'm guessing that the problem under OpenSolaris is that PostgreSQL is built using a different compiler than Ruby is, resulting in the unrecognized options. |
Original comment by Don Morrison (Bitbucket: elskwid, GitHub: elskwid). Hey Michael, Thanks so much for looking at this. I will try out the gem in the next couple of days. As for helping with OpenSolaris install, I'm actually quite new to it. I'll need to have a coworker help me, then I can help you. :-) I will give you an update as soon as I can. Thanks again! |
Original comment by Michael Granger (Bitbucket: ged, GitHub: ged). No problem. I've been talking to a former co-worker of mine who's a Solaris admin, and he's been trying out the newer gems for me. We haven't been able to duplicate your results, but I at least verified that the newest gem installs okay in his environment. |
Original comment by Anonymous. Hi, This didn't work on Mac OS X 10.6.6 with latest XCode. I get the same failure as described above. Thanks |
Original comment by Michael Granger (Bitbucket: ged, GitHub: ged). Are you sure it's not more like #57? 99% of the time, when someone reports a problem installing the library under OSX, it's because they're installing 'pg' with a universal Ruby binary compiled against a non-universal PostgreSQL. See the instructions in [[https://bitbucket.org/ged/ruby-pg/src/8ab3dd3c757b/README.OS_X|README.OS_X]] for how to resolve this. |
Original report by Don Morrison (Bitbucket: elskwid, GitHub: elskwid).
Hello pg team,
Recently ran into a problem compiling 0.10.0 on our OpenSolaris server. Server version: OpenSolaris 2008.11 snv_101b_rc2 X86
The error when bundler attempts the install:
The contents of mkmf.log
I did do some investigation/verification before filing the ticket:
verified my path configuration was correct, pg_config is available
the files that are reported as missing are actually on the server
since I deploy from cap, I made sure that the same failure is experienced when logged in to the server
checked rbconfig.rb for common erroneous compiler settings - they all looked good to me - and I had just recently compiled a new version of ruby 1.8.7 so I know the toolchain was working a short time ago. (I have attached a copy to this issue)
This same server is able to compile pg 0.9.0 no problem.
Please let me know if there is anything else I can do or information I can provide to help solve this problem.
Thank you!
The text was updated successfully, but these errors were encountered: