The Samba-Bugzilla – Bug 3200
Visual Studio 2003 gives ICE with Precompiled Header on Samba Drive
Last modified: 2005-12-15 08:26:42 UTC
When building OpenOffice.org on Windows XP SP2 with the build tree on a shared
Samba drive, Visual Studio gives the following error:
fatal error C1001: INTERNAL COMPILER ERROR
'f:\vs70builds\3077\vc\Compiler\Utc\src\P2\p2symtab.c', line 1609)
This seems to be caused by a problem with Visual Studio and Precompiled Header
files on Samba drives - see the following URLs
See also the bug report at openoffice.org:
I will try to get a small test case, and I presume some kind of log information
/ network capture is required to resolve what's causing this, but don't know the
details of how to do this.
try setting 'allocation roundup size = 0' for the share in question.
You might also want to review the smb.conf(5) for the option as it
contains some information specific to MS Visual Studio.
Setting "roundup allocation size = 0" definately fixes this, so closing this bug
out. Microsoft knows about this - the ball is now in their court.
I still get an ICE reliably on a shared Samba drive with the following options:
allocation roundup size = 0
dos filetime resolution = no
fake directory create times = no
(from reading man smb.conf)
vpath.c(0) : fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
This is on compiling make for mozilla within compiling OpenOffice.org so its a pretty complex setup, I'll try reduce the test case and report back.
Created attachment 1600 [details]
stripped down version of make used by mozilla that produces this error when built with nmake -f NMakefile
The attached tarball compiles fine with nmake -f NMakefile on a local disk, but fails on a shared samba disk with the allocation roundup size set correctly
Reopening, please tell me what I can do to test and debug this...
Did you create the project on the Samba share ? If not (you moved the project over after being created on a local drive or Windows share) then all bets are off. Microsoft told us precompiled headers are only supported locally on the machine that created them.
The project is just created from the tarball which contains only sourcefiles, so the precompiled header is created from scratch, if thats what you mean.
I'm also going to try testing on a shared Windows drive from another machine to check it isn't just a bug on remote drives.
Compiles fine when untarred and made in exactly the same way in a shared folder from another Windows machine, so this is exactly resolvable to a difference between Windows shared folders and Samba shared folders.
Jeremy, What do you want to do with this one