I switched to gcc44, and get the following build error:
Entering /tmp/apache_oo/svn_clean/ooo/main/xml2cmp/source/finder
Compiling: xml2cmp/source/finder/dependy.cxx
/tmp/apache_oo/svn_clean/ooo/main/solver/340/unxlngx6.pro/bin/makedepend: error
while loading shared libraries:
/tmp/apache_oo/svn_clean/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6:
file too short
dmake: Error code 127, while making '../../unxlngx6.pro/obj/dependy.obj'
dmake: '../../unxlngx6.pro/obj/dependy.obj' removed.
$ file
/tmp/apache_oo/svn_clean/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6
/tmp/apache_oo/svn_clean/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6:
ASCII text
$ cat
/tmp/apache_oo/svn_clean/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6
INPUT ( -lstdc++_nonshared /usr/lib64/libstdc++.so.6 )
Any ideas?
Thanks, Oli
On 9/1/2011 12:06 PM, Marc-Oliver Straub wrote:
Seems like a bug in the <slist> header comping with gcc 4.1.2 on RHEL5.6.
Comparing RHEL56 gcc 4.4.4 <slist> with gcc 4.1.2 <slist>, I noticed
that the 4.4.4 version contains additional using statements:
using std::__true_type;
using std::__false_type;
Can others please check whether their gcc 4.1.2 headers contain these
statements? Is this a RedHat problem? Is this a compiler bug, and do
we need to workaround this?
Bye, Oli
On 9/1/2011 11:45 AM, Marc-Oliver Straub wrote:
Build failed in autodoc module:
Entering /tmp/apache_oo/ooo/main/autodoc/source/display/html
Making: all_display_html.dpobj
Compiling: autodoc/source/display/html/aryattrs.cxx
Compiling: autodoc/source/display/html/cfrstd.cxx
Compiling: autodoc/source/display/html/chd_udk2.cxx
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:413:
error: '__true_type' has not been declared
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:419:
error: '__false_type' has not been declared
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:537:
error: '__true_type' has not been declared
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:544:
error: '__false_type' has not been declared
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:775:
error: '__false_type' has not been declared
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:
In instantiation of '__gnu_cxx::slist<csi::xml::Element*,
std::allocator<csi::xml::Element*> >':
../../../source/inc/estack.hxx:43: instantiated from
'EStack<csi::xml::Element*>'
/tmp/apache_oo/ooo/main/autodoc/source/display/html/easywri.hxx:64:
instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:419:
error: 'template<class _InputIterator> void
__gnu_cxx::slist::_M_assign_dispatch(_InputIterator, _InputIterator,
int) [with _InputIterator = _InputIterator, _Tp = csi::xml::Element*,
_Alloc = std::allocator<csi::xml::Element*>]' cannot be overloaded
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:413:
error: with 'template<class _Integer> void
__gnu_cxx::slist::_M_assign_dispatch(_Integer, _Integer, int) [with
_Integer = _Integer, _Tp = csi::xml::Element*, _Alloc =
std::allocator<csi::xml::Element*>]'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:544:
error: 'template<class _InIterator> void
__gnu_cxx::slist::_M_insert_after_range(__gnu_cxx::_Slist_node_base*,
_InIterator, _InIterator, int) [with _InIterator = _InIterator, _Tp =
csi::xml::Element*, _Alloc = std::allocator<csi::xml::Element*>]'
cannot be overloaded
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/slist:537:
error: with 'template<class _Integer> void
__gnu_cxx::slist::_M_insert_after_range(__gnu_cxx::_Slist_node_base*,
_Integer, _Integer, int) [with _Integer = _Integer, _Tp =
csi::xml::Element*, _Alloc = std::allocator<csi::xml::Element*>]'
dmake: Error code 1, while making
'../../../unxlngx6.pro/obj/chd_udk2.obj'
On 9/1/2011 10:33 AM, Marc-Oliver Straub wrote:
RedHat Enterprise Linux 5.6 64-bit, gcc 4.1.2
./configure --disable-mozilla --without-junit
...
checking whether to enable RandR support... checking for XRANDR... no
checking X11/extensions/Xrandr.h usability... no
checking X11/extensions/Xrandr.h presence... yes
configure: WARNING: X11/extensions/Xrandr.h: present but cannot be
compiled
configure: WARNING: X11/extensions/Xrandr.h: check for missing
prerequisite headers?
configure: WARNING: X11/extensions/Xrandr.h: see the Autoconf
documentation
configure: WARNING: X11/extensions/Xrandr.h: section "Present
But Cannot Be Compiled"
configure: WARNING: X11/extensions/Xrandr.h: proceeding with the
compiler's result
checking for X11/extensions/Xrandr.h... no
configure: error: X11/extensions/Xrandr.h could not be found. X11
dev missing?
Adding --disable-randr to the configure flags succeeds.
However, I see the following error in the configure output:
The variable COMMON_BUILD_TOOLS is set to: $SRC_ROOT/external/common
Use of uninitialized value in string eq at ./set_soenv line 1987.
The variable TMPDIR is set to: /tmp
Now running bootstrap...
On 8/31/2011 8:45 AM, Marc-Oliver Straub wrote:
I'm one of those "hidden" people...
Currently I don't have bandwidth to jump into active development,
but I'd like to stay up to date.
My focus is on the low-level stuff like sal, URE/UDK and IPC
bridges including performance.
I'm using RedHat Enterprise Linux 5.
Bye, Oli
On 8/30/2011 9:24 PM, Rob Weir wrote:
We're blessed to have experienced OOo hackers on the list who have
already jumped on the new code repository and started making
improvements.
But I see we have 214 people subscribed to the mailing list,
including
many who were not previously working on OOo code. This is great.
Growing the community to bring in new developers is key to the
success
of the project.
Do any of you want to get an AOOo dev environment set up, so you can
build OpenOffice? If so, please respond to this note, and state what
operating system you are interested in building on.
Based on this information, we can have a discussion on how best to
get
you up to speed, whether via Q&A on this list, via IRC chat, a phone
conference or maybe even a virtual machine image.
-Rob