Re: MySQL port compile problems [was Re: rb-rubygems does not work]

On 8/24/06, [email protected] <[email protected]> wrote:
> On 8/24/06, Ryan Schmidt <[email protected]> wrote:
> > On Aug 24, 2006, at 09:16, [email protected] wrote:
>
> [snip]
> > > i have used it several times and haven't had any problems (although
> > > this morning i found that the mysql5 port seems hosed on ppc/10.4.7 -
> > > didn't have that problem on intel last week). i routinely install via
> >
> > What's the matter with the mysql5 port?
> >
> > FYI I submitted a bug to request that it be updated to 5.0.24.
> >
> > http://bugzilla.opendarwin.org/show_bug.cgi?id=10534
>
> it appears to die during compile (which is strange since i installed
> 5.0.22 on an intel machine recently without issue). i can put the full
> log somewhere if you'd like to inspect it.

updating my ports tree, i gave 5.0.24 a go on my ppc and it still died
on the SHA1 errors.


jpm.giant-squid ~ -=> sudo port install mysql5 +server
Portfile changed since last build; discarding previous state.
--->  Fetching mysql5
--->  Attempting to fetch mysql-5.0.24.tar.gz from
http://mysql.mirrors.pair.com/Downloads/MySQL-5.0/
--->  Verifying checksum(s) for mysql5
--->  Extracting mysql5
--->  Applying patches to mysql5
--->  Configuring mysql5
--->  Building mysql5 with target all
Error: Target com.apple.build returned: shell command "cd
"/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_databases_mysql5/work/mysql-5.0.24"
&& make all" returned error 2
Command output: sha1.c: In function 'mysql_sha1_reset':
sha1.c:102: error: 'context' undeclared (first use in this function)
sha1.c:102: error: (Each undeclared identifier is reported only once
sha1.c:102: error: for each function it appears in.)
sha1.c:114: error: 'SHA_SUCCESS' undeclared (first use in this function)
sha1.c: At top level:
sha1.c:135: error: parse error before '*' token
sha1.c: In function 'mysql_sha1_result':
sha1.c:148: error: 'context' undeclared (first use in this function)
sha1.c:157: error: 'SHA1_HASH_SIZE' undeclared (first use in this function)
sha1.c:158: error: 'Message_Digest' undeclared (first use in this function)
sha1.c:160: error: 'SHA_SUCCESS' undeclared (first use in this function)
sha1.c: At top level:
sha1.c:179: error: parse error before '*' token
sha1.c: In function 'mysql_sha1_input':
sha1.c:182: error: 'length' undeclared (first use in this function)
sha1.c:183: error: 'SHA_SUCCESS' undeclared (first use in this function)
sha1.c:197: error: 'context' undeclared (first use in this function)
sha1.c:198: error: 'message_array' undeclared (first use in this function)
sha1.c: At top level:
sha1.c:242: error: parse error before '*' token
sha1.c: In function 'SHA1ProcessMessageBlock':
sha1.c:257: error: 'context' undeclared (first use in this function)
sha1.c: At top level:
sha1.c:345: error: parse error before '*' token
sha1.c: In function 'SHA1PadMessage':
sha1.c:354: error: 'context' undeclared (first use in this function)
make[2]: *** [sha1.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Status 1 encountered during processing.



strangely though, on my intel machine, after i had upgraded from
5.0.22 to 5.0.24 (without the SHA1 issue seen on my ppc), my rails
applications became quite unhappy accessing the database. it would
often work on the first try but the second would die. i needed to
uninstall, clean and reinstall rb-mysql5 and then it worked without a
problem. is this expected?

regards,
jean-pierre