[opensource-dev] Not actually OT: How do I get/update gcc to 4.6 on debian squeeze?

2014-08-28 Thread Lance Corrimal
Hi gang,

How do I upgrade gcc to 4.6 on debian squeeze?

And what else does need to be upgraded on debian squeeze to have the versions 
that LL uses?

The wiki page about setting up a build environment on linux still talks about 
gcc 4.3...

Cheers
LC
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges


Re: [opensource-dev] Building the viewer after the latest commits

2014-08-28 Thread Lance Corrimal
Hi,

So how do I get gcc 4.6 on debian squeeze? Building the whole gcc toolchain 
from source?

Cheers
LC

Am Dienstag, 19. August 2014, 11:47:54 schrieb Oz Linden:
> On 2014-08-19, 07:27 , Henri Beauchamp wrote:
> > On Tue, 19 Aug 2014 09:37:36 +0200, Lance Corrimal wrote:
> >>> Am Montag, 18. August 2014, 14:01:45 schrieb Nicky Perian:
>  I ran into an issue with boost built with gcc 4-6 and viewer compiling
>  goo
>  4-7. rebuilt boost on 4.7 and no more problems.
> >> 
> >> Hi,
> >> 
> >> that worked. Now that needs to go into the official sources...
> > 
> > Hopefully not !...
> > 
> > The current Linux builds of the viewer and pre-built libraries are
> > compiled with gcc 4.6, which also imposes a minimal requirement on
> > the target systems' libstdc++ version (6.0.16).
> > 
> > If LL were to provide pre-built libraries compiled with gcc v4.7,
> > then the "old" (like 2 years old *only*) Linux distributions would
> > become incapable of running the resulting viewer.
> > 
> > You should instead keep a partition (or a VirtualBox virtual machine)
> > with a build-system matching LL's one (i.e. using gcc 4.6.4 and its
> > associated libstdc++).
> > 
> > Henri.
> 
> I don't want to miss an opportunity to agree with Henri...
> 
> At present, our standard Linux build environment for Linux is Debian
> Squeeze, gcc 4.6.  That's what we'll build the packages for. We expect
> to start a toolchain update for Windows (to VS 2013) and Mac OSX (to
> Xcode 5, clang) shortly, but don't plan to change Linux (it was updated
> much more recently than the other platforms as part of the Sunshine
> project).
> 
> You are of course welcome to use what you want for your builds, but we
> won't be making changes to the packages we provide in order to support that.

___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges


Re: [opensource-dev] Building the viewer after the latest commits

2014-08-28 Thread Henri Beauchamp
On Thu, 28 Aug 2014 15:53:43 +0200, Lance Corrimal wrote:

> Hi,
> 
> So how do I get gcc 4.6 on debian squeeze? Building the whole gcc
> toolchain from source?

I don't know Debian distros well enough, but I suppose that their
packaging system got the equivalent of rpm-based ones and allow
you to grab a source package from a newer or older Debian version
and recompile it under your installed version...

So yes, you'd have to rebuild gcc and ancillary programs (cpp, g++,
etc) and libraries (especially libstdc++), that should normally be
packaged together.

Note that if you are running a *newer* version of Debian (which should
be the case if you have got gcc 4.7+ installed on your system), then
you may even grab the binaries from the older Debian versions and
install them on your system: since your glibc library will be newer
than the one the older gcc was built against, the old binaries will
run just fine on your system.
However, note that distros usually make a distinction between the
"system compiler" (the one used to build all the packages, and
especially the kernel and modules for your distro version) and other
(often older) compilers (sometimes required to be able to build
antiquated software): you shall not overwrite your system compiler
with another one when installing the latter... Rpm-based distros
use different binary names for all compilers (for example:
/usr/bin/gcc4.6 instead of just /usr/bin/gcc) and use "alternative"
links (have a look at /etc/alternatives) to link the various compiler
versions to a soft link (/usr/bin/gcc); an "update-alternatives"
command is available to automatically update all the links (links to
gcc, g++, cpp, libstdc++, etc must also be updated together)
automatically, allowing you to easily switch from one version to
another.

Henri.
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges