On 05/25/2018 12:36 PM, Dietmar M. Zettl wrote:
Hi,
Just to let you know - build still fails with the same error.
In lib/tt/lib/db/tt_old_db.C, line 54? How can that be? Just to be
sure, check that that line contains:
dbResults = TT_DB_OK;
rather than the original (and incorrect)
dbResults = NULL;
What compiler are you using? What is the exact error message relating
to this line?
As Ulrich noted, there are other compile failures known for the BSD's -
I can see some issues opened on the Issue tracker, so even with this
fix, you will still see failures (though they will be in other places).
Until some patches come through correcting these issues, you should just
wait.
-jon
Cheers,
Dietmar
On 25 May 2018, at 19:12, Jon Trulson <j...@radscan.com> wrote:
On 05/25/2018 10:36 AM, Ulrich Wilkens wrote:
Hello,
at the moment all BSD and Solaris platforms are broken. Even some Linux
platforms doesn't built anymore. And this is for several reasons. The
error mentioned in the previous mail is only the first one. Beside of
that a lot of new warnings are generated.
Really? I've seen the warning go from the thousands down to 403 (after my fix
for the problem Dietmar reported). I will commit that one to master in a few
minutes.
I have patches against all these problems. But they need some more tests
before I can send them. I have ~40 Virtualbox test systems and some of
them have to be tested twice due to different compilers. These tests
are important because I often find new errors.
I agree!
I sure wish there was some sort of CI in SourceForge.
Unfortunately at the moment its impossible to finish such tests because
we have so many mass changes. I had already finished the tests for BSD
platforms, but then a new mass patch came out and I had to start from
scratch again.
I would need a week or better ten days without such mass changes.
Otherwise its impossible for me to fix the broken systems.
If you are talking about the mass removal of old systems patches from Chase, we
can stop putting those in master, leaving that free for testing. Only actual
fixes would go in there, and anything else goes into cde-next-2. Would that
work for you?
Also, I was not aware you were even trying to do any testing (or that you were
even on the list anymore :)...
Please feel free to let me know when you are doing this kind of stuff so I can
act appropriately in the future.
Linux systems will need (by default) to have tirpc-dev installed now. If thats
not the case on your Linux test systems, you will likely have build problems,
just FYI.
Thanks for testing/patching!
--
Jon Trulson
"But when I'm in command, every mission's a suicide mission."
- Zapp Brannigan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
--
Jon Trulson
"But when I'm in command, every mission's a suicide mission."
- Zapp Brannigan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
