First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 38001
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Jeremy Huddleston <eradicator@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Douglas Pollock <douglas.pollock@magma.ca>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
faad2-xmms.patch Patch to faad2's ebuild patch Douglas Pollock 2004-01-12 13:14 0000 1.65 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 38001 depends on: Show dependency tree
Show dependency graph
Bug 38001 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-01-12 13:13 0000 
Not elegant, but it works.  Feel free to modify it into whatever style you
like.

Tested and works loading my iTunes m4a files from a Windows XP partition into
XMMS.

------- Comment #1 From Douglas Pollock 2004-01-12 13:14:08 0000 ------- 
Created an attachment (id=23696) [edit]
Patch to faad2's ebuild

------- Comment #2 From Jeremy Huddleston 2004-01-31 20:44:56 0000 ------- 
I'll take a look at this.

------- Comment #3 From Jeremy Huddleston 2004-01-31 21:16:44 0000 ------- 
works great.  thanks.  in portage with version bump

------- Comment #4 From Douglas Pollock 2004-02-01 07:23:20 0000 ------- 
Many apologies.  I found this out at the beginning of the week, and should have
mentioned it here immediately.  There's a problem with the dynamic linker
during the install phase if you do not already fadd2 installed.  It incorrectly
resolves a linked library to the non-image version of the faad2 library.  This
means that those with faad2 already installed can upgrade, but clean installs
fail.

I don't have time to look at this for a week or so; I'm at EclipseCon with
work.

If you want, it should just be one more tweak to the makefile.  Otherwise, I'll
find it when I get back.

In the meantime, I'd recommend rolling back this change.  Reduced functionality
is probably better than broken ebuilds.

Sorry once again....

------- Comment #5 From Jeremy Huddleston 2004-02-01 12:09:34 0000 ------- 
ImageMagick was having this same problem a few months back... I'll check out
how they fixed it and try to implement the same fix.  It's probably just
throwing in the correct order of -L to the LDFLAGS.

------- Comment #6 From Jeremy Huddleston 2004-02-02 00:22:02 0000 ------- 
Alright... I ended up not using this patch... instead, changing emake to make
causes compilation to succeed, but we still have the -lfaad errors on
installation if it's not an upgrade... so I just 'doexe' them before running
the make install... it's not pretty, but it works...  A patch to the
Makefile.am would be best, but I'm not an automake/autoconf guru.
First Last Prev Next    No search results available      Search page      Enter new bug