Skip to Content.
Sympa Menu

freetds - RE: [freetds] dbschema.pl -- fixed

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] dbschema.pl -- fixed
  • Date: Tue, 25 Feb 2003 15:00:02 -0500

> From: Craig Davison [mailto:cd AT securityfocus.com]
> Sent: February 25, 2003 2:41 PM
>
> On Tue, Feb 25, 2003 at 12:26:39PM -0700, Craig Davison wrote:
> > I have access to a FreeBSD 4.5 (x86) box, so I thought I'd
> > try building
> > 0.61rc4 as well. It failed for me too with errors about
> > undefined types
> > like u_char, etc.
>
> Just to clarify, I should mention that the compile errors occured in
> <sys/socket.h> in login.c and <netinet/in.h> in pool.h. It
> seems that in
> FreeBSD, these headers, which use types like u_char, were written
> expecting the developer to include <sys/types.h> as well.

Craig,

Thank you for testing rc4. I'll put together a "proper patch" tonight. I
hope you'll try rc5. ;-)

In login.c, I see:

#if HAVE_SYS_SOCKET_H
#include <sys/socket.h>
#endif /* HAVE_SYS_SOCKET_H */

#if HAVE_SYS_TYPES_H
#include <sys/types.h>
#endif /* HAVE_SYS_TYPES_H */

If you reverse these two blocks, does it compile?

If so, then perhaps pool.h should be:

#if HAVE_SYS_TYPES_H
#include <sys/types.h>
#endif /* HAVE_SYS_TYPES_H */

#if HAVE_NETINET_IN_H
#include <netinet/in.h>
#endif /* HAVE_NETINET_IN_H */

You can expect fixes along those lines tonight.

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.





Archive powered by MHonArc 2.6.24.

Top of Page