Bug 6324 - "make install" fails to create pam_winbind.mo in Solaris
Summary: "make install" fails to create pam_winbind.mo in Solaris
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.3
Classification: Unclassified
Component: Build environment (show other bugs)
Version: 3.3.4
Hardware: Sparc Solaris
: P3 normal
Target Milestone: ---
Assignee: Karolin Seeger
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-05 03:58 UTC by Reinhard Sojka
Modified: 2009-05-05 04:32 UTC (History)
0 users

See Also:

Attachments
changed sequence for options and filenames for command msgfmt (391 bytes, patch)
2009-05-05 04:08 UTC, Reinhard Sojka 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Reinhard Sojka 2009-05-05 03:58:54 UTC 
Hello!

"make install" on Solaris 10 (with locale de_DE.UTF-8) displays this error message

Installing /export/source/work_sol10/samba-3.3.4_cluster_kern/source//locale/pam_winbind/de.po as ///global/kern/samba334/share/locale/de/LC_MESSAGES/pam_winbind.mo
ERROR: Cannot open file -f.
==============================================================
MO files for pam_winbind are installed.
==============================================================

and leaves pam_winbind.mo as an empty file
Comment 1 Reinhard Sojka 2009-05-05 04:08:34 UTC 
Created attachment 4114 [details]
changed sequence for options and filenames for command msgfmt

on Solaris the command msgfmt needs to be called with "msgfmt [Options] filename.po" otherwise it fails 
(msgfmt on Linux seems to be more tolerant)
Comment 2 Reinhard Sojka 2009-05-05 04:14:08 UTC 
Oops, forgot to mention that whole path for the patch - it is for file <Path>/samba-3.3.4/source/script/installmo.sh
Comment 3 Björn Jacke 2009-05-05 04:23:46 UTC 
this is already fixed in master, Karolin, can you pick that to the 3.3 branch, too? (commit da06a345cc2)
Comment 4 Karolin Seeger 2009-05-05 04:32:01 UTC 
Yep. Will be fixed in 3.3.5.

Thanks for reporting!