BootstrapCompile Error #94

Open
johnjelinek opened this Issue Dec 10, 2013 · 19 comments

Projects

None yet

3 participants

@johnjelinek

When the build fails, a dialog box pops up saying BootstrapCompile Error and I have to close that box before I can see the compilation errors.

@frankhale frankhale was assigned Dec 10, 2013
@speige
speige commented Dec 11, 2013

Can you add a screenshot including the error?

@frankhale

I'm going to try to reproduce this now.

@frankhale frankhale was assigned Dec 13, 2013
@frankhale

I'm not able to reproduce this. Is there anyway I can get a sample project or some code that can reproduce this error?

@frankhale

Awesome, thank you!

On Thu, Dec 12, 2013 at 9:21 PM, John Jelinek IV
notifications@github.comwrote:

[image: fail]https://f.cloud.github.com/assets/873610/1739439/4072a3a0-639d-11e3-8e55-3e4ac84fb96f.gif


Reply to this email directly or view it on GitHubhttps://github.com/vsClojure/vsClojure/issues/94#issuecomment-30481456
.

@frankhale

Hi @johnjelinek ,

I've duplicated your code but I cannot reproduce the error you are getting. Which version of Visual Studio are you using?

boostrap-error-not-reproducable

@frankhale

I think you are on 2012 because I'm on 2013 and your screen looks slightly different. I can definitely find references to BootstrapCompile in the ClojureCLR source code. I'll try tomorrow to duplicate this on VS2012.

@johnjelinek

I was using 2013 Premium, I was just clipping some of the UI though.

@johnjelinek

Note the command path is referencing VisualStudio\12.0\Extensions... (VS 2013)

@frankhale

Okay, interesting. Is this a vanilla project with just that code I can see
in the screenshot? Do you have any special references?

On Thu, Dec 12, 2013 at 10:33 PM, John Jelinek IV
notifications@github.comwrote:

Note the command path is referencing VisualStudio\12.0\Extensions... (VS
2013)


Reply to this email directly or view it on GitHubhttps://github.com/vsClojure/vsClojure/issues/94#issuecomment-30483979
.

@johnjelinek

plain vanilla, this happens with all projects.

On Thu, Dec 12, 2013 at 9:54 PM, Frank Hale notifications@github.comwrote:

Okay, interesting. Is this a vanilla project with just that code I can see
in the screenshot? Do you have any special references?

On Thu, Dec 12, 2013 at 10:33 PM, John Jelinek IV
notifications@github.comwrote:

Note the command path is referencing VisualStudio\12.0\Extensions... (VS
2013)


Reply to this email directly or view it on GitHub<
https://github.com/vsClojure/vsClojure/issues/94#issuecomment-30483979>
.


Reply to this email directly or view it on GitHubhttps://github.com/vsClojure/vsClojure/issues/94#issuecomment-30484604
.

@frankhale

Which version of the vsClojure extension are you using?

@speige
speige commented Dec 13, 2013

@johnjelinek Would you mind clicking "view details" & take a screenshot as well? Also, would you mind clicking "debug" to see if it'll give you a stack trace that you can screenshot? If so, if the stack trace has any inner exceptions that give more detail than the main exception, would you expand each of them & then take a screenshot?

@speige
speige commented Dec 13, 2013

@johnjelinek This is because your namespace "log-analysis.webapi" doesn't match your filename "webapi.clj". The filename & namespace must match. I understand it's a code smell to not have the period in the filename. There is an issue logged for it, hopefully we'll have it fixed in the next version.

I'm not sure why sometimes it's showing build succeeded, but I'm pretty sure it's never succeeding. You could double check whether a .dll file is being generated in the bin folder.

Also, unrelated, but your parameters for defn -somethings is still wrong, it should be "[this x]" -> This technically will only matter when you call the method from c# code.

@johnjelinek

@frankhale I'm using vsClojure 2.1.5.

@speige Here's the view details:

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: Clojure.Compile.exe
  Problem Signature 02: 1.0.0.0
  Problem Signature 03: 51fb5503
  Problem Signature 04: Clojure
  Problem Signature 05: 1.3.0.0
  Problem Signature 06: 51fb5516
  Problem Signature 07: 3d48
  Problem Signature 08: 15
  Problem Signature 09: clojure.lang.Compiler+Compiler
  OS Version:   6.3.9600.2.0.0.400.8
  Locale ID:    1033
  Additional Information 1: fa95
  Additional Information 2: fa95115db40da237ce684e8c160735e9
  Additional Information 3: abe9
  Additional Information 4: abe98b4cec9190df46e09e4536e637a9

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Here's the debug stacktrace:

clojure.lang.Compiler.CompilerException was unhandled
Message: An unhandled exception of type 'clojure.lang.Compiler.CompilerException' occurred in ManyConsole.dll
Additional information: System.ArgumentException: Unmatched delimiter: )
   at clojure.lang.LispReader.UnmatchedDelimiterReader.Read(PushbackTextReader reader, Char rightdelim)
   at clojure.lang.LispReader.read(PushbackTextReader r, Boolean eofIsError, Object eofValue, Boolean isRecursive), compiling: (webapi.clj:7:36)

@johnjelinek

@speige A .dll is being generated when it says build succeeded even though the filename does not match the namespace.

Also, I noted your this comment :) I'll change it when trying to reference from C#. Thanks!

@frankhale

@johnjelinek, I've also seen these DLL's built even when the compile fails. I think this is because the ClojureCLR compiler builds more than one DLL for a particular set of source code. This is probably an intermediate DLL. It could all be in the way the ClojureCLR compiler emits it's code.

I know this issue has been opened a while but have you worked on any more ClojureCLR code and experienced this again?

I've definitely seen the "BootstrapCompile Error" while doing command line builds of ClojureCLR code so we know this is coming from ClojureCLR compiler. Now, I wonder if there was a change between 2.1.5 and 2.1.6 of vsClojure that made a change to the way the compiler is invoked which would cause it to display the error in a dialog instead of redirecting it to the Visual Studio output & error windows.

I'm sure we could benefit from updating the Clojure 1.5 compiler to the latest 1.5.x version.

@frankhale frankhale closed this May 20, 2014
@frankhale

Development is non-existent,,,, will reopen if development picks up again.

@johnjelinek

👍
On May 19, 2014 10:23 PM, "Frank Hale" notifications@github.com wrote:

Development is non-existent,,,, will reopen if development picks up again.


Reply to this email directly or view it on GitHubhttps://github.com/vsClojure/vsClojure/issues/94#issuecomment-43582882
.

@frankhale frankhale reopened this Aug 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment