Hey... [snip] ---> Configuring gettext ---> Building gettext with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_gettext/work/gettext-0.17" && make all " returned error 2 Command output: rm -f t-charset.alias charset.alias /bin/sh ./config.charset 'i386-apple-darwin9.1.0' > t-charset.alias mv t-charset.alias charset.alias rm -f t-ref-add.sed ref-add.sed sed -e '/^#/d' -e 's/@''PACKAGE''@/gettext-tools/g' ref-add.sin > t- ref-add.sed mv t-ref-add.sed ref-add.sed rm -f t-ref-del.sed ref-del.sed sed -e '/^#/d' -e 's/@''PACKAGE''@/gettext-tools/g' ref-del.sin > t- ref-del.sed mv t-ref-del.sed ref-del.sed Making all in po Making all in projects make[3]: Nothing to be done for `all'. Making all in styles make[3]: Nothing to be done for `all'. Making all in misc WARNING: Warnings can be ignored. :-) if test "emacs" != no; then \ set x; \ list='start-po.el po-mode.el po-compat.el'; for p in $list; do \ if test -f "$p"; then d=; else d="./"; fi; \ set x "$@" "$d$p"; shift; \ done; \ shift; \ EMACS="emacs" /bin/sh ../../build-aux/elisp-comp "$@" || exit 1; \ else : ; fi Fatal malloc_jumpstart() error make[3]: *** [elc-stamp] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 Error: The following dependencies failed to build: gettext Error: Status 1 encountered during processing. Never did fill out a ticket with FreeBSD ports. Must have been lucky ;) Do I need to fill one out with MacPorts or is this msg sufficient? TIA.... -- Duke Normandin dukeofperl@ml1.net A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
Hi! On Jan 27, 2008, at 16:24, Duke Normandin wrote:
---> Configuring gettext ---> Building gettext with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel _gettext/work/gettext-0.17" && make all " returned error 2 Command output: rm -f t-charset.alias charset.alias /bin/sh ./config.charset 'i386-apple-darwin9.1.0' > t-charset.alias mv t-charset.alias charset.alias rm -f t-ref-add.sed ref-add.sed sed -e '/^#/d' -e 's/@''PACKAGE''@/gettext-tools/g' ref-add.sin > t- ref-add.sed mv t-ref-add.sed ref-add.sed rm -f t-ref-del.sed ref-del.sed sed -e '/^#/d' -e 's/@''PACKAGE''@/gettext-tools/g' ref-del.sin > t- ref-del.sed mv t-ref-del.sed ref-del.sed Making all in po Making all in projects make[3]: Nothing to be done for `all'. Making all in styles make[3]: Nothing to be done for `all'. Making all in misc WARNING: Warnings can be ignored. :-) if test "emacs" != no; then \ set x; \ list='start-po.el po-mode.el po-compat.el'; for p in $list; do \ if test -f "$p"; then d=; else d="./"; fi; \ set x "$@" "$d$p"; shift; \ done; \ shift; \ EMACS="emacs" /bin/sh ../../build-aux/elisp-comp "$@" || exit 1; \ else : ; fi Fatal malloc_jumpstart() error make[3]: *** [elc-stamp] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1
Error: The following dependencies failed to build: gettext Error: Status 1 encountered during processing.
Never did fill out a ticket with FreeBSD ports. Must have been lucky ;) Do I need to fill one out with MacPorts or is this msg sufficient? TIA....
MacPorts isn't really related to FreeBSD ports, FYI. The failing package seems to be gettext, not mutt. A ticket was filed for this issue two months ago: http://trac.macosforge.org/projects/macports/ticket/13381 But I thought I had already fixed this. (I resolved the ticket 6 weeks ago.) Is your ports tree up to date? Try: sudo port selfupdate sudo port clean --work gettext sudo port install gettext Does it work now? a
On 27-Jan-2008, at 9:19 PM, Ryan Schmidt wrote:
Hi!
[snip]
MacPorts isn't really related to FreeBSD ports, FYI.
Yep! I'm aware of that. How they both work is similar, however. ;)
The failing package seems to be gettext, not mutt.
Again... I realize that. That's why my quote stopped at the "gettext" choke point.
A ticket was filed for this issue two months ago:
http://trac.macosforge.org/projects/macports/ticket/13381
But I thought I had already fixed this. (I resolved the ticket 6 weeks ago.) Is your ports tree up to date? Try:
sudo port selfupdate sudo port clean --work gettext sudo port install gettext
Does it work now?
Like a charm!! Thanks. Then I did: sudo port install mutt Seems to work OK. All I need to do now is to stick a .muttrc file in $HOME. Thanks again. - dukeofperl@ml1.net A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
participants (2)
-
Duke Normandin
-
Ryan Schmidt