[MacPorts] #44528: Error: build org.macports.build for port gettext returned: command execution failed

MacPorts noreply at macports.org
Sun Sep 14 12:23:34 PDT 2014


#44528: Error: build org.macports.build for port gettext returned: command
execution failed
--------------------------------+--------------------------
  Reporter:  wolfhard.langer@…  |      Owner:  ryandesign@…
      Type:  defect             |     Status:  new
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:  2.3.1
Resolution:                     |   Keywords:
      Port:  gettext            |
--------------------------------+--------------------------

Comment (by ryandesign@…):

 Replying to [comment:15 wolfhard.langer@…]:
 > Here ist the result of the command "sudo port -v rev-upgrade":
 >
 > {{{
 > $ sudo port -v rev-upgrade
 > --->  Scanning binaries for linking errors
 > --->  No broken files found.
 > }}}

 Ok good, nothing is broken.

 > {{{
 > $ sudo port info gettext
 > gettext @0.19.2 (devel)
 > Variants:             (+)universal
 > Description:          gettext is the GNU internationalization (i18n) and
 localization (l10n) library, used for writing multilingual programs.
 > Homepage:             http://www.gnu.org/software/gettext/
 > Library Dependencies: expat, libiconv, ncurses
 > Platforms:            darwin, freebsd, linux
 > License:              LGPL-2.1+ GPL-3+
 > Maintainers:          ryandesign at macports.org
 > }}}

 The interesting information here is that the universal variant is being
 enabled by default, presumably because you inserted "+universal" into your
 variants.conf file. If you don't actually need universal builds, you could
 remove that. Non-universal builds are faster and take less disk space.
 Also, you'll be more likely to be able to get binaries from our server,
 which should be much faster than building ports yourself.

 > In ticket:43886 the string "/AppleInternal" also can be found. And the
 string "/opt/sfw" can be found in ticket:43947.

 Hmm, ok. Do you actually have these paths on disk? If not, then we can
 ignore it. I'm just not familiar with the behavior of trace mode ("`-t`").

 > I would like to ask you if you could check if eventually the contents in
 ticket:43947 is related to my ticket?

 I don't see any similarities to your situation.

-- 
Ticket URL: <https://trac.macports.org/ticket/44528#comment:16>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list