Bug 62729 - libtool detect gpm even without devel
Summary: libtool detect gpm even without devel
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gpm
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Eido Inoue
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-04 23:23 UTC by Kang Jeong-Hee
Modified: 2007-04-18 16:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-06 08:45:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Kang Jeong-Hee 2002-04-04 23:23:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020326

Description of problem:
libtool gpm as -lgpm but I have nothing about gpm-devel.
so compilation failed. I have to install gpm-devel.
'cos I cannot remove gpm by dependency of links, aumix, etc.
I think this is guilty of gpm.spec.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. checkout gimp from gnome cvs
2. ./autogen.sh --prefix=/usr --sysconfdir=/etc
3. make
	

Actual Results:  .../plug-ins/common fail to go ahead.
told: -lgpm is absent.

Expected Results:  why gpm talked about?

Additional info:

I tried rawhide gpm and nothing change.
only gpm-devel saved this trouble.

Comment 1 Bernhard Rosenkraenzer 2002-04-05 08:46:42 UTC
gimp's broken configure scripts are not a gpm problem.

Comment 2 Kang Jeong-Hee 2002-04-06 10:36:04 UTC
Yes, it's gpm problem. gimp-1.3 has nothing about gpm in source directory anywhere.
grep gpm * -ir is clear.
the issued stage of compilation is in control of libtool.
and I think gpm.spec set to provide libtool-related file in gpm not gpm-devel.
or libtool problem?

Comment 3 Nils Philippsen 2004-08-06 08:44:34 UTC
From a quick glance at it this should be working in current gpm
packages. Closing as CURRENTRELEASE.


Note You need to log in before you can comment on or make changes to this bug.