Bug 425661

Summary: resgen2 fails to build resx files if DISPLAY is unset or set to a non-existent DISPLAY
Product: [Mono] Mono: Compilers Reporter: Paul Johnson <paul>
Component: Other.Assignee: Mono Bugs <mono-bugs>
Status: RESOLVED DUPLICATE QA Contact: Mono Bugs <mono-bugs>
Severity: Normal    
Priority: P5 - None    
Version: 2.0.x   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
URL: https://bugzilla.redhat.com/show_bug.cgi?id=462005
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Paul Johnson 2008-09-11 21:26:59 UTC 
To recreate this problem

1. Download cs_obexftp sources from
http://cs-obexftp.svn.sourceforge.net/viewvc/cs-obexftp/trunk/Cs-ObexFtp/Cs-ObexFtp.tar.gz
2. unset DISPLAY
3. ./configure && make

What I'm seeing is this

make[1]: Entering directory `/builddir/build/SOURCES/Cs-ObexFtp/Cs-ObexFtp'
resgen2 -usesourcepath 'Forms/About.de.resx' 'Forms/About.de.resources'
Read in 13 resources from
'/builddir/build/SOURCES/Cs-ObexFtp/Cs-ObexFtp/Forms/About.de.resx'
Writing resource file...  Done.
resgen2 -usesourcepath 'Forms/About.fr.resx' 'Forms/About.fr.resources'
Read in 9 resources from
'/builddir/build/SOURCES/Cs-ObexFtp/Cs-ObexFtp/Forms/About.fr.resx'
Writing resource file...  Done.
resgen2 -usesourcepath 'Forms/About.it.resx' 'Forms/About.it.resources'
Read in 15 resources from
'/builddir/build/SOURCES/Cs-ObexFtp/Cs-ObexFtp/Forms/About.it.resx'
Writing resource file...  Done.
resgen2 -usesourcepath 'Forms/About.resx' 'Forms/About.resources'
Error: Invalid ResX input.
Inner exception: An exception was thrown by the type initializer for
System.Windows.Forms.TableLayoutPanel  Line 230, position 5.
make[1]: *** [Forms/About.resources] Error 1
make[1]: Leaving directory `/builddir/build/SOURCES/Cs-ObexFtp/Cs-ObexFtp'
make: *** [all-recursive] Error 1

If DISPLAY is set correctly, the compile works fine.

Using Mono 2.0 RC 1
Comment 1 Dominik Mierzejewski 2008-09-11 22:03:48 UTC 
I've already filed it as bug 425647.

*** This bug has been marked as a duplicate of bug 425647 ***