Hi folks,
Is there any utility in publishing building
experience, like with non-standard
configurations, and such? It's sort of
'experimental data' after all, right?
If so, what's the preferred form and the
'repository' for that?
Anyway, I've just completed building yesterday's
trunk with gcc 13.2.0 set to c++11 mode, on a
rather up-to-date Slackware Linux system.
No immediate issues with apps as yet, but there
was one peculiar problem when building.
I'm usually configuring the build with
--with-system-boost=no
and recently switched the downloaded boost
version to 1.79, per the advise in this same
maillist. It was building okay with end-2022
Slackware's gcc (11-something, don't remember).
But after going to gcc 13 (which came with
updating to January 2024 Slackware) the
rebuilding snagged in configmgr module, couldn't
go further. What happended was GCC now somehow
manages in such configuration to reach for the
system's boost header files which produces
definitions mismatch.
So I had to switch to
--with-system-boost=yes
and things went well after that.
However, the questions remains -- what had
actually happened there (and how to resolve)?
The command line failing was:
R=/d/home/ty/c/+ooo/aoo45 && S=$R/main &&
O=$S/solver/450/unxlngx6.pro && W=$O/workdir &&
mkdir -p $W/CxxObject/configmgr/source/
$W/Dep/CxxObject/configmgr/source/ && g++ -DCPP
U_ENV=gcc3 -DCUI -DENABLE_GTK -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -DGCC -DHA
VE_GCC_VISIBILITY_FEATURE -DLINUX -DNDEBUG
-DNEED_ALIGN16 -DOPTIMIZE -DOSL_DEBUG_LEVEL=0
-DPRODUCT -DPRODUCT_FULL -DSOLAR_JAVA -DSUPD=450
-DUNIX -DUNX -DVCL -DX86_64 -DXML_STATIC
-D_PTHREADS -D_REENTRANT -Wall -Wendif-labels
-Wextra -Wno-ctor-dtor-privacy -Wno-non-v
irtual-dtor -Wshadow -fPIC -fmessage-length=0
-fno-common -fno-strict-aliasing -fuse-cxa-
atexit -fvisibility-inlines-hidden
-fvisibility=hidden -std=c++11 -pipe
-DEXCEPTIONS_ON
-fexceptions -fno-enforce-eh-specs -Os -ggdb3
-finline-limit=0 -fno-inline -fno-default-
inline -c $S/configmgr/source/access.cxx -o
$W/CxxObject/configmgr/source/access.o -MMD -
MT $W/CxxObject/configmgr/source/access.o -MF
$W/Dep/CxxObject/configmgr/source/access.d
\
-I$S/configmgr/source/ -I$O/inc/stl
-I$O/inc/external -I$O/inc -I$S/solenv/unxlngx6/i
nc -I$S/solenv/inc -I$S/res -I$S/tools/inc
-I$S/comphelper/inc -I$S/solenv/inc/Xp31 -I/us
r/lib64/java/include
-I/usr/lib64/java/include/linux
-I/usr/lib64/java/include/native_thr
eads/include -I$S/configmgr/inc/pch
-I$O/inc/offapi -I$O/inc/udkapi
and it produced the following (cut down to save
space):
In file included from
/d/home/ty/c/+ooo/aoo45/main/solver/450/unxlngx6.pro/inc/boost/move
/algorithm.hpp:29,
from
/d/home/ty/c/+ooo/aoo45/main/solver/450/unxlngx6.pro/inc/boost/move
/move.hpp:32,
from
/d/home/ty/c/+ooo/aoo45/main/solver/450/unxlngx6.pro/inc/boost/unor
dered/unordered_map.hpp:19,
from
/d/home/ty/c/+ooo/aoo45/main/solver/450/unxlngx6.pro/inc/boost/unor
dered_map.hpp:17,
from
/d/home/ty/c/+ooo/aoo45/main/configmgr/source/modifications.hxx:29,
from
/d/home/ty/c/+ooo/aoo45/main/configmgr/source/access.hxx:67,
from
/d/home/ty/c/+ooo/aoo45/main/configmgr/source/access.cxx:88:
/usr/include/boost/move/algo/move.hpp: In
function ‘F boost::uninitialized_move(I, I, F)’
:
/usr/include/boost/move/algo/move.hpp:124:4:
error: ‘BOOST_MOVE_TRY’ was not declared in
this scope; did you mean ‘BOOST_MOVE_RET’?
How could this happen with the compiling options
being set as they were?
I've tried adding -I-, but it seems to be
completely deprecated.
-Yury
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
