Re: [CentOS] devtoolset-4 ageing?

[Lamar Owen]

On 12/19/2016 01:09 PM, Lamar Owen wrote:

On 12/19/2016 11:47 AM, lejeczek wrote:


devtoolset-6-runtime is missing from repo(s) ?
Looks like it is being made available, but not all there yet. Wait a 
few days and check again, I guess.  I just happened to notice that 
some devtoolset-6 packages were out there; must not yet be the full set.
I just successfully installed devtoolset-6 from the repos.  Also, there 
has been a devtoolset-4 update; a yum update should pull in the updated 
devtoolset-4 packages, and a yum install devtoolset-6 should work for 
you now (it just did for me).


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4 ageing?

[Lamar Owen]

On 12/19/2016 11:47 AM, lejeczek wrote:


On 19/12/16 16:05, Lamar Owen wrote:

On 12/19/2016 08:33 AM, lejeczek wrote:
devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS 
elfutils-0.166-2.el7.x86_64


isn't devtool ageing? Could this be the case with more packages?
regards, 

devtoolset-6 is available.

devtoolset-6-runtime is missing from repo(s) ?
Looks like it is being made available, but not all there yet.  Wait a 
few days and check again, I guess.  I just happened to notice that some 
devtoolset-6 packages were out there; must not yet be the full set.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4 ageing?

[lejeczek]

On 19/12/16 16:05, Lamar Owen wrote:

On 12/19/2016 08:33 AM, lejeczek wrote:
devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS 
elfutils-0.166-2.el7.x86_64


isn't devtool ageing? Could this be the case with more 
packages?
regards, 

devtoolset-6 is available.

devtoolset-6-runtime is missing from repo(s) ?


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4 ageing?

[lejeczek]

On 19/12/16 16:38, lejeczek wrote:



On 19/12/16 16:05, Lamar Owen wrote:

On 12/19/2016 08:33 AM, lejeczek wrote:
devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS 
elfutils-0.166-2.el7.x86_64


isn't devtool ageing? Could this be the case with more 
packages?
regards, 

devtoolset-6 is available.


somewhere (semi)officially? where?

yes, of course.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4 ageing?

[lejeczek]

On 19/12/16 16:05, Lamar Owen wrote:

On 12/19/2016 08:33 AM, lejeczek wrote:
devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS 
elfutils-0.166-2.el7.x86_64


isn't devtool ageing? Could this be the case with more 
packages?
regards, 

devtoolset-6 is available.


somewhere (semi)officially? where?


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4 ageing?

[Lamar Owen]

On 12/19/2016 08:33 AM, lejeczek wrote:
devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS 
elfutils-0.166-2.el7.x86_64


isn't devtool ageing? Could this be the case with more packages?
regards, 

devtoolset-6 is available.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] devtoolset-4 ageing?

[lejeczek]

hi everyone

just a quickie to devel maybe. I'm looking at some bits:

devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS 
elfutils-0.166-2.el7.x86_64


isn't devtool ageing? Could this be the case with more packages?
regards,
L.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4

[Jarosław Bober]

Hello, I just found the discussion on the devtoolset on SO:
https://stackoverflow.com/questions/15599714/risks-of-different-gcc-versions-at-link-run-time

confirming my guesses.
You can use any new C++11/C++14 feature and your program will link
dynamically to stock libstdc++. Any feature that is not present there will
be linked statically with nonshared_libstdc++.a. The only cost would be
additional binary size. I checked using few features and binary growth was
ignorable. But definitelly one have to take it into account. The only
problem I have for now is to bring all of machines I maintain to a stable
6.6 version. Which is >1000 machines :) The cos is well worth it :)

Regards,
-Jarek



2016-05-20 21:16 GMT+02:00 Warren Young :

> On May 20, 2016, at 8:17 AM, Jarosław Bober 
> wrote:
> >
> > ldd gives me:
> > ldd a.out
> > linux-vdso.so.1 =>  (0x7fff6e5ff000)
> > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0039d840)
>
> In that case, I don’t see how you can be making use of any C++11/14
> features that aren’t implemented by the compiler itself (e.g. type
> inference via “auto”) or purely in template form.  Any feature that uses
> the compiled Standard C++ Library can’t be using the new library.
>
> That may be useful for your purposes.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4

[Warren Young]

On May 20, 2016, at 8:17 AM, Jarosław Bober  wrote:
> 
> ldd gives me:
> ldd a.out
> linux-vdso.so.1 =>  (0x7fff6e5ff000)
> libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0039d840)

In that case, I don’t see how you can be making use of any C++11/14 features 
that aren’t implemented by the compiler itself (e.g. type inference via “auto”) 
or purely in template form.  Any feature that uses the compiled Standard C++ 
Library can’t be using the new library.

That may be useful for your purposes.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4

[Jarosław Bober]

Are you asking if the new libstdc++ is statically linked into your app only
for the new functions but your app remains dynamically linked to the old
one for the parts of C++ that have remained unchanged, the answer is “no”.
Your app is linked to the new library, period.  You can use ldd(1) to prove
this to yourself.
I am not so sure.
That is what I thought, but then I compiled something with a compiler from
devtoolset (5.2.1) with --std=c++11 flag.

ldd gives me:
ldd a.out
linux-vdso.so.1 =>  (0x7fff6e5ff000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0039d840)
libm.so.6 => /lib64/libm.so.6 (0x0039ce80)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0039d800)
libc.so.6 => /lib64/libc.so.6 (0x0039ce00)
/lib64/ld-linux-x86-64.so.2 (0x0039cdc0)

