Re: Building with --without-system-serf
On 15/02/2013 Andre Fischer wrote: I am probably responsible for this code. If you can make it better, and have not not already done so, then please do it. Thanks, committed (but I only made the minimal changes for --without-system-serf, not a global cleanup). Regards, Andrea.
Re: Building with --without-system-serf
On Fri, Feb 15, 2013 at 9:32 AM, Ariel Constenla-Haile arie...@apache.orgwrote: On Fri, Feb 15, 2013 at 09:04:37AM -0800, Kay Schenk wrote: On Wed, Feb 13, 2013 at 1:11 PM, Andrea Pescetti pesce...@apache.org wrote: I've been busy with building lately, especially with building on Fedora 18 with the --with-system-libs switch, which should be used for packaging in Fedora. This is preparation work for the Fedora 19 packaging. Well good for you! I've had some thoughts about this proposed packaging. This is unrelated to your question here, but something I've been thinking about. Should we be using OpenJDK in building and packaging for Fedora instead of Oracle Java to ensure compatibility? Hopefully no anomolies will crop up but you never know. Building and packaging for Fedora 19 has to be done in Fedora 19 (that is, rawhide), where obviously you use the javac that is there in the system by default, together with all the system jars and libraries (a sort of Odyssey, given that no one has been trying that). Regards OK, thanks Ariel...of course this makes sense. It also seems one could include/use other resources as long as they followed Fedora licensing guidelines. But anyway, we need to use OpenJDK for this. -- Ariel Constenla-Haile La Plata, Argentina -- MzK Achieving happiness requires the right combination of Zen and Zin.
Re: Building with --without-system-serf
On Feb 13, 2013 10:12 PM, Andrea Pescetti pesce...@apache.org wrote: I've been busy with building lately, especially with building on Fedora 18 with the --with-system-libs switch, which should be used for packaging in Fedora. This is preparation work for the Fedora 19 packaging. To isolate the problematic dependencies, I configure with something like ./configure --with-system-libs --without-system-NAME1 --without-system-NAME2 [...] The effect in general is that the without switch overrides the generic --with-system-libs. So for example ./configure --with-system-libs --without-system-libxslt won't use the system library. Now, some libraries use a different convention: ./configure --with-system-libs --without-system-serf will still use the system library and not override the generic choice. You can see the different patterns in http://svn.apache.org/viewvc/openoffice/trunk/main/configure.in?view=markup (4002-4003 for the former pattern, 4579 for the latter) Any technical reasons for that? Otherwise I'll assume lazy consensus and modify configure.in to use the former pattern consistently, at least in the cases where I need it. I am probably responsible for this code. If you can make it better, and have not not already done so, then please do it. -Andre The patch would be a variant of: -if test x$with_system_serf = xyes -o -n $with_system_libs; then +if test -n $with_system_serf -o -n $with_system_libs \ + test $with_system_serf != no; then Regards, Andrea.
Re: Building with --without-system-serf
On Fri, Feb 15, 2013 at 09:04:37AM -0800, Kay Schenk wrote: On Wed, Feb 13, 2013 at 1:11 PM, Andrea Pescetti pesce...@apache.orgwrote: I've been busy with building lately, especially with building on Fedora 18 with the --with-system-libs switch, which should be used for packaging in Fedora. This is preparation work for the Fedora 19 packaging. Well good for you! I've had some thoughts about this proposed packaging. This is unrelated to your question here, but something I've been thinking about. Should we be using OpenJDK in building and packaging for Fedora instead of Oracle Java to ensure compatibility? Hopefully no anomolies will crop up but you never know. Building and packaging for Fedora 19 has to be done in Fedora 19 (that is, rawhide), where obviously you use the javac that is there in the system by default, together with all the system jars and libraries (a sort of Odyssey, given that no one has been trying that). Regards -- Ariel Constenla-Haile La Plata, Argentina pgpCkx00sfMDy.pgp Description: PGP signature
Re: Building with --without-system-serf
On 2/13/13 10:11 PM, Andrea Pescetti wrote: I've been busy with building lately, especially with building on Fedora 18 with the --with-system-libs switch, which should be used for packaging in Fedora. This is preparation work for the Fedora 19 packaging. To isolate the problematic dependencies, I configure with something like ./configure --with-system-libs --without-system-NAME1 --without-system-NAME2 [...] The effect in general is that the without switch overrides the generic --with-system-libs. So for example ./configure --with-system-libs --without-system-libxslt won't use the system library. Now, some libraries use a different convention: ./configure --with-system-libs --without-system-serf will still use the system library and not override the generic choice. You can see the different patterns in http://svn.apache.org/viewvc/openoffice/trunk/main/configure.in?view=markup (4002-4003 for the former pattern, 4579 for the latter) Any technical reasons for that? Otherwise I'll assume lazy consensus and modify configure.in to use the former pattern consistently, at least in the cases where I need it. The patch would be a variant of: -if test x$with_system_serf = xyes -o -n $with_system_libs; then +if test -n $with_system_serf -o -n $with_system_libs \ + test $with_system_serf != no; then I believe you don't have to wait, just fix it. Cleaning up and document configure would be a nice job for somebody who is familiar with autoconf, configure etc. Juergen
Building with --without-system-serf
I've been busy with building lately, especially with building on Fedora 18 with the --with-system-libs switch, which should be used for packaging in Fedora. This is preparation work for the Fedora 19 packaging. To isolate the problematic dependencies, I configure with something like ./configure --with-system-libs --without-system-NAME1 --without-system-NAME2 [...] The effect in general is that the without switch overrides the generic --with-system-libs. So for example ./configure --with-system-libs --without-system-libxslt won't use the system library. Now, some libraries use a different convention: ./configure --with-system-libs --without-system-serf will still use the system library and not override the generic choice. You can see the different patterns in http://svn.apache.org/viewvc/openoffice/trunk/main/configure.in?view=markup (4002-4003 for the former pattern, 4579 for the latter) Any technical reasons for that? Otherwise I'll assume lazy consensus and modify configure.in to use the former pattern consistently, at least in the cases where I need it. The patch would be a variant of: -if test x$with_system_serf = xyes -o -n $with_system_libs; then +if test -n $with_system_serf -o -n $with_system_libs \ + test $with_system_serf != no; then Regards, Andrea.
