Pavel Janík wrote:
Hi,
You misunderstand me; I guess I was not clear enough.
you was perfectly clear.
1 Sun Hamburg Linux builds include a libstdc++.so.6 that comes from
somewhere by magic; it is not checked into CVS. That is already how
it works for a long time, and probably will not
Hi,
On 9.6.2008, at 9:27, Stephan Bergmann wrote:
I still fail to understand your reasons to oppose to the proposed
change when the status quo is apparently OK for you. Sun Hamburg
builds with GCC X and includes in install sets libstdc++.so version
Y. What changes over time (through the
Hi,
It's not magic at all. It comes from the used compiler. Always been
so. And the compiler version is documented here:
http://wiki.services.openoffice.org/wiki/
Compiler_versions_used_by_port_maintainers_and_release_engineers
Heiner, yes. This is the current status quo. And sb wants to
Pavel,
Kurt got the task to switch to gcc-4.2.3 before the final. In principe
this is easy but ... the major issue with that is to upgrade all our
build machines and still be able to do the old build.
With that gcc-4.2.3 will come a new libstdc++ ... problem solved :)
Heiner
PS: We might
Pavel Janík wrote:
Hi,
It's not magic at all. It comes from the used compiler. Always been
so. And the compiler version is documented here:
http://wiki.services.openoffice.org/wiki/Compiler_versions_used_by_port_maintainers_and_release_engineers
Heiner, yes. This is the current status quo.
Maybe using magic was a poor choice to begin with. We could
extend the above wiki page to list exactly which GCC/libstdc++
combination is used in each case.
Is used while compiling and is used for the final instsets, right?
Two columns...
--
Pavel Janík
Stephan Bergmann wrote:
Rene Engelhard wrote:
Hi,
Stephan Bergmann wrote:
http://www.openoffice.org/issues/show_bug.cgi?id=86389 still waits
for a fix, rather urgently: On Linux, (at least Sun-built) OOo
(and derivatives, like BrOffice) brings along a (rather old)
libstdc++.so.6. It can
Hi,
Another line of attack I had in mind is to ship a recent version
of libstdc++.so.6 (from GCC 4.2, say), even if we continue to
build with GCC 3.4.1. The advantages are that it is simple, we do
not need to change any code, and OOo keeps running on machines
that do not already have
On Fri, 2008-06-06 at 09:30 +0200, Oliver Braun wrote:
#if defined _gcc3 !(defined FREEBSD || defined NETBSD \
|| defined MACOSX || defined SYSTEM_STDLIBS || defined(WNT))
Does this mean with switching to gcc4 we no longer ship libstdc++ ?
If you're referring to _gcc3. That
Pavel Janík wrote:
Hi,
Another line of attack I had in mind is to ship a recent version of
libstdc++.so.6 (from GCC 4.2, say), even if we continue to build with
GCC 3.4.1. The advantages are that it is simple, we do not need to
change any code, and OOo keeps running on machines that do
Oliver Braun wrote:
Hi Stephan et al.,
Stephan Bergmann wrote:
Another line of attack I had in mind is to ship a recent version of
libstdc++.so.6 (from GCC 4.2, say), even if we continue to build with
GCC 3.4.1. The advantages are that it is simple, we do not need to
change any code, and
Hi,
You misunderstand me; I guess I was not clear enough.
you was perfectly clear.
1 Sun Hamburg Linux builds include a libstdc++.so.6 that comes
from somewhere by magic; it is not checked into CVS. That is
already how it works for a long time, and probably will not
change.
http://www.openoffice.org/issues/show_bug.cgi?id=86389 still waits for
a fix, rather urgently: On Linux, (at least Sun-built) OOo (and
derivatives, like BrOffice) brings along a (rather old) libstdc++.so.6.
It can happen that there is a later libstdc++.so.6 already installed
on the system,
Hi,
Stephan Bergmann wrote:
http://www.openoffice.org/issues/show_bug.cgi?id=86389 still waits for
a fix, rather urgently: On Linux, (at least Sun-built) OOo (and
derivatives, like BrOffice) brings along a (rather old) libstdc++.so.6.
It can happen that there is a later libstdc++.so.6
Rene Engelhard wrote:
Hi,
Stephan Bergmann wrote:
http://www.openoffice.org/issues/show_bug.cgi?id=86389 still waits for
a fix, rather urgently: On Linux, (at least Sun-built) OOo (and
derivatives, like BrOffice) brings along a (rather old) libstdc++.so.6.
It can happen that there is a
15 matches
Mail list logo
