FreeTDS Development Group

["Adwin Singh" <singha AT redrock.net.au>]

I have attached the output of man malloc.

Perhaps you guys can see something useful that I don't ?

Thanks
Adwin

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of
ikorot AT earthlink.net
Sent: Monday, 20 December 2010 6:10 PM
To: FreeTDS Development Group; FreeTDS Development Group
Subject: Re: [freetds] Missing libtdsodbc.so on Solaris

Adwin,
What's "man malloc" gives you? Maybe there is some good info there?

Thank you.


-----Original Message-----
>From: Adwin Singh <singha AT redrock.net.au>
>Sent: Dec 19, 2010 10:12 PM
>To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
>Subject: Re: [freetds] Missing libtdsodbc.so on Solaris
>
>Hi,
>
>Not on Solaris - that appears to be a linux feature:
>
>$ cat /etc/malloc.conf
>cat: cannot open /etc/malloc.conf
>
>Thanks
>Adwin
>
>-----Original Message-----
>From: freetds-bounces AT lists.ibiblio.org
>[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of
>ikorot AT earthlink.net
>Sent: Monday, 20 December 2010 4:00 PM
>To: FreeTDS Development Group; FreeTDS Development Group
>Subject: Re: [freetds] Missing libtdsodbc.so on Solaris
>
>Hi, Adwin,
>
>From "man malloc" (http://www.rocketaware.com/man/man3/malloc.3.htm):
>
>"Malloc will first look for a symbolic link called /etc/malloc.conf and
>     next check the environment for a variable called MALLOC_OPTIONS
and
>fi-
>     nally for the global variable malloc_options and scan them for
>flags in
>     that order.  Flags are single letters, uppercase means on,
>lowercase
>     means off."
>
>Is Solaris has a link "/etc/malloc.conf"?
>
>Thank you.
>
>
>-----Original Message-----
>>From: Adwin Singh <singha AT redrock.net.au>
>>Sent: Dec 19, 2010 8:19 PM
>>To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
>>Subject: Re: [freetds] Missing libtdsodbc.so on Solaris
>>
>>Hi All,
>>
>>We've double checked. The --with-unixodbc option is not on by default,
>>so was not in the original freetds installation. We have rebuilt but
>>hitting an issue because the software assumes "malloc_options" is
>always
>>available. Issue is that "malloc_options" is only available on FreeBSD
>>and Linux, not Solaris.
>>
>>FYI we are running Solaris SPARC 64bit. Is it possible to get around
>>this issue or get a precompiled version for Solaris ?
>>
>>See below from our IT Guys:
>>
>>I've rebuilt with
>>
>>  root@ofdev # LDFLAGS=-L/opt/csw/lib CFLAGS=-I/opt/csw/include
>>./configure --with-unixodbc=/opt/csw/lib --prefix=/opt/freetds/
>>
>>This fails because of an assumption within the freetds software that
>>"malloc_options" is always available.
>>
>>configure:20732: checking whether malloc_options variable is present
>>configure:20758: cc -o conftest -I/opt/csw/include
>>-D_FREETDS_LIBRARY_SOURCE -L/opt/csw/lib -lmalloc conftest.c -lpthread
>>>&5
>>Undefined                       first referenced
>> symbol                             in file
>>malloc_options                      conftest.o
>>
>>However malloc_options is only available on FreeBSD and Linux; it is
>not
>>available on Solaris.
>>
>>It is not possible to enable the --with-unixodbc option
>>
>>Thanks
>>Adwin
>>
>>-----Original Message-----
>>From: Adwin Singh
>>Sent: Friday, 3 December 2010 4:39 PM
>>To: freetds AT lists.ibiblio.org
>>Subject: RE: [freetds] Missing libtdsodbc.so on Solaris
>>
>>Thanks - let me double check if configure, make and make install were
>>indeed performed.
>>
>>I'll report back.
>>
>>-----Original Message-----
>>From: freetds-bounces AT lists.ibiblio.org
>>[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Dann Corbit
>>Sent: Friday, 3 December 2010 10:39 AM
>>To: freetds AT lists.ibiblio.org
>>Subject: Re: [freetds] Missing libtdsodbc.so on Solaris
>>
>>Did you perform make?
>>
>>> -----Original Message-----
>>> From: freetds-bounces AT lists.ibiblio.org [mailto:freetds-
>>> bounces AT lists.ibiblio.org] On Behalf Of Adwin Singh
>>> Sent: Thursday, December 02, 2010 3:07 PM
>>> To: freetds AT lists.ibiblio.org
>>> Subject: [freetds] Missing libtdsodbc.so on Solaris
>>>
>>> Hi All,
>>>
>>>
>>>
>>> We have just installed freetds on a Solaris machine at /opt/freetds.
>>>
>>>
>>>
>>> We are attempting to connect from Oracle to a SQL Server machine.
>I've
>>> noticed that in the setup, it requires a library file called
>>> 'libtdsodbc.so' which should be located at /opt/freetds/lib.
>>>
>>>
>>>
>>> Unfortunately the file doesn't exist, other library files exist but
>>not
>>> this file. I believe this should have been installed as part of
>>> freetds.
>>> Do you have any suggestions on generating this library file ?
>>>
>>>
>>>
>>> Thanks for your help
>>>
>>> Adwin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> "Your Success is our Success"
>>>
>>> NOTICE: This email is intended only to be read or used by the
>>> addressee. It is confidential and may contain legally privileged
>>> information. If you are not the addressee indicated in this message
>>(or
>>> responsible for delivery of the message to such person), you may not
>>> copy or deliver this message to anyone and you should destroy this
>>> message and kindly notify the sender by reply email. Confidentiality
>>> and legal privilege are not waived or lost by reason of mistaken
>>> delivery to you.
>>>
>>> _______________________________________________
>>> FreeTDS mailing list
>>> FreeTDS AT lists.ibiblio.org
>>> http://lists.ibiblio.org/mailman/listinfo/freetds
>>_______________________________________________
>>FreeTDS mailing list
>>FreeTDS AT lists.ibiblio.org
>>http://lists.ibiblio.org/mailman/listinfo/freetds
>>
>>
>>
>>"Your Success is our Success"
>>
>>NOTICE: This email is intended only to be read or used by the
>addressee. It is confidential and may contain legally privileged
>information. If you are not the addressee indicated in this message (or
>responsible for delivery of the message to such person), you may not
>copy or deliver this message to anyone and you should destroy this
>message and kindly notify the sender by reply email. Confidentiality
and
>legal privilege are not waived or lost by reason of mistaken delivery
to
>you.
>>
>>_______________________________________________
>>FreeTDS mailing list
>>FreeTDS AT lists.ibiblio.org
>>http://lists.ibiblio.org/mailman/listinfo/freetds
>
>_______________________________________________
>FreeTDS mailing list
>FreeTDS AT lists.ibiblio.org
>http://lists.ibiblio.org/mailman/listinfo/freetds
>
>
>
>"Your Success is our Success"
>
>NOTICE: This email is intended only to be read or used by the
addressee. It is confidential and may contain legally privileged
information. If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone and you should destroy this
message and kindly notify the sender by reply email. Confidentiality and
legal privilege are not waived or lost by reason of mistaken delivery to
you.
>
>_______________________________________________
>FreeTDS mailing list
>FreeTDS AT lists.ibiblio.org
>http://lists.ibiblio.org/mailman/listinfo/freetds

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds



"Your Success is our Success"

NOTICE: This email is intended only to be read or used by the addressee. It 
is confidential and may contain legally privileged information. If you are 
not the addressee indicated in this message (or responsible for delivery of 
the message to such person), you may not copy or deliver this message to 
anyone and you should destroy this message and kindly notify the sender by 
reply email. Confidentiality and legal privilege are not waived or lost by 
reason of mistaken delivery to you.

Reformatting page.  Please Wait... done

Standard C Library Functions                           malloc(3C)

NAME
     malloc, calloc, free, memalign, realloc,  valloc,  alloca  -
     memory allocator

SYNOPSIS
     #include <stdlib.h>

     void *malloc(size_t size);

     void *calloc(size_t nelem, size_t elsize);

     void free(void *ptr);

     void *memalign(size_t alignment, size_t size);

     void *realloc(void *ptr, size_t size);

     void *valloc(size_t size);

     #include <alloca.h>

     void *alloca(size_t size);

DESCRIPTION
     The  malloc()  and  free()  functions  provide   a   simple,
     general-purpose  memory  allocation  package.  The  malloc()
     function returns a pointer to a block of at least size bytes
     suitably aligned for any use.

     The argument to free() is a pointer to  a  block  previously
     allocated  by malloc(), calloc(), or realloc(). After free()
     is executed, this space is made available for further  allo-
     cation  by  the application, though not returned to the sys-
     tem. Memory is returned to the system only upon  termination
     of  the  application.   If  ptr is a null pointer, no action
     occurs.

     Undefined results will occur if the space assigned  by  mal-
     loc()  is  overrun  or  if  some  random number is passed to
     free().

     The calloc() function allocates space for an array of  nelem
  elements of size elsize. The space is initialized to zeros.

     The memalign() function allocates size bytes on a  specified
     alignment  boundary  and  returns a pointer to the allocated
     block. The value of the returned address is guaranteed to be
     an even multiple of alignment. Note that the value of align-
     ment must be a power of two, and must  be  greater  than  or
     equal to the size of a word.

SunOS 5.8           Last change: 26 Feb 1999                    1

Standard C Library Functions                           malloc(3C)

     The realloc() function changes the size of the block pointed
     to by ptr to size bytes and returns a pointer to the (possi-
     bly moved) block.  The contents will be unchanged up to  the
     lesser  of the new and old sizes. If  ptr is NULL, realloc()
     behaves like malloc() for the specified size. If  size is  0
     and  ptr  is  not a null pointer, the space pointed to is is
     made available for further allocation  by  the  application,
     though not returned to the system. Memory is returned to the
     system only upon termination of the application.

   The     valloc()     function     is      equivalent      to
     memalign(sysconf(_SC_PAGESIZE),size).

     Each of the allocation functions returns a pointer to  space
     suitably  aligned  (after  possible  pointer  coercion)  for
     storage of any type of object.

     The malloc(), realloc(), memalign(), and  valloc() functions
     will fail if there is not enough available memory.

     The alloca() function allocates size bytes of space  in  the
     stack  frame  of  the  caller,  and returns a pointer to the
     allocated block. This temporary space is automatically freed
     when  the  caller  returns. If the allocated block is beyond
     the current stack limit, the  resulting  behavior  is  unde-
     fined.

RETURN VALUES
     If there  is  no  available  memory,   malloc(),  realloc(),
     memalign(),  valloc(),  and  calloc() return a null pointer.
      When realloc() returns NULL, the block pointed to by  ptr is
     left  intact.  If   size,  nelem,  or elsize is  0, a unique
     pointer to the arena is returned.

     If malloc(), calloc(), or realloc() returns  unsuccessfully,
     errno will be set to indicate the error. The free() function
     does not set errno.

ERRORS
     The malloc(), calloc(), and realloc()  functions  will  fail
     if:

     ENOMEM
           The physical limits of the system are exceeded by size
           bytes of memory which cannot be allocated.

     EAGAIN
           There is not enough memory available at this point  in
           time  to allocate size bytes of memory; but the appli-
           cation could try again later.

SunOS 5.8           Last change: 26 Feb 1999        

Standard C Library Functions                           malloc(3C)

USAGE
     Comparative features of malloc(3C), bsdmalloc(3MALLOC),  and
     malloc(3MALLOC) are as follows:

        o  The bsdmalloc(3MALLOC) routines afford better  perfor-
           mance, but are space-inefficient.

        o  The malloc(3MALLOC) routines are space-efficient,  but
           have slower performance.

        o  The standard, fully SCD-compliant malloc routines  are
           a trade-off between performance and space-efficiency.

ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |_____________________________|_____________________________|
    | MT-Level                    | Safe                        |
    |_____________________________|_____________________________|

SEE ALSO
     brk(2), getrlimit(2),  bsdmalloc(3MALLOC),  malloc(3MALLOC),
     mapmalloc(3MALLOC), watchmalloc(3MALLOC), attributes(5)

WARNINGS
     Undefined results will occur if the  size  requested  for  a
     block  of  memory  exceeds  the  maximum size of a process's
     heap, which may be obtained with getrlimit(2)

     The alloca() function is machine-, compiler-,  and  most  of
     all, system-dependent. Its use is strongly discouraged.

SunOS 5.8           Last change: 26 Feb 1999