topic Re: Mysql link error in Operating System - OpenVMS

Mysql link error

Dario Karlen — Mon, 17 Mar 2008 15:34:21 GMT

I've installed JPFs MySQL server 5.1 on a I64 VMS V8.3. The Server is running well, but when I try to compile and link a C program some errors occur.
I ve got an option file sql.opt:
MYSQL051_ROOT:[000000.VMS.LIB]MYSQLCLIENT_MIXED.OLB/lib
MYSQL051_ROOT:[000000.VMS.LIB]LIBZ_SHR32.exe/share
DKA0:[VMS$COMMON.SYSLIB]SSL$LIBSSL_SHR32/share
DKA0:[VMS$COMMON.SYSLIB]SSL$LIBCRYPTO_SHR32/share

and a compile/link program:
$ cc/float=ieee/iee=denorm/name=(as_is, trunc) -
/INCLUDE=SYS$COMMON:[000000.MYSQL051.INCLUDE]mysql testmysql
$ link testmysql, -
INA_DISK:[INA.PROGS.DK]sql/opt, -
MYSQL051_ROOT:[000000.VMS.LIB]MYSQLCLIENT_MIXED/lib

but when I try to run the compile/link program, some undefined symbols are detected:
ina > @linkmysql
%ILINK-W-NUDFSYMS, 2 undefined symbols:
%ILINK-I-UDFSYM, my_time
%ILINK-I-UDFSYM, thd_lib_detected
%ILINK-W-USEUNDEF, undefined symbol my_time referenced
section: $CODE$
offset: %X0000000000000270 slot: 2
module: client
file: MYSQL051_ROOT:[000000.VMS.LIB]MYSQLCLIENT_MIXED.OLB;1
%ILINK-W-USEUNDEF, undefined symbol my_time referenced
section: $CODE$
offset: %X00000000000002F0 slot: 2
module: client
file: MYSQL051_ROOT:[000000.VMS.LIB]MYSQLCLIENT_MIXED.OLB;1
%ILINK-W-USEUNDEF, undefined symbol thd_lib_detected referenced
section: $CODE$
offset: %X0000000000000000 slot: 1
module: my_thr_init
file: MYSQL051_ROOT:[000000.VMS.LIB]MYSQLCLIENT_MIXED.OLB;1
%ILINK-W-USEUNDEF, undefined symbol thd_lib_detected referenced
section: $CODE$
offset: %X0000000000000010 slot: 1
module: my_thr_init
file: MYSQL051_ROOT:[000000.VMS.LIB]MYSQLCLIENT_MIXED.OLB;1

but my_time should be included in the mysqlclient_mixed.olb.
Any ideas how I can solve this problem?
Thanks in advance.

Re: Mysql link error

Hoff — Mon, 17 Mar 2008 16:06:42 GMT

Check with JFP. There's a potential for an error or for a improvement in the kit or in the kit documentation.

I'd guess that the dependency isn't found until after the OLB has been processed.

And an OLB? I'll assume there's a reason JFP used that approach and not a shareable image version of that code.

As for options (and off the top), I might well try the following:

$ link testmysql, -
MYSQLCLIENT_MIXED/lib, -
sql/opt

and try:

$ link testmysql, -
sql/opt, -
MYSQLCLIENT_MIXED/lib, -
MYSQLCLIENT_MIXED/lib

--

And MYSQL051_ROOT:[000000.VMS.LIB]?

if that's a real rooted logical name, try:

MYSQL051_ROOT:[VMS.LIB]

Do also look for a logical that specifically references the VMS Library area.

Re: Mysql link error

Jan van den Ende — Mon, 17 Mar 2008 16:15:14 GMT

Re Hoff:

>>>
And MYSQL051_ROOT:[000000.VMS.LIB]?

if that's a real rooted logical name, try:

MYSQL051_ROOT:[VMS.LIB]
<<<

