I've not updated my system for about three months. Next emerge -DuN world failed. Reproducible: Always Steps to Reproduce: 1. emerge -DuN world or 2. emerge lame Actual Results: compiler complains about errors in assembly code: nasm.h:153: error: `%$STACK': context stack is empty Expected Results: flawless installation I've tried to dig into emerge logs. Here some results. ./configure && make (without flags) builds lame fine. I've copied all flags for configure and started to remove them one by one. It seems that --enable-nasm flag causes the compilation errors. I've tried to re-emerge nasm and gcc with no luck.
Created attachment 248982 [details] emerge --info emerge --info
Created attachment 248984 [details] emerge -pqv =media-sound/lame-3.98.4 emerge -pqv =media-sound/lame-3.98.
Created attachment 248986 [details] Build environment Build environment
Created attachment 248987 [details] Build log Build log
vasiliy: for me works good.. see my build log and emerge --info http://paste.pocoo.org/show/269144/ are you sure you have a clean system despite having ~ ?
(In reply to comment #5) > vasiliy: > > for me works good.. see my build log and emerge --info > http://paste.pocoo.org/show/269144/ > > are you sure you have a clean system despite having ~ ? > Agostino, I'm not quite sure what do you mean by 'clean system'
(In reply to comment #5) > vasiliy: > > for me works good.. see my build log and emerge --info > http://paste.pocoo.org/show/269144/ > > are you sure you have a clean system despite having ~ ? > What is the reason your configure is ran with --disable-nasm ?
For me it breaks using nasm-2.09.02, ok with nasm-2.08.02
(In reply to comment #8) > For me it breaks using nasm-2.09.02, ok with nasm-2.08.02 > Same for me. I've unmerged nasm, emerged lame, and re-emerged nasm afterwards. Should I resolve this bug as "works for me" ?
(In reply to comment #8) > For me it breaks using nasm-2.09.02, ok with nasm-2.08.02 > ditto. Some problem with nasm? I can't build any versions of lame with nasm-2.09.02.
(In reply to comment #10) > ditto. Some problem with nasm? I can't build any versions of lame with > nasm-2.09.02. > idem for me
I can confirm this exact same issue on my ~86 laptop. Downgrading to nasm-2.08.02 from nasm-2.09.02 resolves this issue and allows lame to build. This was not an issue with ver.-2.09.01 which is no longer in the tree. So this is a regression of some sort. For now, I've added nasm-2.09.02 to my package.mask file.
Guys :) see ebuild: DEPEND="${RDEPEND} dev-util/pkgconfig mmx? ( dev-lang/nasm )" So, try temporarily build with -mmx: echo "media-sound/lame -mmx" >> /etc/portage/package.use
Occurred on 5 different systems. If nasm> 2.08.02 installed, emerge fails. Simply reverting to 2.08.02 for this build fixes the problem.
Created attachment 249391 [details] patch @ ssuominen Is a good job and good syntax?
No, nasm isn't slotted so that patch to the ebuild isn't correct.
sed -i -e '/define sp/s/+/ + /g' libmp3lame/i386/nasm.h || die works around it I believe.
For me, I have this problem only on ~x86. However on ~amd64 both lame-3.98.4 and nasm-2.09.02 build just fine together.
(In reply to comment #18) > For me, I have this problem only on ~x86. However on ~amd64 both lame-3.98.4 > and nasm-2.09.02 build just fine together. > The mmx code in lame is only for x86 (32bit) so you won't see it in other arch's. That said, the solution in Comment #17 looks fine to me but I can't test it. So anyone who can, please go ahead and apply it.
(In reply to comment #19) > (In reply to comment #18) > > For me, I have this problem only on ~x86. However on ~amd64 both lame-3.98.4 > > and nasm-2.09.02 build just fine together. > > > > The mmx code in lame is only for x86 (32bit) so you won't see it in other > arch's. > > That said, the solution in Comment #17 looks fine to me but I can't test it. So > anyone who can, please go ahead and apply it. > I'd love to help, but I'm a truck driver not a programmer. How and where would I execute that command to try it out and see if it works? TIA
It worked fine for me and lame is high enough profile that I just went ahead and committed the fix.
(In reply to comment #21) > It worked fine for me and lame is high enough profile that I just went ahead > and committed the fix. > TY. I just re-synced and can confirm build works now. Thanks
