Skip to Content.
Sympa Menu

freetds - RE: make install no samples

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: make install no samples
  • Date: Fri, 11 Oct 2002 09:46:50 -0400


I'll look at the first one...

I haven't touched the iconv prototype since the last time you set it back to
const. As I think I mentioned in our last conversation, the iconv prototype
is different in different situations. I don't fully understand when the
parameters are const and when they are not. I may look into this
eventually, but it's not a high priority right now. Right now, I'm not
getting any warning about that line, even with "gcc -Wall
-Wmissing-prototypes -Wstrict-prototypes", on a NetBSD-1.6 system.

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Thursday, October 10, 2002 10:09 PM
To: TDS Development Group
Subject: [freetds] make install no samples


$ make install
[...]
Making install in samples
make: don't know how to make install. Stop
*** Error code 1

No big deal, of course.

Also (Nick?):

iconv.c:132: warning: passing arg 2 of `libiconv' from incompatible pointer
type

I'm gonna make that line read-only! :-)

--jkl

---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page