> I'm not so sure about that. What this means is that the test program
> that tried to test linking against libpq failed to compile. Most
> obviously this would be because libpq can't be found but doesn't look
> like it in this case. Like I said before i would play around with the
> LDFLAGS environment variable and see if you could use that to make it
> link against the kerberos library.
I agree with you: compilation of test program fails.
Following sequence:
export LDFLAGS=-lkrb5
sudo gem install ruby-pg
changes nothing. "-lkrb5" wasn't added to cc command in mkmf.log
> The libpgsql-ruby library is basically the ruby postgres bindings (at
> least one of them - there have been a number of them over time, all
> with rather similar names), but installed via your package manager
> rather than as a gem. Assuming this library is the set of bindings
> that you do want you don't need the gem - you'd just end up with the
> same code installed twice, once as a gem and once not (although the
> timestamp in the version number for it makes it look quite old).
Yes. That could be a solution. But this package installed only /usr/
lib/ruby/1.8/i486-linux/pg.so library and some documents. None rb
script was installed! I feel that without .rb scripts I cannot use
ruby-pg adapter in my rails.
I think I will try to compile myself postgres + libpq without
Kerberos.
Then ruby-pg should be installed without problems.
Conrad, Fred: Thanks for your help!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
