On Mon, Mar 30, 2015 at 3:10 PM, Barry Schwartz <chemoelect...@chemoelectric.org> wrote: > Mark Knecht <markkne...@gmail.com> skribis: >> On Mon, Mar 30, 2015 at 2:04 PM, Frank Peters <frank.pet...@comcast.net> >> wrote: >> > On Mon, 30 Mar 2015 12:15:55 -0700 >> > Mark Knecht <markkne...@gmail.com> wrote: >> > >> >> Yesterday I was emerge -DuN @world clean. It took hours due to Gentoo >> >> decisions about multilib stuff. >> >> >> > >> > Is it still necessary to be using multilib? >> > >> > I've been using pure AMD64 for so long I tend to forget that >> > 32-bit stuff still exists. >> > >> > Frank Peters >> >> Hi Frank, >> Honestly, I really don't know and figure the answer is probably no, >> but it was when I set the machine up this way 5 or so years ago. Even >> today I still see messages from things like Virtualbox drivers saying >> they are using 32-bit modes, but what do I know? When emerge threw all >> this stuff at me Sunday I figured I had no reason to break a machine >> that has been working well so I let it do everything it wanted to do. >> I don't have any problems with them getting rid of emulation libraries >> and having everything built into the packages. I just wasn't prepare >> for the time it required yesterday. > > I’m still working on it, myself. Various problems. Nothing I won’t be > able to figure out. My list of things to build ~amd64 instead of amd64 > is growing a bit, for instance. Had to fix one of my overlay > ebuilds. Etc. Removed some 32-bit stuff at least temporarily. I do not > use 32-bit stuff very often. > > The main problem at this case is emerge wanting to install libav > despite that I’m set up for ffmpeg. These things happen. > > At least if you use emerge as your package manager, it’s probably safe > to go ahead and uninstall the emul packages, if you haven’t. The > binaries will stay in place until you build the replacements. >
Hi Barry, Yes, uninstalling the emulation libraries is exactly what I did yesterday. It all seemed to work. Everything (nearly 300 packages) built cleanly, and then following that there were another 250 or so that had to be rebuilt I guess to be relinked or something. Anyway, it took a few hours but everything went fine. In my case I've been slowly converting my machine back to nearly 100% stable. I don't need anything more than that in my daily work these days and would greatly prefer fewer updates. In the old days when I ran a lot of Gentoo pro-audio overlay stuff I stay to stay leading edge all the time but these days I don't do that and life should be easier. The libav vs ffmpeg thing was an issue for me also but I eventually got through that a couple of weeks ago. As part of 'going stable' I've removed use flags in make.conf and package.use and then basically let portage do its thing. Everything worked fine once I got it all to build. handbrake/makemkv/vlc and (I think) xine are all working now but they weren't for a few days. I was thinking back about my 32-bit usage when I built the machine. In those days (and it's likely still true) to run Windows VST plugins you had to have 32-bit support. I was doing a lot of software synth stuff a decade ago and suspect that was my main need in that area. I don't intentionally use 32-bit for anything so likely I don't need it at all as per Frank's comment but I also didn't feel like I really wanted to deal with that right now. Cheers, Mark