Yeah, one more case of that BL***D [000000. construct.
Regular readers will know my aversion.

Dario: DO follow Hoff's request, and report the result! I have a feeling that it DOES make a difference, and I would love another example of whence my aversion comes.

Proost.

Have one on me

jpe

Re: Mysql link error

Dario Karlen — Tue, 18 Mar 2008 07:45:22 GMT

Thanks for your answer, I tried as you mentioned:

sql.opt:
MYSQL051_ROOT:[VMS.LIB]MYSQLCLIENT_MIXED.OLB/lib
MYSQL051_ROOT:[VMS.LIB]LIBZ_SHR32.exe/share
DKA0:[VMS$COMMON.SYSLIB]SSL$LIBSSL_SHR32/share
DKA0:[VMS$COMMON.SYSLIB]SSL$LIBCRYPTO_SHR32/share

linkmysql.com:
$ cc/float=ieee/iee=denorm/name=(as_is, trunc) -
/INCLUDE=mysql testmysql
$ link testmysql, -
sql/opt, -
MYSQL051_ROOT:[VMS.LIB]MYSQLCLIENT_MIXED/lib, -
MYSQL051_ROOT:[VMS.LIB]MYSQLCLIENT_MIXED/LIB

but still the same result: two undefined symbols.
ina > @linkmysql
%ILINK-W-NUDFSYMS, 2 undefined symbols:
%ILINK-I-UDFSYM, my_time
%ILINK-I-UDFSYM, thd_lib_detected
%ILINK-W-USEUNDEF, undefined symbol my_time referenced
section: $CODE$
offset: %X0000000000000270 slot: 2
module: client
file: MYSQL051_ROOT:[VMS.LIB]MYSQLCLIENT_MIXED.OLB;1

there is only one MySQL symbol:
ina > sh log *sql*

(LNM$PROCESS_TABLE)

(LNM$JOB_884FECC0)

(LNM$GROUP_000300)

(LNM$SYSTEM_TABLE)

"MYSQL051_ROOT" = "ALESA$DKA0:[SYS0.SYSCOMMON.MYSQL051.]"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)

Re: Mysql link error

x2084 — Tue, 18 Mar 2008 08:45:27 GMT

I would double check if the names are in the library. LIBRARY/LIST/NAMES should do that. The undefined symbols are in lowercase, the OLB needs to have them in lowercase as well.

On the other hand, an OLB can contain object modules without having their symbols in the library's symbol table. You can ask ANALYZE/OBJECT to look at all object modules in the library and format the symbols. If you find the symbol in that output you can explicitly include the object module.

Anyway, as already said, it looks like something is missing in the documentation or in the envnironment.

Re: Mysql link error

Dario Karlen — Tue, 18 Mar 2008 09:07:19 GMT

Thanks.

I checked the library:
lib/list/names MYSQLCLIENT_MIXED.OLB

Module my_time

TIME_to_ulonglong
TIME_to_ulonglong_date
TIME_to_ulonglong_datetime
TIME_to_ulonglong_time
calc_daynr
calc_days_in_year
check_date
check_time_range
days_in_month
init_time
log_10_int
my_TIME_to_str
my_date_to_str
my_datetime_to_str
my_system_gmt_sec
my_time_to_str_default
number_to_datetime
set_zero_time
str_to_datetime
str_to_time
year_2000_handling

my_time seems OK.

anal/obj MYSQLCLIENT_MIXED.OLB output is attached.

Re: Mysql link error

Dario Karlen — Tue, 18 Mar 2008 10:26:44 GMT

I was wrong, my_time is not the modul, its the symbol in module client:

%ILINK-W-USEUNDEF, undefined symbol my_time referenced
section: $CODE$
offset: %X0000000000000270 slot: 2
module: client
file: MYSQL051_ROOT:[VMS.LIB]MYSQLCLIENT_MIXED.OLB;1

and
%ILINK-W-USEUNDEF, undefined symbol thd_lib_detected referenced
section: $CODE$
offset: %X0000000000000000 slot: 1
module: my_thr_init
file: MYSQL051_ROOT:[VMS.LIB]MYSQLCLIENT_MIXED.OLB;1

how can I fix this? I already send a mail to JFP.

Module client

cli_advanced_command
cli_read_rows
cli_safe_read
default_client_charset_info
end_server
free_old_query
free_rows
my_connect
mysql_close
mysql_detach_stmt_list
mysql_errno
mysql_error
mysql_fetch_lengths
mysql_fetch_row
mysql_free_result
mysql_get_server_version
mysql_get_ssl_cipher
mysql_init
mysql_init_character_set
mysql_num_fields
mysql_num_rows
mysql_options
mysql_port
mysql_read_default_options
mysql_real_connect
mysql_real_query
mysql_reconnect
mysql_select_db
mysql_send_query
mysql_set_character_set
mysql_ssl_set
mysql_store_result
mysql_unix_port
not_error_sqlstate
set_mysql_error
sql_protocol_names_lib
sql_protocol_typelib
unknown_sqlstate
unpack_fields

