forlano Messages: 1207 Registered: March 2006 Location: Italy
Senior Contributor
Hello,
I get the errors
/home/luigi/upp/uppsrc/Core/ValueUtil.h (87): error: expected unqualified-id before '=' token
/home/luigi/upp/uppsrc/Core/ValueUtil.h (88): error: expected unqualified-id before '=' token
on lubuntu 18.10 and nightly build 12599. Theide was compiled with version 11393, but I think this should not be a problem.
Is this a known problem or it is my machine the need a review?
/home/luigi/upp/uppsrc/Core/ValueUtil.h (87): error: expected unqualified-id before '=' token
/home/luigi/upp/uppsrc/Core/ValueUtil.h (88): error: expected unqualified-id before '=' token
on lubuntu 18.10 and nightly build 12599. Theide was compiled with version 11393, but I think this should not be a problem.
Is this a known problem or it is my machine the need a review?
/home/luigi/upp/uppsrc/Core/ValueUtil.h (87): error: expected unqualified-id before '=' token
/home/luigi/upp/uppsrc/Core/ValueUtil.h (88): error: expected unqualified-id before '=' token
on lubuntu 18.10 and nightly build 12599. Theide was compiled with version 11393, but I think this should not be a problem.
Is this a known problem or it is my machine the need a review?
Thanks,
Luigi
I have tried lubuntu 18.10 with latest nightly and it seems to work fine.
forlano Messages: 1207 Registered: March 2006 Location: Italy
Senior Contributor
mirek wrote on Sun, 09 December 2018 12:39
forlano wrote on Wed, 05 December 2018 09:42
Hello,
I get the errors
/home/luigi/upp/uppsrc/Core/ValueUtil.h (87): error: expected unqualified-id before '=' token
/home/luigi/upp/uppsrc/Core/ValueUtil.h (88): error: expected unqualified-id before '=' token
on lubuntu 18.10 and nightly build 12599. Theide was compiled with version 11393, but I think this should not be a problem.
Is this a known problem or it is my machine the need a review?
Thanks,
Luigi
I have tried lubuntu 18.10 with latest nightly and it seems to work fine.
I am sorry for my bad quote. The problem appeared on a recently updated 18.04.
However it seems resolved in the new version.