-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build errors w/master #402
Comments
Hi Bill, you using the latest repo provided version of qpid proton? Unfortunately I think the latest qpid proton version introduces some issues which came up around time of the last RC I'll have a closer look |
Related: #272 |
HI Frank: Thanks for the quick reply -- nice to hear from you. The deprecated warnings do in fact appear because the default version of qpid on CentOS 7 is now 0.29 (from epel). I uninstalled that and installed 0.28 from the rpm's, and that took care of the deprecated warnings. However, that didn't solve the linker error. I poked around a bit and the following declaration looked a bit suspicious:
Removing the I also have no clue why the appveyor build doesn't get the error, but as above a simple checkout and vanilla build on CentOS 7 does trigger the error. |
I feel like there's no good reason to static nor inline that function so i'd be inclined to just take both keywords out |
Created a PR for this -- left inline, although optimizer will prob do that anyway, can't hurt. This builds on both CentOS 7 and Mac OS. If you prefer we can lose the inline completely -- your call. |
just created a pr in upstream repo for this...#408 |
Resolved in #408 |
Hi Frank:
Just starting to get back up to date with latest OpenMAMA, and I'm getting build errors:
This is on CentOS 7.7, but I see the same build errors on CentOS 6.9.
I've compared my build logs against the build logs at https://ci.appveyor.com/project/fquinner/openmama-gnbjp/branch/master and don't see any obvious reason for build to fail, but I do see one other difference that is odd: I'm getting deprecated errors which don't appear in appveyor build:
Again, this is all pretty vanilla:
Any hints would be appreciated -- thanks! Hope all's well with you.
The text was updated successfully, but these errors were encountered: