Wireshark · Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x8

["Graham Bloice" <graham.bloice@xxxxxxxxxxxxx>]

> > On Fri, Feb 17, 2012 at 04:49:37AM -0800,
> > buildbot-no-reply@xxxxxxxxxxxxx
> > wrote:
> > >
> > > http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/2
> > > 09
> > >
> > > Buildbot URL: http://buildbot.wireshark.org/trunk/
> > >
> > > Buildslave for this Build: windows-xp-x86
> > >
> > > Build Reason: scheduler
> > > Build Source Stamp: 41047
> > > Blamelist: jmayer
> > >
> > > BUILD FAILED: failed nmake all
> >
> > The reason is the move of util.c to ui/util.c:
> >
> > Linking wireshark.exe
> > 	link @C:\Users\buildbot\AppData\Local\Temp\nm4B0.tmp
> > LINK : fatal error LNK1181: cannot open input file 'ui/util.obj'
> > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> > Studio 9.0\VC\BIN\x86_amd64\link.EXE"' : return code '0x49d'
> >
> > Most likely it has a problem with the / instead of \ in uil/util.obj.
> > Does someone have an idea how to resolve this?
> 
> util.obj is being produced in the top level root directory, but the linker
is
> looking for it in ui\.  I'm looking at the makefile now.
> 

Hmm.  I think this would need an explicit build rule.  As it stands, the
compiler is told to compile ui/util.c when in the top level directory, so
that's where the object file is placed.  The linker is told to look for
ui/util.obj and complains.

Graham Bloice