Back to Questions
2.5k
views7
comments
build errors
f#

Hey guys,

I often get the "Build Failed" message but *no* errors pop up in the Error List. Has anyone else experienced this, and have any debugging tips in this regard? One situation when this often happens is when the build order is wrong, but there are other times as well when this happens - and I'll document those when I find them ;-)

If anyone has some debugging suggestions for this particular situation - please do let me know.

Regards,
Tejus

.

Hi, I have the same problem but nothing seems to work. I have tried the build order -
but my files are in the correct order. And all my files are open.

I get the "Build Failed" message but no errors.

any Ideas ??

By on 8/22/2006 5:41 AM ()

Could you attach a screenshot or text dump of the "Output" window after the build?

Thx

don

By on 8/22/2006 7:13 AM ()

I fixed the error - I was optimistically trying to ignore a field in a tagged-datatype by using the _ wildcard.

e.g.
Set.Contains(DataType(value, _), datatype_set)

Here is screen-dump of the output window after a reconstruction of the error

------ Rebuild All started: Project: Klaim, Configuration: Debug Win32 ------
Compiling Project Klaim ...
Executing
C:\fsharp-1.1.11.7\FSharp-1.1.11.7\bin\fsc.exe --fullpaths --progress -Ooff -g -o "c:\Klaim\klaim.exe" "abstractsystem.fsi" "abstractsystem.fs" "test.fs"
in directory
C:Klaim\
Typecheck implementation AbstractSystem
Typecheck implementation Test

C:\Klaim\abstractsystem.fs(50,35): error: Anonymous expressions are only allowed in quotations.

C:\Klaim\abstractsystem.fs(50,35): error: unexpected TExpr_hole.
Klaim build failed.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

By on 8/22/2006 7:27 AM ()

Yes, we should report this earlier. There are a small number of checks which are only made in later phases of the compiler (rather than the type checker, which is run interactively)

Don

By on 8/22/2006 7:34 AM ()

Hi Tejus,

This can happen when you don't have all of your files open, or you haven't yet viewed/modified them since files that they depend on have been saved. See [link:www.strangelights.com] for a range of tips on using the Visual Dtudio extensions most effectively.

Cheers!

Don

By on 8/3/2006 1:55 PM ()

That helped - thanks!!

By on 8/3/2006 9:40 PM ()

Also, FYI, one other case that causes this error is when

1. the project DLL is loaded into the interactive shell, and
2. I've made some changes & attempt to build again (fails with no errors displayed)

This is easily fixed by quitting the Interactive shell.

By on 8/3/2006 11:59 PM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper