Bug 162062 – MySQL >=4.1.22 fails to compile on Alpha?

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Johan Nilsson 2007-01-14 16:24:32 UTC]

I am running a Alpha EV6 system with dev-db/mysql-4.1.21 installed. But I am no longer able to upgrade MySQL since compilation fails when it can't find a defination.

alpha-unknown-linux-gnu-gcc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr\"" -DDAT
ADIR="\"/var/lib/mysql\"" -DSHAREDIR="\"/usr/share/mysql\"" -DHAVE_CONFIG_H -I.
-I.. -I../innobase/include -I../include -I../include -I../regex -I.     -DDBUG_O
FF -mieee -mcpu=ev4 -DHAVE_ERRNO_AS_DEFINE=1   -MT stacktrace.o -MD -MP -MF .dep
s/stacktrace.Tpo -c -o stacktrace.o stacktrace.c
stacktrace.c: In function `print_stacktrace':
stacktrace.c:189: error: `SIGRETURN_FRAME_COUNT' undeclared (first use in this f
unction)
stacktrace.c:189: error: (Each undeclared identifier is reported only once
stacktrace.c:189: error: for each function it appears in.)
make[4]: *** [stacktrace.o] Error 1
make[4]: Leaving directory `/var/tmp/portage/mysql-4.1.22-r1/work/mysql/sql'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/mysql-4.1.22-r1/work/mysql/sql'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/mysql-4.1.22-r1/work/mysql/sql'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/mysql-4.1.22-r1/work/mysql'
make: *** [all] Error 2

!!! ERROR: dev-db/mysql-4.1.22-r1 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  ebuild.sh, line 1255:   Called mysql_src_compile
  mysql.eclass, line 603:   Called die

!!! emake failed
!!! If you need support, post the topmost build error, and the call stack if relevant.

Reproducible: Always

Steps to Reproduce:
1. emerge mysql




According to http://bugs.mysql.com/bug.php?id=23256 an update seem to be missing for alpha architecture, but they also say alpha is not supported anymore by MySQL.  Should all new versions of MySQL on alpha be masked from now on? May the patch be included in portage?

[Comment 1 Luca Longinotti (RETIRED) 2007-01-14 17:51:47 UTC]

The patch will be included in the 4.1.22 and 5.0.26 releases of our MySQL packages, later versions already do include the patch (or the alpha* packages will include the patches once properly released, at least). I'll see to fix this in the next days, thanks for the report!
Best regards, CHTEKK.

[Comment 2 Brian Parkhurst 2007-02-23 21:48:11 UTC]

http://lists.mysql.com/commits/14037

[Comment 3 Jose Luis Rivero (yoswink) (RETIRED) 2007-04-19 15:40:12 UTC]

(In reply to comment #1)
> The patch will be included in the 4.1.22 and 5.0.26 releases of our MySQL
> packages, later versions already do include the patch (or the alpha* packages
> will include the patches once properly released, at least). I'll see to fix
> this in the next days, thanks for the report!
> Best regards, CHTEKK.
> 

@Luca: I've tried today to install mysql-4.1.22-r1 (stable version for alpha) and I still getting the same error. Seems like mysql-5 series, that also were affected by this bug (see bug #144999), are now fixed (mysql-5.0.38) and I will mark it stable very soon. 

Anyway, to have mysql4 series fixed would be cool. 

Thanks a lot.

[Comment 4 Tobias Klausmann (RETIRED) 2008-12-14 20:18:55 UTC]

Nothing depends on mysql-4 specifically, so I dropped the keyword for those ebuilds altogether.