On 4/20/06, Marcel Molina Jr. <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 20, 2006 at 11:28:24PM -0400, Mike Laster wrote:
> > On 4/20/06, Marcel Molina Jr. <[EMAIL PROTECTED]> wrote:
> > > I installed Frontbase and the ruby bindings for it.  At first when I ran 
> > > the
> > > test it was complaining that FBSQL_Connect.connect was getting one too 
> > > many
> > > arguments passed to it. Just to move forward I took off the extra 
> > > argument.
> > > Then when I run the tests I get loads of warnings from Object#type on line
> > > 511 of the frontbase adapter.
> >
> > Are you running the newest FrontBase?  I am testing against 4.2.4.  It
> > definitely
> > will not work with the 3.x line.
>
> I've got 4.2.4, yeah.
>
> > About the extra argument...check that you have the newest Ruby bindings.
> > The ones on the Frontbase site are *not* the newest.  I had to modify
> > them to work
> > with ActiveRecord.  I sent my changes back to them but they haven't
> > posted them yet.
> >
> > I have the source to the modified bindings checked in at:
> >
> > svn://rubyforge.org//var/svn/frontbase-rails/trunk/ruby-frontbase
>
> I did indeed have the bindings from the Frontbase site.
>
> When I grab yours from rubyforge, this is what I get when I run make:
>
> /usr/bin/ld: /Library/FrontBase/lib/libFBCAccess.a(FBCAccessAll-i386.o) 
> malformed object (section (__TEXT,__textcoal_nt) no symbol at start of 
> coalesced section)
> collect2: ld returned 1 exit status
> make: *** [frontbase.bundle] Error 1
>
> (MacBook Pro)

Hmm...that is a new one to me.  I don't have access to an Intel Mac so
I've only done this on PPC.  That looks like FrontBase may have a bad
framework in their distribution.

I'll forward this to their support people and see what they can find out.
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to