[Info-vax] MySql for OpenVMS

[tadamsmar]

On Jan 13, 9:09 am, tadamsmar <tadams... at yahoo.com> wrote:
> On Jan 11, 10:55 pm, Arne Vajhøj <a... at vajhoej.dk> wrote:
>
>
>
>
>
> > On 11-01-2010 12:02,tadamsmarwrote:
>
> > > On Dec 18 2009, 10:34 pm, Arne Vajhøj<a... at vajhoej.dk>  wrote:
> > >> On 18-12-2009 11:58,tadamsmarwrote:
>
> > >>> I want to interface to an instrument that uses MySql for TCPIP
> > >>> communications.
>
> > >>> I am downloading MySql for OpenVMS.
>
> > >>> I wonder if I will find a programming interface in the download, or
> > >>> merely a user interface.
>
> > >>> I need a programming interface so I can get data from the instrument
> > >>> into an existing Fortran program.
>
> > >>> (the instrument also has a serial interface, but we would prefer to
> > >>> use ethernet.)
>
> > >> SYS$COMMON:[MYSQL051.INCLUDE]
> > >> SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB
> > >> SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_UPPER.OLB
>
> > >> should include a MySQL client lib (MySQL C API).
>
> > > I am trying my first links, but I get  lot of errors.
>
> > > I am starting with a small C program that calls mysql_init.
>
> > > For some reason, I have to link  to SYS$COMMON:[MYSQL051.VMS.LIB]
> > > MYSQLCLIENT_UPPER.OLB.  I am not using upper case, but I can't
> > > link to SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB for some
> > > reason.
>
> > > Anyway, I get messages for a bunch of unresolved symbols in client.  I
> > > have included all available .OLB files in the link, but the symbols
> > > remain usresolved.
> > > I have located some of the symbols in other OLB files, but they are
> > > OLB files
> > > with MIXED in the name.  There does not seem to be a full set of OLB
> > > files with upper case symbols.  But I don't even know why I need to
> > > link to upper case
> > > symbols, it makes no sense to me.
>
> > > The messages don't seem to be indentifying real problems for the
> > > resulting exe file.
> > > The exe file seems to run fine, but of course I can't fully check it
> > > out this with only a call to mysql_init to make sure things are really
> > > going to work.
>
> > > Does anyone know how to resolve this symbols in the link?
>
> > Try:
>
> > $ cc /include=sys$common:[mysql051.include]/names=as_is foobar
> > $ link foobar+ -
> >         sys$common:[mysql051.vms.lib]mysqlclient_mixed/lib+ -
> >         sys$common:[mysql051.vms.lib]libssl_mixed/lib+ -
> >         sys$common:[mysql051.vms.lib]libcrypto_mixed/lib
>
> > Arne- Hide quoted text -
>
> > - Show quoted text -
>
> Thanks!
>
> That cleared up the bulk of the link messages.  Here are the ones that
> I
> still get:
>
> %LINK-W-MULPSC, conflicting attributes for psect mysql_port
>         in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT_MIXE
> D.OLB;1
> %LINK-W-MULPSC, conflicting attributes for psect mysql_unix_port
>         in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT_MIXE
> D.OLB;1
> %LINK-W-MULPSC, conflicting attributes for psect sql_protocol_typelib
>         in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT_MIXE
> D.OLB;1
> %LINK-W-NUDFSYMS, 2 undefined symbols:
> %LINK-I-UDFSYM,         compress
> %LINK-I-UDFSYM,         uncompress
> %LINK-W-USEUNDEF, undefined symbol compress referenced
>         in psect $LINK$ offset %X00000050
>         in module my_compress file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT
> _MIXED.OLB;1
> %LINK-W-USEUNDEF, undefined symbol uncompress referenced
>         in psect $LINK$ offset %X000000B0
>         in module my_compress file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT
> _MIXED.OLB;1- Hide quoted text -
>
> - Show quoted text -

The psect conflicts were because I compiling with CC/EXTER=COMMON