Summary: | multimedia/gstreamer1-libav: firefox crashes in gstreamer-1.0/libgstlibav.so on i386 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Dmitry Afanasiev <KOT> | ||||
Component: | Individual Port(s) | Assignee: | freebsd-multimedia (Nobody) <multimedia> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | tijl | ||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Dmitry Afanasiev
2014-05-07 16:10:00 UTC
Responsible Changed From-To: freebsd-ports-bugs->freebsd-multimedia Over to maintainer (via the GNATS Auto Assign Tool) Hi, What cpu model do you have? Hello!
> What cpu model do you have?
I got this problem on AMD C-60 CPU and Xeon E5345.
World and kernel build from stable/10 r264761, ports revision 352970.
But I'm confused. I rebuilded multimedia/gstreamer1-libav on i386
chrooted environment on amd64 system (Xeon E5450), created package,
installed this package back to full i386 system with E5345. After this
firefox works correctly.
System's and ports revision are identical on amd64 and i386 systems.
It's too strange for me.
I will try to rebuild again multimedia/gstreamer1-libav on my C-60 CPU.
On 08.05.2014 15:52, Dmitry Afanasiev wrote:
>> What cpu model do you have?
> I got this problem on AMD C-60 CPU and Xeon E5345.
> World and kernel build from stable/10 r264761, ports revision 352970.
>
> But I'm confused. I rebuilded multimedia/gstreamer1-libav on i386
> chrooted environment on amd64 system (Xeon E5450), created package,
> installed this package back to full i386 system with E5345. After this
> firefox works correctly.
> System's and ports revision are identical on amd64 and i386 systems.
> It's too strange for me.
>
> I will try to rebuild again multimedia/gstreamer1-libav on my C-60 CPU.
I remembered difference between hosts - working gstreamer1-libav was
build on host with GCC as system compiler.
I tried gstreamer1-libav compiled by gcc on AMD C-60 and it working
properly.
I think problems may be related to clang.
Fixed in r361776. |