FreeTDS Development Group

[Norman Palardy <palardyn AT mac.com>]

Thanks to James and Mark I have a build that I am trying to test (not 
sure I want to venture into trying to get SQSH going right now)
Things do seem to be compiled and linked ok and even running
On to bigger an better things now

On Thursday, October 18, 2001, at 03:20  PM, Lowden, James K wrote:

> Hi Norman,
>
> Someone here undoubtedly knows the answer to your question.  I don't, 
> but I
> have an advanced degree in speculation, so if you're putzing around with
> this anyway, here's my two cents.
>
> I can't tell from your posts if this box has ever compiled anything
> successfully.  I'm guessing that --host=ppc is right and your 
> /usr/include
> is missing something.  I don't think you want to use sys/malloc.h, and I
> don't think there's anything else you need to tell ./configure.  All
> guesses, you realize.
>
> OS X is a FreeBSD variant, which is related to NetBSD, which is what I 
> have.
> On my system, there are two malloc.h files:
>
> $ find /usr/include -name malloc.h
> /usr/include/sys/malloc.h
> /usr/include/malloc.h
>
> Here's the entire contents of /usr/include/malloc.h:
>
> $cat /usr/include/malloc.h
> /*      $NetBSD: malloc.h,v 1.3 1994/10/26 00:56:03 cgd Exp $   */
>
> #include <stdlib.h>
>
> That's it.  stdlib.h has the declaration for malloc().
>
> If your stdlib.h has a malloc declaration, you might want to try 
> creating a
> one-line malloc.h like mine, and give it another whirl.
>
> I know you've been knocking around with this for a while.  I wish it 
> were
> otherwise.
>
> Let me respond to your rant, too.
>
> Many of your criticisms are well-placed (except I have to point out 
> that a
> link to the User Guide is on the very first line of the FAQ.  It was put
> online for your convenience, so you wouldn't have to build it from the
> sgml.)
>
> On the plus side, maybe your observations will encourage us to post 
> binary
> packages in the new ftp space.  OTOH, FreeTDS builds in so many 
> different
> environments that it will be hard even to name and organize binary 
> libraries
> such that you can find what you need.  A complete matrix would be the 
> cross
> product of:
>
> 8       or so OS's (probably more)
> N       Supported hardware architectures for some of the OS's
> 3       TDS protocol versions (basically)
> Y/N     --enable-dbmfix
> Y/N     --enable-msdblib
>
> That's about 200 permutations and I haven't listed all the available 
> inputs
> to configure.  How would you suggest we organize and document such an
> ungainly collection?  I'm not challenging you or suggesting it's 
> impossible.
> I'm genuinely open to suggestion.
>
> A vendor gets to control a lot of these variables.  Sybase, for 
> instance,
> supports 1 protocol on a few OS's, for instance.  (I don't know what 
> they do
> about --enable-dbmfix.)  We won't speak of Microsoft.
>
> I think some of the difficulties you've encountered are fixable and 
> some are
> inescapeable.  FreeTDS might be the most complicated Hydra I've seen.  
> Not
> to say the beast can't be slain, only to say the solution isn't entirely
> straightforward.
>
> Regards,
>
> --jkl
>
> -----Original Message-----
> From: Norman Palardy [mailto:palardyn AT mac.com]
> Sent: October 18, 2001 3:44 PM
> To: TDS Development Group
> Subject: [freetds] Re: Building FREETDS
>
>
> missed adding this this .... malloc on this box is in
> /usr/include/sys/malloc.h
> What config settings might get the makefiles built in a way that it
> would find it there ?
>
> On Thursday, October 18, 2001, at 01:32  PM, Norman Palardy wrote:
>
> > I really DO want to make this work
> > I've tried quite a few things and cannot get FreeTDS to build to the
> > point I can use it
> >
> > It seems that at this point I have a problem with specifying the right
> > --host option for configure
> > It doesn't guess it properly and so I have to supply one
> >
> > ./configure --with-tdsver=5.0
> >   fails at checking host system type... configure: error: can not guess
> > host type; you must specify one
> >
> > ./configure --with-tdsver=5.0 --host=ppc
> >    configures OK but makes fail trying to locate malloc.h
> >
> > ./configure --with-tdsver=5.0 --host=apple
> >  fails
> >  ltconfig: you must specify a host type if you use `--no-verify'
> >
> > ./configure --prefix=/usr/local/freetds --with-tdsver=4.2
> > --enable-shared --enable-static
> >   fails .... need to supply a host
> >
> > ./configure --prefix=/usr/local/freetds --with-tdsver=4.2
> > --enable-shared --enable-static --host=ppc_apple_osx
> >   fails .... osx unrecognized
> >
> > ./configure --prefix=/usr/local/freetds --with-tdsver=4.2
> > --enable-shared --enable-static --host=ppc_apple_os_x
> >   fails .... os_x unrecognized
> >
> > ./configure --prefix=/usr/local/freetds --with-tdsver=4.2
> > --enable-shared --enable-static --host=ppc_apple_macos
> >   fails .... macos unrecognized
> >
> > ./configure --prefix=/usr/local/freetds --with-tdsver=4.2
> > --enable-shared --enable-static --host=powerpc
> >   configure runs but make fails on malloc.h again
> >
> >
> > Yes, I checked. /usr/include on this set up really has no malloc.h
> > I'm checking on another developer list to see why this is and what I
> > can do about it
> >
> > In the mean time, what might you folks suggest as the host variable ?
> >
> >
> > ---
> > You are currently subscribed to freetds as: [norm AT kirais.com]
> > To unsubscribe, forward this message to leave-
> > freetds-136003B AT franklin.oit.unc.edu
>
>
> ---
> You are currently subscribed to freetds as: [LowdenJK AT bernstein.com]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>
> ---
> You are currently subscribed to freetds as: [norm AT kirais.com]
> To unsubscribe, forward this message to leave-
> freetds-136003B AT franklin.oit.unc.edu