[Bug 194561] New: graphics/libEGL, graphics/libglapi, graphics/libGL and graphics/libglesv2 are using msgfmt from gettext during build stage but does not depend on it

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Oct 23 18:29:08 UTC 2014


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194561

            Bug ID: 194561
           Summary: graphics/libEGL, graphics/libglapi, graphics/libGL and
                     graphics/libglesv2 are using msgfmt from gettext
                    during build stage but does not depend on it
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: m.tsatsenko at gmail.com
                CC: x11 at FreeBSD.org
                CC: x11 at FreeBSD.org

Usually they are using gettext installed by some dependency which has NLS
enabled by default, but we can not rely on it.
I have custom NLS-disabled poudriere repo and I am getting build failures:
===>  Building for libglapi-10.3.0
gmake[1]: Entering directory
'/wrkdirs/usr/ports/graphics/libglapi/work/Mesa-10.3.0/src/mesa/drivers/dri/common/xmlpool'
cd ../../../../../.. && gmake  am--refresh
cd ../../../../../.. && gmake  am--refresh
Updating (ca) ca/LC_MESSAGES/options.mo from ca.po.
msgfmt: not found
Makefile:638: recipe for target 'ca/LC_MESSAGES/options.mo' failed
gmake[1]: *** [ca/LC_MESSAGES/options.mo] Error 127
gmake[1]: Leaving directory
'/wrkdirs/usr/ports/graphics/libglapi/work/Mesa-10.3.0/src/mesa/drivers/dri/common/xmlpool'
*** Error code 2

Stop.
make: stopped in /usr/ports/graphics/libglapi

Adding 
USES=           gettext:build
to the Makefile (all of graphics/libEGL, graphics/libglapi, graphics/libGL and 
graphics/libglesv2) solves the problem.

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Maintainers CC'd

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-x11 mailing list