Which is stock libstdc++
Devtoolset version is located at:
/opt/rh/devtoolset-4/root/usr/lib/gcc/x86_64-redhat-linux/5.2.1/libstdc++.so
Additionally there is libstdc++_nonshared.a:
/opt/rh/devtoolset-4/root/usr/lib/gcc/x86_64-redhat-linux/5.2.1/libstdc++_nonshared.a

In the guide there is a matrix of compatibility:
https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/4/html/User_Guide/sect-Red_Hat_Developer_Toolset-Compatibility.html
it says that If I compile with DTS on 6.6 thet it will run on 6.6 and
above, but it doesn't say if DTS has to be installed on that machine.
So this got me to thinking.
I definitelly will check that :) and I really believe that it can be this
way. Althought it sounds like black magic.

Regards,
-Jarek

2016-05-19 23:02 GMT+02:00 Warren Young :

> On May 19, 2016, at 3:30 AM, Jarosław Bober 
> wrote:
> >
> > Do I have to  install devtoolset on all my machines that I want to run
> this
> > app?
>
> Probably, yes.  That, or redistribute parts of it with your app, either by
> cherrypicking files from the devtoolset RPM or statically linking to it.
>
> > Or would it use built-in libstdc++ library, linking statically only
> > the missing parts?
>
> Are you asking if the new libstdc++ is statically linked into your app
> only for the new functions but your app remains dynamically linked to the
> old one for the parts of C++ that have remained unchanged, the answer is
> “no”.  Your app is linked to the new library, period.  You can use ldd(1)
> to prove this to yourself.
>
> Yes, this is a pain, which is why most people writing software for older
> CentOS releases don’t upgrade their development tools.  There’s a lot to be
> said for holding off on using new language features until they’re available
> in the stock version of the tools for all OSes you need to deploy on.
>
> I’d like to be using C++11 myself, but a feature-complete version of C++11
> didn’t appear in g++ until 4.8, which first shipped in CentOS 7.  I just
> got done backporting a feature to a 32-bit CentOS 5 box, so I’m probably
> not going to be able to use C++11 for another 3-5 years.  Sad, but I still
> get the work done with C++98.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4

[Warren Young]

On May 19, 2016, at 3:30 AM, Jarosław Bober  wrote:
> 
> Do I have to  install devtoolset on all my machines that I want to run this
> app?

Probably, yes.  That, or redistribute parts of it with your app, either by 
cherrypicking files from the devtoolset RPM or statically linking to it.

> Or would it use built-in libstdc++ library, linking statically only
> the missing parts?

Are you asking if the new libstdc++ is statically linked into your app only for 
the new functions but your app remains dynamically linked to the old one for 
the parts of C++ that have remained unchanged, the answer is “no”.  Your app is 
linked to the new library, period.  You can use ldd(1) to prove this to 
yourself.

Yes, this is a pain, which is why most people writing software for older CentOS 
releases don’t upgrade their development tools.  There’s a lot to be said for 
holding off on using new language features until they’re available in the stock 
version of the tools for all OSes you need to deploy on.

I’d like to be using C++11 myself, but a feature-complete version of C++11 
didn’t appear in g++ until 4.8, which first shipped in CentOS 7.  I just got 
done backporting a feature to a 32-bit CentOS 5 box, so I’m probably not going 
to be able to use C++11 for another 3-5 years.  Sad, but I still get the work 
done with C++98.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] devtoolset-4

[Jarosław Bober]

Hello,
my name is Jarek I am new here. I need some clarifications on how to
distribute an app developed with devtoolset-4 enabled.

 I am developing a distributed app in c++ I wanted to upgrade toolchain to
use new standard.
Is it true that when I compile on centos 6.x with devtoolset enabled then I
will be able to run this app on centos 7.x as well?

Do I have to  install devtoolset on all my machines that I want to run this
app? Or would it use built-in libstdc++ library, linking statically only
the missing parts?

This confuses me a bit.

Regards,
-Jarek
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] devtoolset-4

[Jarosław Bober]

Hello,
my name is Jarek I am new here. I need some clarifications on how to
distribute an app developed with devtoolset-4 enabled.

 I am developing a distributed app in c++ I wanted to upgrade toolchain to
use new standard.
Is it true that when I compile on centos 6.x with devtoolset enabled then I
will be able to run this app on centos 7.x as well?

Do I have to  install devtoolset on all my machines that I want to run this
app? Or would it use built-in libstdc++ library, linking statically only
the missing parts?

This confuses me a bit.

Regards,
-Jarek
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] devtoolset-4

[Karanbir Singh]

On 28/01/16 10:54, Kay Diederichs wrote:
> Hi,
> 
> is there any way to get access to devtoolset-4 ?
> 
> I see alot of stuff at
> http://cbs.centos.org/koji/packageinfo?packageID=2076 . Is this not yet
> released?
> 

not as yet, the SCL Sig guys are working through the initial bootstrap,
and should have it done soon - I would recommend dropping into the next
SCL SIG meeting ( they are held on IRC in #centos-devel on
irc.freenode.net at 16:00 UTC on alternate Wednesdays ).
https://www.centos.org/community/calendar/#Software_Collections_SIG_Sync-up

regards


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] devtoolset-4

[Kay Diederichs]

Hi,

is there any way to get access to devtoolset-4 ?

I see alot of stuff at
http://cbs.centos.org/koji/packageinfo?packageID=2076 . Is this not yet
released?

thanks,

Kay

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos