Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » Mt.cpp broken compile using 9604 nightly snap-shot (Our app fails to compile using IDE: multiple definitions in Mt.cpp and Mt.h)
Mt.cpp broken compile using 9604 nightly snap-shot [message #46138] Wed, 16 March 2016 16:14 Go to next message
jfranks is currently offline  jfranks
Messages: 36
Registered: September 2014
Location: Houston, Texas
Member
index.php?t=getfile&id=4969&private=0Environment: Linux Mint 17.3
The U++ IDE compiles and installs okay.
However, as we start to build our application from scratch, errors emit during compile of Core/Mt.cpp.
The complaint is multiple definitions of Upp::ReadMemoryBarrier() and Upp::WriteMemoryBarrier().

An in-line version of this method is enabled in Mt.h at the same time that
the method is enabled for compile in Mt.cpp.

Our build flags: GCC GUI X11 MT DEBUG M32

We are not using either of these methods in our application.
As a work-around, I used #if 0 around each method in the Mt.cpp file in order to compile without errors.

Here is a session snapshot that demonstrates the issue of just trying to compile Core/Mt.cpp and
the errors that emit.
Re: Mt.cpp broken compile using 9604 nightly snap-shot [message #46153 is a reply to message #46138] Fri, 18 March 2016 19:31 Go to previous message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
jfranks wrote on Wed, 16 March 2016 16:14
index.php?t=getfile&id=4969&private=0Environment: Linux Mint 17.3
The U++ IDE compiles and installs okay.
However, as we start to build our application from scratch, errors emit during compile of Core/Mt.cpp.
The complaint is multiple definitions of Upp::ReadMemoryBarrier() and Upp::WriteMemoryBarrier().

An in-line version of this method is enabled in Mt.h at the same time that
the method is enabled for compile in Mt.cpp.

Our build flags: GCC GUI X11 MT DEBUG M32

We are not using either of these methods in our application.
As a work-around, I used #if 0 around each method in the Mt.cpp file in order to compile without errors.

Here is a session snapshot that demonstrates the issue of just trying to compile Core/Mt.cpp and
the errors that emit.


Hopefully fixed.

Mirek
Previous Topic: Simple class to handle variables used by different threads
Next Topic: How to break the server loop ?
Goto Forum:
  


Current Time: Thu Apr 18 23:13:39 CEST 2024

Total time taken to generate the page: 0.04753 seconds