Module my_thr_init

THR_thread_count
_my_thread_var
my_thread_dbug_id
my_thread_end
my_thread_end_wait_time
my_thread_global_end
my_thread_global_init
my_thread_init
my_thread_name

Re: Mysql link error

labadie_1 — Tue, 18 Mar 2008 11:16:40 GMT

JFP is on holiday this week, wait for next Monday.

Re: Mysql link error

Jan van den Ende — Tue, 18 Mar 2008 12:06:32 GMT

@ Gerard Labadie:

>>>
JFP is on holiday this week, wait for next Monday.
<<<

Surely, in France Easter Monday ("Lundi de Paques") is a holiday?

So, make that "wait for Tuesday".

Proost.

Have one on me.

jpe

Re: Mysql link error

Willem Grooters — Wed, 19 Mar 2008 06:19:26 GMT

I vaguely remember from other discussions (on JFP's MySQL list and forum, probably) that there are TWO libraries: The one you seem to use is allowing mixed-case names, and there must be one using uppercase only.
Worth a look to try that one.

Or put your question here:
http://www.pi-net.dyndns.org/piforum/viewforum.php?f=3

Re: Mysql link error

Jean-François Piéronne — Wed, 19 Mar 2008 08:11:58 GMT

Dario,

Sorry for the inconvenience.

this is a know problem in the 5.1.22 IA64 kit.

It is fixed in 5.1.23 AXP and in the future 5.1.23 IA64 kits.

If you take a look at the log of the repository:
http://hgm.vmspython.dyndns.org/vmsmysql/shortlog
You can view what has be done.

We expect to release a new IA64 kits probably in a few week. We are fixing some others problems.

If you want I can build and put online the correct libraries newt week.

About why it's libraires and not shareable:
Old MySQL kit contains the clients part as a shareables with bot cases symbols. But between version MySQL change a lot (and often) the API and it will be very difficult to maintains a compatible shareable.
This is the reason why I have switch to libraries.
Myy be a separate client kits with a full version number (for examples 5122) can contains shareables.
Using server kit and a client kit will allow to upgrade the server without impacting the client part. And will allow to have many client shareable installed. Open question.

JF

Re: Mysql link error

Dario Karlen — Wed, 19 Mar 2008 09:01:52 GMT

JFP

Thanks a lot for your answer.
I would really appreciate the new libray, but I know you re on holiday, so please enjoy it and don't care about this ;) The problem can still be fixed later.

Wish you a nice holiday.

Re: Mysql link error

Jörg Sporer — Tue, 08 Apr 2008 13:08:16 GMT

Hello,

I have exactly the same problem as Dario. Are there any news about the fixed libraries?

Best regards
JÃ¶rg

Re: Mysql link error

Dario Karlen — Tue, 08 Apr 2008 13:12:20 GMT

Hello JÃ¶rg

I sent an email to JFP (who ports MySQL to VMS) two weeks ago but no response so far. The only thing we can do at the moment is wait...As soon as I receive a response I will post it here.

Dario

Re: Mysql link error

Jean-François Piéronne — Wed, 09 Apr 2008 19:41:35 GMT

Darion, JÃ¶rg,

Sorry I'm busy on others projects.
I have rebuild the libraries using MySQL 5.1.23
Download link:
http://www.pi-net.dyndns.org/anonymous/kits/tmp/ia64/mysqlclient05123_ia64.zip

I haven't done any tests except building the standard clients.

JF

Re: Mysql link error

Jörg Sporer — Fri, 11 Apr 2008 14:00:50 GMT

Hello JFP,

thanks for the lib. Works great!
However I still get two linker errors when using the "upper" olb:
%ILINK-I-UDFSYM, ARRAY_APPEND_STRING_UNIQUE
%ILINK-I-UDFSYM, MY_QSORT

Since I donÂ´t use those functions I can live with it. Just for your information...

Bye Joerg

Re: Mysql link error

Jean-François Piéronne — Mon, 14 Apr 2008 20:41:54 GMT

Joerg,

I will take a look and rebuild a new version.

JF