Opened 8 months ago

Last modified 3 weeks ago

#69553 new defect

ruby33 fails on Tiger: error: 'MD5_Init' undeclared here (not in a function); did you mean 'CC_MD5_Init'?

Reported by: barracuda156 Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.9.1
Keywords: tiger Cc: fhgwright (Fred Wright)
Port: ruby32, ruby33

Description

gmake[2]: Entering directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_ruby33/ruby33/work/ruby-3.3.0/ext/digest/md5'
compiling md5init.c
md5init.c:17:33: error: 'MD5_Init' undeclared here (not in a function); did you mean 'CC_MD5_Init'?
     (rb_digest_hash_init_func_t)MD5_Init,
                                 ^~~~~~~~
                                 CC_MD5_Init
gmake[2]: *** [Makefile:253: md5init.o] Error 1
gmake[2]: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_ruby33/ruby33/work/ruby-3.3.0/ext/digest/md5'
gmake[1]: *** [exts.mk:253: ext/digest/md5/all] Error 2

Also, looks like pthread part should have a fallback for 10.4, though it does not err out on this code:

In file included from thread.c:263:0:
thread_pthread.c: In function 'native_thread_native_thread_id':
thread_pthread.c:2780:24: warning: implicit declaration of function 'pthread_mach_thread_np'; did you mean 'pthread_getugid_np'? [-Wimplicit-function-declaration]
         return ULL2NUM(pthread_mach_thread_np(pthread_self()));
                        ^~~~~~~~~~~~~~~~~~~~~~
                        pthread_getugid_np

Change History (2)

comment:1 Changed 3 weeks ago by fhgwright (Fred Wright)

Cc: fhgwright added

comment:2 Changed 3 weeks ago by fhgwright (Fred Wright)

I fixed this ages ago, but never saw the ticket. It should be closed.

Note: See TracTickets for help on using tickets.