Lennon Cook wrote:
Stef Bon wrote:

Can I compile OO 2 right away or do I need I patch for my native compiler
(gcc-3.4.1)?

It should work fine on gcc3. The reason for the various gcc4 patches
in different packages is because of imcompatibilities between gcc3 and
4. Some apps haven't been tested (or targeted) for gcc4, and so won't
necesarily compile out-of-the-box with it (GCC4 is still a fairly
minority thing). gcc3 has been around for a good long while and is
included in most current Linux distros  (not necesarily by default,
but as a distro-managed package), and so it doesn't have this problem.

In general, you should be able to build packages from SVN BLFS on gcc3
if you simply don't apply any patches that are specifically for GCC4
compatibility.

--
Lennon Victor Cook

Not quite.  Still the STLPort issues among others.  Have a look at
David Ciecierski's page at http://www.doc.ic.ac.uk/~dfc04/OOo_2.0.0/ for the needed patches to use gcc3...however, I'll warn in advance for 3.4.1, it may or may not work. I can't remember if it was OOo or jdk that gave me fits. In 3.4.1 BLFS, I had dropped it back to 3.3.x for both IIRC do to a (serious IMO) bug with 3.4.1 that was resolved in 3.4.2. If not, then drop back to 3.3 and _I_ _believe_ that all should be well without the gcc4 patch....the exception is the c++ headers. In the /opt/gcc-3.3.6 case....

'ln -sf /opt/gcc-3.3.6/include/c++/3.3.6 /usr/g++-v3'

You might also take a look at the 6.0 book's patches and instructions if you should run into build problems, and of course you can still ask here, although I don't have a PC capable of hosting an OOo build that still has gcc3 on it, the correct questions might spark a memory or two. :-) Even with all of that, in theory, the gcc4 patch _shouldn't_ hurt the build...but I've never tried it. Lastly, the BLFS-Dev archives around the new year should hold all of my ramblings on what I had found at the time.

-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to