Bugzilla Bug 46432

I see messages of

In function 'initialize_mousetype':: undefined reference to 'Gpm_Open'
In function 'initialize_mousetype':: undefined reference to 'gpm_fd'
In function '_nc_mouse_event':: undefined reference to 'Gpm_GetEvent'
In function 'mouse_activate':: undefined reference to 'gpm_fd'

!!! ERROR: app-text/aspell-0.50.3 failed.
!!! Function src_compile, Line 35, Exitcode 2
!!! (no error message)

In the forums, a workaround seems to have been discoverd:

USE="-gpm" emerge ncurses aspell

Which seems fine if you don't want to use the mouse in the console, but this probably should be looked into (yes, I want to use the mouse in the console).

Oddly enough, it had been successfully emerged previously, and I'm now in the middle of an emerge -e world, as I changed my CFLAGS flags to be significantly less aggressive and wanted all apps built with the new CFLAGS.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




CFLAGS="-march=pentium4 -O2 -fPIC -DPIC -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
USE includes "gpm ncurses aspell"

I have the same problem, with the same type of system.

CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"

Tested against aspell-0.50.4.1 and aspell-0.50.5. Is this a gpm error?

Also tested to downgrade gpm from 1.20.1 to gpm-1.20.0-r6, this didn't help. Any ideas?

This is caused by a bug in the ebuild. It does not include the -lgpm flag in
LDFLAGS.

To work around this, edit the build, and change the pkg_setup function to
match:

pkg_setup() {
    if [ ${ARCH} = "ppc" ] ; then
        CXXFLAGS="-O2 -fsigned-char"
        CFLAGS=${CXXFLAGS}
    fi
    LDFLAGS="-lgpm"
}

*** Bug 46399 has been marked as a duplicate of this bug. ***

Ideally it should be:

use gpm && LDFLAGS="-lgpm"

with a USE=gpm dep for gpm. 

We can't really check to see if ncurses was built with USE=gpm, so for now we're stuck with that little kludge.

Upping severity, this'll effect a pretty large number of people.

Committed.

*** Bug 46423 has been marked as a duplicate of this bug. ***