Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4244 - mysql fails to emerge
Summary: mysql fails to emerge
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Mark Guertin
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-27 11:14 UTC by johnathan spectre
Modified: 2003-02-04 19:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description johnathan spectre 2002-06-27 11:14:40 UTC
11:13:23 (148.69 KB/s) - `/usr/portage/distfiles/mysql-3.23.51.tar.gz' saved
[11203102/11203102]

>>> md5 ;-) mysql-3.23.51.tar.gz
uid=60(mysql) gid=60(mysql) groups=60(mysql)
>>> Unpacking source...
>>> Unpacking mysql-3.23.51.tar.gz
 * patching for <gentoo-1.3 system (gcc-2.95.x)..
patching file acinclude.m4
patching file include/nisam.h
patching file scripts/mysql_install_db.sh
patching file scripts/safe_mysqld.sh
patching file mysys/default.c
patching file sql/mysqld.cc
aclocal: /usr/share/aclocal/gimpprint.m4: 698: duplicated macro
`_AM_PATH_GIMPPRINT_CHECK_REGISTER_DEFAULTS'

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_unpack, Line -5, Exitcode 1
!!! (no error message)

!!! emerge aborting on  /usr/portage/dev-db/mysql/mysql-3.23.51.ebuild .
Comment 1 johnathan spectre 2002-06-27 12:22:56 UTC
well i solved the problem by unmerging gimp-print, removing
/usr/share/aclocal/gimpprint.m4, emerging gimp-print and then emerge -u mysql.
Comment 2 johnathan spectre 2002-06-27 12:27:16 UTC
i had the same problem on another system trying to update mysql. that system
didn't have gimp-print installed, but the bad file was in aclocal still. i seem
to remember an update to aclocal recently, maybe it's the cause?
Comment 3 Mark Guertin 2002-06-27 22:34:17 UTC
Johnathon:

I am unable to reproduce this across 3 gentoo ppc boxes. :(  All 3 boxes (1.2
based installs) are working fine for this and gnome2.

Is your other box also based on a 1.1a install?  It's the only thing I can think
of that may be causing these problems (although how I don't know).
Comment 4 Jacob Perkins 2002-06-28 01:06:33 UTC
this is a duplicate of 4157
Comment 5 johnathan spectre 2002-07-02 09:00:59 UTC
yes. all my boxes are based on 1.2.. i'm thinking of reinstalling them when 1.3
is available. i thought upgrading 1.1a via emerge would basically give you a 1.2
system?
Comment 6 Mark Guertin 2002-07-02 09:15:04 UTC
1.1a upgraded is still not 1.2 (unless you re-bootstrapped etc).

This is a duplicate, see 4157 for fix.