Opened 12 years ago

Closed 11 years ago

#3155 closed defect (fixed)

msgfmt detection not working

Reported by: lschiere Owned by: elb
Milestone: Component: unclassified
Version: Keywords:
Cc:

Description

There are two aspects to this bug.

1) autogen.sh/configure do not detect msgfmt on my system, which is required to successfully build in the po directory, however configure does not fail. This is despite the fact that it appears that we test for it, and should be failing if it does not detect it.

I am judging that it does not detect it based on the fact that in the resulting makefile, these variables are left unset.

2)this failure is happening even though msgfmt is in fact installed, and is installed in a directory that is in my path, and from which other binaries are found for the configure process.

This is an OSX system using macports.

Attachments (1)

config.log (140.5 KB) - added by lschiere 12 years ago.

Download all attachments as: .zip

Change History (6)

Changed 12 years ago by lschiere

comment:1 Changed 12 years ago by lschiere

  • Owner changed from sadrul to elb

file attached as requested.

comment:2 Changed 12 years ago by deryni

msgfmt is being found in /opt/local/bin/msgfmt but a test compilation in the gettext check is failing.

comment:3 Changed 11 years ago by sadrul

  • Component changed from finch (gnt/ncurses) to unclassified

comment:4 Changed 11 years ago by elb

Ahh ... somehow I lost track of this bug, I'm glad sadrul pinged it.

Luke, is this still happening? What is the actual error that you get at build time?

comment:5 Changed 11 years ago by lschiere

  • Resolution set to fixed
  • Status changed from new to closed

Now that I have a build environment set back up on my laptop, I cannot duplicate this with 10.5. I cannot test to see if it would still be a problem with 10.4 (which has a different version of xtools), but I am going to close this.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!