=media-libs/jpeg-6b-r8 crash during the compilation, i'm emerge this during the update. It's the package of portage ~x86-fbsd, for information is a centrino labtop ( dell latitude D600 ). =media-libs/jpeg-6b-r7 run without any problem. Reproducible: Always Steps to Reproduce: 1.When update your system with emerge -avuDN world 2.When update this package media-libs/jpeg 3. Actual Results: The compilation of media-libs/jpeg abort with message http://www.sagwin.org/NoPasting/pasting/1754509325764141953.html Expected Results: This preceding version of media-libs/jpeg ( (~)6b-r7 ) run without any problem. I'm past my emerge --info here http://pastebin.ca/346401 and i past my /etc/make.conf here http://pastebin.ca/346456.
Don't refer to pastebins when reporting bugs. Post/attach the info here, post emerge --info and reopen then.
Created attachment 109629 [details] This is the crash of compilation to media-libs/jpeg
Created attachment 109631 [details] This is my emerge --info, for information.
I am create two attachments for this bug.
(In reply to comment #4) > I am create two attachments for this bug. For now i masked r8
I see the same issue on OSX/ppc.
@vapier: in your -r8 bump, the patchver went from 1.4 to 1.5. In the latter, 60_all_jpeg-maxmem-sysconf.patch seems to lack FreeBSD/Darwin support, hence it only compiles on Linux/Solaris. Please put the right 60_all_jpeg-maxmem-sysconf.patch patch back in like in patchver 1.4 to fix this bug.
lemme spell this plainly ... if you're screwing with patch tarballs and not talking to the maintainers, this is your fault aka, by you screwing with the patch tarball directly, you screwed the pooch patch tarballs are generated files, they should never be modified by hand if there's a patch you want updated *in cvs* then post the patch and i'll do so; the patch that is in the 1.5 tarball is the correct patch as that is the one found in cvs
I get you point. Bah, I never listen to ya anymore Diego!
Hey now, what do I have to do with this? We got a bug running for that one, if I was to add the patch myself, I knew how to handle it, I just wasn't the one doing the change! (I was waiting for Mike to do it).
waiting for me where ? i dont see any open jpeg reports ...
It was an old one, but nevermind. Can you handle it now Mike?
post any patches you want me to update to this bug ... that way there is no confusion as to what i should be doing
Created attachment 110087 [details, diff] patch for FreeBSD and Darwin vapier, please consider applying the attached patch to allow for compilation on FreeBSD and Darwin. Thanks.
added to cvs
