[clc-devel] configure Option and gphoto2 / libgphoto2
Hi, i have seen that Arnaud MAZIN updated gphoto2 and libgphoto2, but libgphoto2 has (junk) files in /usr/share/doc. Here some general question: Why so many libraries and application are compiled with static option in configure? Why the option --disable-dependency-tracking is sometimes not enabled? Greetings Torsten PS: Sorry for my English!
Hi,
i have seen that Arnaud MAZIN updated gphoto2 and libgphoto2, but libgphoto2 has (junk) files in /usr/share/doc. Thanks for reporting this... it was actually me fixing the libgphoto2
Here some general question: Why so many libraries and application are compiled with static option in configure? grep enable-static */Pkgfile|wc -l in the CLC cvs dir tells me of 12
Hi, On Wed, Oct 08, 2003 at 22:14:41 +0200, thenschel@henschelsoft.de wrote: port and Matt updating both of them to the new version; Arnauld has not responded to e-mail lately. I'm not sure how we're going to handle updates in the umaintained collection in the future, but I guess someone will fix the /usr/share/doc thing :-) ports (of a total number of 460 in CLC cvs) use enable-static; that's a very small number (and two of them are actually false hits, and one port (xfce4) counts twice). I'm pretty sure the respective packager has a good reason to do this, but the answer is most certainly very different from port to port. In case of the xfce4 which makes up 6 out of 9 ports using static compilation, this is IIRC to avoid getting *.a libs which are not required.
Why the option --disable-dependency-tracking is sometimes not enabled? I had to check what this option does first, so the answer why I didn't enable it was because I didn't know about it. I guess it could save some time during the build, but I'm not sure if it's worth it; I could imagine that some (broken) packages wouldn't build correctly without it, so I think it is a sensible default for our packages to not disable it.
Quoting from http://www.delorie.com/gnu/docs/automake/automake_60.html: "Experience with earlier versions of Automake (8) taught us that it is not reliable to generate dependencies only on the maintainer's system, as configurations vary too much. So instead Automake implements dependency tracking at build time. " Not sure if this is still valid, though :-); Seeing that some gentoo ebuilds do this, it could be worth considering. Can someone comment on the time saved by this? Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Biel, Switzerland http://jw.tks6.net
Small correction to my previous post: On Thu, Oct 09, 2003 at 12:50:18 +0200, Johannes Winkelmann wrote:
Hi, [...] grep enable-static */Pkgfile|wc -l in the CLC cvs dir tells me of 12 ports (of a total number of 460 in CLC cvs) use enable-static; that's a it's 917 ports in CVS and 737 published via cvsup.
Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Biel, Switzerland http://jw.tks6.net
Hi, Johannes Winkelmann wrote:
Small correction to my previous post:
On Thu, Oct 09, 2003 at 12:50:18 +0200, Johannes Winkelmann wrote:
Hi,
[...]
grep enable-static */Pkgfile|wc -l in the CLC cvs dir tells me of 12 ports (of a total number of 460 in CLC cvs) use enable-static; that's a
i mean not the directly option, but in many/any ports is static automatic enabled by configure. For example: libgphoto2 gimp libsdl ... You can see this, if you type configure --help | grep --enable-static . I disabled allready the static mode and compile all only as shared and i haven't problems. Torsten
On Thu, Oct 09, 2003 at 12:50:18PM +0200, Johannes Winkelmann wrote:
Here some general question: Why so many libraries and application are compiled with static option in configure? grep enable-static */Pkgfile|wc -l in the CLC cvs dir tells me of 12 ports (of a total number of 460 in CLC cvs) use enable-static; that's a very small number (and two of them are actually false hits, and one port (xfce4) counts twice). I'm pretty sure the respective packager has a good reason to do this, but the answer is most certainly very different from port to port. In case of the xfce4 which makes up 6 out of 9 ports using static compilation, this is IIRC to avoid getting *.a libs which are not required.
Not really ;) The configure option for all xfce4* ports is --enable-static=no to avoid building of unneeded static libraries. Greetings Jürgen -- juergen.daubert@t-online.de
participants (4)
-
Johannes Winkelmann -
Juergen.Daubert＠t-online.de -
thenschel＠henschelsoft.de -
Torsten Henschel