I get over 2000 compilation errors. Something fundamental must be wrong...
Created attachment 138071 [details] build.log.aa split -b 1000000 build.log build.log.
Created attachment 138072 [details] build.log.ab split -b 1000000 build.log build.log.
Created attachment 138073 [details] build.log.ac split -b 1000000 build.log build.log.
Created attachment 138075 [details] build.log.ad split -b 1000000 build.log build.log.
Created attachment 138077 [details] build.log.ae split -b 1000000 build.log build.log.
Created attachment 138078 [details] emerge --info
(In reply to comment #0) > I get over 2000 compilation errors. Something fundamental must be wrong... > FYI: Octave-2.9.18 from the science overlay built without errors.
Hi Vladimir, Thanks for your report. Unfortunately, octave-forge is tied closely to octave itself and you will have to use octave-2.1.72 or octave-2.1.73 for octave-forge-2006.03.17 to compile since octave-2.9.x, which are the new pre-release versions for octave-3.0 are fundamentally different. Hence, the boatload of errors you get are no surprise. However, the science overlay contains new style split octave-forge ebuilds that will replace the monolithic octave-forge once octave 2.9.x or 3.0 is in portage. To give it a try just emerge any of octave-forge-* or just pull in octave-forge-meta to get them all. Best, Markus
octave-forge-meta worked like a charm.
I am glad to hear :) Hopefully, we can merge the new octave and octave-forge-meta ebuilds into the main tree in the not so far future. best, Markus