GNU nano - Bugs: bug #54265, running 'make' errors out with:...
You are not allowed to post comments on this tracker with your current authentication level.
bug #54265: running 'make' errors out with: recipe for target 'bg.gmo' failed
Submitter: | None | ||
Submitted: | Sun 08 Jul 2018 01:03:55 AM UTC | ||
Severity: | 3 - Normal | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Mon 10 Sep 2018 05:46:42 PM UTC, comment #9: |
Benno Schulenberg <bens> |
Sun 08 Jul 2018 12:59:53 PM UTC, comment #8: I uninstalled gettext, and got:
|
Peter Passchier <pepa65> |
Sun 08 Jul 2018 12:26:19 PM UTC, comment #7: With "fixed" I mean: configure will now fail when msgfmt is missing (when building from a git repo). |
Benno Schulenberg <bens> |
Sun 08 Jul 2018 12:15:11 PM UTC, comment #6: Fixed in git, commit fa454abb. |
Benno Schulenberg <bens> |
Sun 08 Jul 2018 11:06:49 AM UTC, comment #5: Hrrrm... I seem to remember that configure.ac used to check for the availability of gettext, but in the history of the file I cannot find anything of the sort. But... thinking a bit more, this makes sense: gettext would never be required for a normal build (from a tarball) -- it is only required when building from svn/git.
|
Benno Schulenberg <bens> |
Sun 08 Jul 2018 10:07:12 AM UTC, comment #4: Hmmm... Configure used to give a warning when gettext was not installed. But I've removed the gettext package from my system, and ./configure does not complain, but does the same as for you: it finds the colon as the msgfmt and msgmerge commands. :| When I touch nano.pot and vi.po and then run make, I get:
|
Benno Schulenberg <bens> |
Sun 08 Jul 2018 08:26:35 AM UTC, comment #3: grep -i msgfmt config.log
|
Peter Passchier <pepa65> |
Sun 08 Jul 2018 08:01:26 AM UTC, comment #2: Instead of semicolons it is better to use &&. So please run:
|
Benno Schulenberg <bens> |
Sun 08 Jul 2018 03:26:33 AM UTC, comment #1: But yes, I only started make after I thought configure was completing without errors. But, looking again, it seemed (to me) to complete without errors, because nothing at the end of the output indicated anything wrong. But scrolling up, there was a fatal error that groff wasn't installed:
|
Peter Passchier <pepa65> |
Sun 08 Jul 2018 01:03:55 AM UTC, original submission:
Reposting from http://savannah.gnu.org/patch/?9661
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-09-10 | bens | Open/Closed | Open | Closed | |
2018-07-08 | bens | Status | In Progress | Fixed | |
2018-07-08 | bens | Status | None | In Progress | |
2018-07-08 | bens | Assigned to | None | bens | |
Summary | [patch #9661] running make errors out with: recipe for target 'bg.gmo' failed | running 'make' errors out with: recipe for target 'bg.gmo' failed |
Powered by Savane 3.13-4448.
Corresponding source code
Released in 3.0. Thanks again for reporting, and for testing.