Re: gobolinux-users Digest, Vol 139, Issue 13
sali <[email protected]> Mon, 27 Feb 2017 16:12:17 +0100
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <[email protected]> |
[email protected] schreef op 2017-02-23 00:00: > Send gobolinux-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of gobolinux-users digest..." > > > Today's Topics: > > 1. gcc Internal Compiler Errors (Hisham Muhammad) > 2. Follow up on gcc internal compiler errors while compiling (3) > (sali) > 3. Re: gcc Internal Compiler Errors (Stéphane Aulery) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 22 Feb 2017 15:59:48 -0300 > From: Hisham Muhammad <[email protected]> > To: [email protected] > Subject: [gobolinux-users] gcc Internal Compiler Errors > Message-ID: > <CAJpkDYe8e8hTgYdkMqi0hWB4Tdn6BuVB-YTwS19O3VMZ0=3yEA@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Martin and Stéphane, > > We tracked down the problem. > > The version of GMP which the build of GCC built in the ISO for 016 was > accidentally compiled for a higher processor family, so they are > incompatible with Core2 machines. > > We are rebuilding the packages for GMP and GCC to make them > processor-independent, so they run on all x86-64 systems. When we get > them ready to install, I'll post about it here. > > -- Hisham > > > ------------------------------ > > Message: 2 > Date: Wed, 22 Feb 2017 21:52:02 +0100 > From: sali <[email protected]> > To: [email protected] > Subject: [gobolinux-users] Follow up on gcc internal compiler errors > while compiling (3) > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi there ! > > The only thing > I can come up with > at this moment > is this - > >> exerpt from: >> http://linuxfromscratch.org/blfs/view/svn/general/gcc.html > > [Caution] Caution > > If you are upgrading GCC from any other version prior to 6.3.0, then > you > must be careful compiling 3rd party kernel modules. You should ensure > that the kernel and all its native modules are also compiled using the > same version of GCC that you use to build the 3rd party module. This > issue does not affect native kernel (and kernel modules) updates, as > the > instructions below are a complete reinstallation of GCC. If you have > existing 3rd party modules installed, ensure they are recompiled using > the updated version of GCC. As always, never update the kernel headers > from the ones used when Glibc was compiled during LFS. > > The 5.1.0 version of GCC introduces an incompatible ABI change in the > C++ library libstdc++.so. This does not prevent using programs compiled > with the previous version of GCC , since both old and new symbols are > available in the library. But compiling, with the new version, programs > which use libraries compiled with the old version is likely to give > errors. So, if you are upgrading from any previous version prior to > 5.1.0, you have two solutions: recompile all the libraries with the new > version, or use the --with-default-libstdcxx-abi switch to configure. > > < ends > > I use two descendants from linuxfromscratch: Gobo Linux and Nutyx > Linux; > both have 'internal compiler errors'. > Up till now I've - tried to - compile(d) S-Lang Midnight Commander on > Gobo Linux > on several 'core' ( duo quad two ) processors via Installed and Live > versions. > > Also I - tried to - compile php on Nutyx Linux which gave comparable > errors. > But ... > - the last week or so I have been busy working on my 'own descendant' > based on > the development branch of xLFS. > And neither of the above sources gave problems. They just compiled. > So might this be 'the problem' or ... ? > > Good Night, > > Martin. > > > > ------------------------------ > > Message: 3 > Date: Wed, 22 Feb 2017 23:30:37 +0100 > From: Stéphane Aulery <[email protected]> > To: [email protected] > Subject: Re: [gobolinux-users] gcc Internal Compiler Errors > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello Hisham, > > Le 22/02/2017 à 19:59, Hisham Muhammad a écrit : >> Martin and Stéphane, >> >> We tracked down the problem. >> >> The version of GMP which the build of GCC built in the ISO for 016 was >> accidentally compiled for a higher processor family, so they are >> incompatible with Core2 machines. >> >> We are rebuilding the packages for GMP and GCC to make them >> processor-independent, so they run on all x86-64 systems. When we get >> them ready to install, I'll post about it here. > > Good news and thanks for you help. > > I'm happy to continue testing the distribution for my use. > > If I can do something for helping you, say it. > > Regards, > > -- > Stéphane Aulery > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.gobolinux.org/pipermail/gobolinux-users/attachments/20170222/e9791270/attachment-0001.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > gobolinux-users mailing list > [email protected] > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > > > ------------------------------ > > End of gobolinux-users Digest, Vol 139, Issue 13 > ************************************************ That's nice to know. Thanks. Martin. _______________________________________________ gobolinux-users mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-users