They rerolled the tarball to change the manpage. Looks like they added
a new dia.1 right before the release, and forgot to take the old one
out of the tarball.
Extra special thanks to the dia team for not bumping the version number ;;)
Submitted by: "Florian C. Smeets" <flo@kasimir.com>
Situation:
- The PTP2 driver doesn't work for G5
- The G3 driver can't be used a G5
- So the canon native driver has been tought the G5's id etc ...
- Bumped port revision, since the G5 PTP2 support was in
test status and the G5 canon native driver support
- fixes G5 PTP2 flaws and
- is kind of new functionality
These patches have been sent to the gphoto devel team and
have been included into CVS today. Since yestarday 2.1.3
has been releases this fix will show up in later versions of
libgphoto.
Note 1: when using gphoto --auto-detect unluckily the buggy PTP2 driver
will be autodetected. You then have to choose manually the correct
driver. Easiest way is to use digikam->Setup and to Choose driver called
"Canon PowerShot G5 (normal mode)".
Note 2: If you want to use digikam as non-root user, you have to tweak
permissions of /dev/ugenX and /dev/ugenX.{1,2,3}
I succeded by using the following commands which I put into /etc/rc.local,
thanks to Poul-Henning Kamp:
/sbin/devfs ruleset 10
/sbin/devfs rule applyset
/sbin/devfs rule add path ugen1* mode 666
/sbin/devfs rule show
A working solution for /etc/devfs.rules I didn't find yet.
Approved by: portmgr@freebsd.org (Joe)
. run the vendor-supplied test automaticly upon building;
. link the vendor-supplied test dynamicly (using -rpath to
force the usage of the just-built library) -- to add another
implicit test of the shared library's validity;
. reword one of the shell commands as ``sed ... file'' instead
of ``cat file | sed ...'';
. modify one of the files to make it properly compilable by the
icc -- gcc was, apparently, optimizing the junk out anyway.
Approved by: maintainer (ache)
This is a temporary update, because of issues with sound support.
More fixes will be on the way for quicktime, vorbis, ogg, openal, etc...
PR: ports/58231
Submitted by: David Yeske <dyeske@yahoo.com>
> I'm a bit confused here - where am I using the -fpic flag?
It comes from kmod.mk, I think. Anyway, it turns out this is
a bug in kmod.mk and kernel modules are not yet implemented on
amd64. The previous change should be backed out - sorry for
the misleading suggestion.