Opened 16 years ago
Closed 15 years ago
#16834 closed defect (worksforme)
iso-codes 3.2: he.mo: No such file or directory
Reported by: | philbrisco@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | iso-codes |
Description (last modified by jmroot (Joshua Root))
iso-codes 3.2 fails to compile due to recursion errors. The following are the relevant error messages:
Error: Target org.macports.destroot returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_iso-codes/work/iso-codes-3.2" && make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_iso-codes/work/destroot " returned error 2 make[3]: *** [install-data-hook] Error 71 make[2]: *** [install-data-am] Error 2 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing. PhillipBrisco:build phillipbrisco$ port info iso-codes iso-codes 3.2, devel/iso-codes http://pkg-isocodes.alioth.debian.org/
Change History (7)
comment:1 follow-up: 2 Changed 16 years ago by jmroot (Joshua Root)
Description: | modified (diff) |
---|
comment:2 Changed 16 years ago by philbrisco@…
Replying to jmr@…:
Those actually aren't the relevant error messages, they only say what failed at a very high level. The primary error message would be earlier on.
I actually concatenated the info about the recursion errors onto the original errors. This may be confusing, so I am giving the entire output I encountered while trying to install the iso-codes port through macports.
---> Staging iso-codes into destroot Error: Target org.macports.destroot returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_iso-codes/work/iso-codes-3.2" && make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_iso-codes/work/destroot " returned error 2 Command output: install: he.mo: No such file or directory install: hu.mo: No such file or directory install: it.mo: No such file or directory install: ja.mo: No such file or directory install: ko.mo: No such file or directory install: lt.mo: No such file or directory install: ml.mo: No such file or directory install: nb.mo: No such file or directory install: nl.mo: No such file or directory install: nn.mo: No such file or directory install: pl.mo: No such file or directory install: pt.mo: No such file or directory install: pt_BR.mo: No such file or directory install: ro.mo: No such file or directory install: ru.mo: No such file or directory install: sk.mo: No such file or directory install: sl.mo: No such file or directory install: sr.mo: No such file or directory install: sv.mo: No such file or directory install: th.mo: No such file or directory install: tr.mo: No such file or directory install: uk.mo: No such file or directory install: vi.mo: No such file or directory install: zh_CN.mo: No such file or directory install: zh_HK.mo: No such file or directory install: zh_TW.mo: No such file or directory make[3]: *** [install-data-hook] Error 71 make[2]: *** [install-data-am] Error 2 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing.
comment:3 Changed 16 years ago by philbrisco@…
Urgh! Let's try it with some formatting.
---> Staging iso-codes into destroot Error: Target org.macports.destroot returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_iso-codes/work/iso-codes-3.2" && make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_iso-codes/work/destroot " returned error 2 Command output: install: he.mo: No such file or directory install: hu.mo: No such file or directory install: it.mo: No such file or directory install: ja.mo: No such file or directory install: ko.mo: No such file or directory install: lt.mo: No such file or directory install: ml.mo: No such file or directory install: nb.mo: No such file or directory install: nl.mo: No such file or directory install: nn.mo: No such file or directory install: pl.mo: No such file or directory install: pt.mo: No such file or directory install: pt_BR.mo: No such file or directory install: ro.mo: No such file or directory install: ru.mo: No such file or directory install: sk.mo: No such file or directory install: sl.mo: No such file or directory install: sr.mo: No such file or directory install: sv.mo: No such file or directory install: th.mo: No such file or directory install: tr.mo: No such file or directory install: uk.mo: No such file or directory install: vi.mo: No such file or directory install: zh_CN.mo: No such file or directory install: zh_HK.mo: No such file or directory install: zh_TW.mo: No such file or directory make[3]: *** [install-data-hook] Error 71 make[2]: *** [install-data-am] Error 2 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing.
comment:5 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Summary: | iso-codes 3.2 Error: Target org.macports.destroot...returned error 2 → iso-codes 3.2: he.mo: No such file or directory |
iso-codes has been updated several times since this ticket was filed, and it installs fine for me. Do you still see the problem with the current version (3.10.3)? If so, please clean the port and try again with debug output, and attach it to this ticket as a file, so that we see the complete error message.
sudo port clean iso-codes sudo port -d install iso-codes
comment:6 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | iso-codes Error 71 2 1 removed |
---|
comment:7 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Those actually aren't the relevant error messages, they only say what failed at a very high level. The primary error message would be earlier on.