On 29/05/2017 5:25 PM, Magnus Ihse Bursie wrote:
Maybe we should have a way to scan the source tree for files with
problematic names, like *#* or *,*...? Or CachedFind should be written
to handle *#* files properly?
I have a recollection that these temp files used to cause a different
kind of error that was much more obvious. I remember commenting that it
was good that the build failed because you wouldn't be building waht you
expected. But this "missing separator" error is just ridiculously
obscure. :( Though something you should only get bitten by once.
Cheers,
David
/Magnus
On 2017-05-24 08:49, David Holmes wrote:
On 24/05/2017 4:44 PM, Erik Joelsson wrote:
Hello David,
That error means something goes wrong when evaluating the macro body.
Unfortunately make will not give you any better message than that. If
you didn't change anything in make/common/NativeCompilation.gmk, the
most likely cause is that you have changed a variable that is used in
there, or in one of the parameters in that call, and that variable
now has some character in it that gets misinterpreted, typically a
comma or dollar would be the culprits.
Or a # :(
Thanks Erik. Offlist Christine F. suggested I look for editor temp
files but I didn't find any. But by using the trace output and running
the find command - there it was: .#constantPool.cpp
Wow! What an insane waste of time. :(
David
/Erik
On 2017-05-24 01:44, David Holmes wrote:
I just sync'd my local project with jdk10/hs and am getting a
strange build error:
Building targets 'images test-image' in configuration 'linux-x64-debug'
lib/CompileJvm.gmk:207: *** missing separator. Stop.
Line 207 is:
$(eval $(call SetupNativeCompilation, BUILD_LIBJVM, \
so it can't in itself have a missing separator!
I don't know how to try and debug this - any suggestions?
Thanks,
David
