On 22 August 2017 14:09:39 EEST, Dale <rdalek1...@gmail.com> wrote: >It may have been you but I was thinking either Walter or Duncan but not >sure. It could be, I read it on -dev too. I'm just not sure who it >was >just know it is gentoo related, since Gentoo is all I'm subscribed to. > >One would think there would be some method to downgrade that is known >to >work and documented. It can be done for lots of other very important >packages but this one, not so much. To me, it's just odd. > >At least the OP found a fix tho. < whew > > >Dale > >:-) :-) > >P. S. Top posting since Neil seems to be on some device that started >it. :-D > > >Neil Bothwick wrote: >> I did it once, some years ago. AFAIR I commented out the version che >k >> in, i think, the glibc-toolchain eclass then emerged the older >> version. Just make sire you have a binary package of the current >> version that you can unpack in / if things go wrong. >> >> On 22 August 2017 13:53:35 EEST, Dale <rdalek1...@gmail.com> wrote: >> >> Raffaele Belardi wrote: >> >> On Fri, 2017-08-18 at 09:00 +0200, Raffaele Belardi wrote: >> >> I hava a build problem upgrading Mythtv to 0.28.1-r1 [1] >> on an ~amd64 system. The problem is related to a glibc >API >> change [2] introduced in glibc-2.24 and still present in >> glibc-2.25. So I'm thinking to try the build with an >older >> glibc version. Downgrading the system to glibc to 2.23-r3 >> means trouble? If not, an emerge @preserved-rebuild after >> the downgrade will be sufficient to not break the rest of >> the system? I suppose a quickpkg of the whole world >before >> the downgrade would be a good idea, just in case... >> thanks, raffaele [1] >> https://bugs.gentoo.org/show_bug.cgi?id=604430 [2] >> https://bugs.gentoo.org/show_bug.cgi?id=575232 >> >> Just as follow up, inspired by [2] I fixed the mythtv build >> issue by adding #include <sys/sysmacros.h> to videosource.cpp >> and continuing the build with ebuild instead of emerge. >raffaele >> >> >> >> >> Just a FYI, some have been able to downgrade and it work. >However, you >> have to be prepared for that beforehand I think. I've seen it >posted >> before but can't recall WHO it was. I was hoping they would >reply but >> either they didn't see your post or they are no longer >subscribed. >> >> While it may be possible, it is risky and not recommended. It's >one >> thing that I wish they had a known path to downgrade for. It's >one of >> those, you don't know it's going to break something until it does >and >> you have little or no options. >> >> Glad you got a workaround tho. Maybe some more info will pop up >later. >> >> Dale >> >> :-) :-) >> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity.
:P -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
