After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 7138 - Cannot find libintl in some compilation
Cannot find libintl in some compilation
Status: VERIFIED FIXED
Product: GIMP
Classification: Other
Component: Internationalisation
1.x
Other FreeBSD
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2000-03-10 03:40 UTC by a.cheung2
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description a.cheung2 2001-01-28 15:49:41 UTC 
Package: gimp
Version: 1.1.18

Name........: Arthur
Email.......: a.cheung2@sympatico.ca
Platform....: P2 , Freebsd3.4
GIMP Version: 1.1.18
GTK Version.: 1.2


-- Other system notes:

--

-- Problem description:
The Makefile in some directory cannot locate libintl
--


-- How to repeat:
type "make" in the top dir
--


-- Other comments:
I fix it by putting LIBINTL= -lintl  in some Makefile ( some
variable like that)
--




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-28 10:49 -------
This bug was previously known as bug 7138 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=7138
Originally filed under the gimp product and general component.

The original reporter (a.cheung2@sympatico.ca) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, egger@suse.de.
Comment 1 Raphaël Quinet 2001-04-26 18:10:16 UTC 
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
Comment 2 Daniel Egger 2001-10-24 09:15:34 UTC 
This is likely to be fixed. Though if it is still a problem you may
want to report back as libintl can really be a nasty beast sometimes.
Comment 3 Raphaël Quinet 2002-02-12 09:43:07 UTC 
Fix is (hopefully?) part of gimp-1.2.3, which has just been released.
Bug is now CLOSED.