015/02/05/gcc5-and-the-c11-abi/
> https://blogs.gentoo.org/blueness/2015/03/10/the-c11-abi-incompatibility-problem-in-gentoo/
>
LGTM.
--
Ryan Hillpsn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
pgp8sN8qTZUiO.pgp
Description: OpenPGP digital signature
uuid_by_uuid':
tcsps.c:(.text+0x3e8): undefined reference to `read_data'
bwm-ng.o: In function `main':
bwm-ng.c:(.text.startup+0x1d3): undefined reference to `get_iface_stats'
Rebuilding won't help with these of course.
--
Ryan Hillpsn: dirtye
exactly how these flags interact with each other.
Something like (emerge -pv):
ssl [ (openssl) libressl gnutls ]
- if USE ssl then pick one of, default openssl if none chosen
ssl [[ (openssl) libressl gnutls ]]
- if USE ssl then one or more of... etc.
But I suppose that's another topic.
--
Ryan Hillpsn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
pgp616RCHiArF.pgp
Description: OpenPGP digital signature
ters. Newest first is the usual order (e.g. it agrees with the
> default of git log), and ChangeLog having different order from
> ChangeLog-20* seems rather confusing to me.
I imagine it breaks emerge --changelog output as well?
--
Ryan Hillpsn: dirtyep
r do a compile test or query
the compiler in some way to ensure the needed support is there. Look at the
fortran virtual and fortran-2 eclass for an example.
--
Ryan Hillpsn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
pgphr6MQ7TfOv.pgp
Description: OpenPGP digital signature
e this for security sensitive data? You want me to use a
potentially unstable live ebuild instead? Well, no, that's not gonna happen.
--
Ryan Hillpsn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
pgppyiHLotbfb.pgp
Description: OpenPGP digital signature
901 - 906 of 906 matches
Mail list logo