Hello, the libraw1394-2.0.0 has been released some weeks ago. A proposed ebuild is on the way.
Created attachment 165455 [details] libraw1392-2.0.0.ebuild The proposed ebuild adds valgrind support.
BTW, the bugfix release libraw1394-2.0.1 is available now.
Add please ebuild for libraw1394-2.0.1, it is sufficient to rename existing libraw1394-2.0.0 ebuild.
Hi, libraw-2.0.2 is out. Nothing yet in Portage?
libraw1394-2.0.1 (released on 15 January 2009) is a straightforward drop-in replacement for 2.0.0. It brings a number of valuable bug fixes in its backend for the newer firewire kernel driver stack. libraw1394-2.0.2 (released on 3 February 2009) is identical with 2.0.1 except for corrections in the licensing comments of some files. Would be good to have. Thanks. :-)
http://forums.gentoo.org/viewtopic-p-5535197.html#5535197 I'm having the problem mentioned in that thread. Basically I took the ebuild for 2.0.0 which was [M] in Portage and just renamed it. Is there anybody out there that can give this package some love? (Or at least some advice to me related to my bug? Pleeease...)
Re comment #6: I for one can't reproduce this here with gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1). It also does not look like a libraw1394 bug. If I count the arguments to open in main.c very thoroughly, I get 2, which is not more than 2 or 3. ;-)
Re comment #6: Try with fortify disabled. The __open_too_many_args check only happens if __USE_FORTIFY_LEVEL > 0. (Gentoo's gcc 4.3.3 has fortify enabled per default.) PS: I have no idea how to disable fortify, nor why __open_too_many_args is triggered.
I had the same problem with this error: /usr/include/bits/fcntl2.h:45: error: call to ‘__open_too_many_args’ declared with attribute error: open can be called either with 2 or 3 arguments, not more I was able to compile libraw1394-2.0.2 (and 2.0.0) using '-O0' in my CFLAGS
Which sys-devel/gcc do you have? No problem here with 4.3.2-r3 on amd64 and stock Gentoo libraw1394-2.0.0 or upstream 2.0.2, without or with -D_FORTIFY_SOURCE=2 in the CFLAGS. What if you add -U_FORTIFY_SOURCE to the CFLAGS (and keep -O2 instead of -O0)?
Adding -U_FORTIFY_SOURCE to CFLAGS does allow to me to compile libraw1394 with -O2.
Which gcc ebuild do you have installed, and on which architecture?
CFLAGS="-O2 -march=athlon64 -mtune=athlon64 -pipe" CHOST="i686-pc-linux-gnu" sys-devel/gcc-4.3.3-r2
The fortify issue is caused by a problem with libraw1394's build system. See bug 272540 for description and fix.
2.0.3 has just been released. This is a much needed release, because 2.0.2 contains a serious memory leak. Unfortunately the new release does not include a prebuilt configure script...
A 2.0.4 ebuild is underway, see bug 272540.
*libraw1394-2.0.4 (30 Jun 2009) 30 Jun 2009; Patrick Lauer <patrick@gentoo.org> +libraw1394-2.0.4.ebuild: Bump to 2.0.4, fixes #272540 *libraw1394-2.0.2 (28 Jun 2009) 28 Jun 2009; Patrick Lauer <patrick@gentoo.org> +libraw1394-2.0.2.ebuild: Bump to 2.0.2 *libraw1394-2.0.0 (31 Jan 2009) 31 Jan 2009; Stefaan De Roeck <stefaan@gentoo.org> +libraw1394-2.0.0.ebuild: Version bump to 2.0.0
