Re: Assigning command output to a variable

2012-11-19 Thread Adam Mercer
On Mon, Nov 19, 2012 at 1:36 PM, Stefano Lattarini wrote: > According to the Autoconf manual, the Tru64/OSF 5.1 sh might abort if > the above is run and the /etc/redhat-release file doesn't exist, since > that shell treats 'read' as a special (in POSIX sense) built-in. See > also Automake commit

Re: Assigning command output to a variable

2012-11-19 Thread Adam Mercer
On Mon, Nov 19, 2012 at 12:36 PM, Eric Blake wrote: > You can avoid the command substitution fork by using read: > > { read redhat_release < /etc/redhat-release; } 2>/dev/null > > Whether that's deemed any simpler, though, is a matter of taste. Not to > mention that use of 'read' like this is li

Re: Global autoconf cache

2012-11-19 Thread Eric Blake
On 11/19/2012 02:32 PM, Richard Stallman wrote: > I personally spent quite a significant amount of time fixing a few > configure.{ac,in} files in various packages, but in the end, we gave up > with this idea and no longer use the autoconf cache. > > If we use the cache for standard tes

Re: Global autoconf cache

2012-11-19 Thread Richard Stallman
I personally spent quite a significant amount of time fixing a few configure.{ac,in} files in various packages, but in the end, we gave up with this idea and no longer use the autoconf cache. If we use the cache for standard tests only, could that fix this problem? -- Dr Richard Stal

need help building and installing in non-standard place

2012-11-19 Thread Gary Aitken
I'm sure this has been addressed already, but I couldn't find what I needed searching the archives. I'm trying to build gimp-2.8.2 on freebsd, and am doing it step-wise from the individual dependent packages. What I tried (among other things...): unpack in /usr/home/foo/gimp_2_8/work cd glib-

Re: Assigning command output to a variable

2012-11-19 Thread Stefano Lattarini
On 11/19/2012 07:36 PM, Eric Blake wrote: > On 11/19/2012 10:09 AM, Adam Mercer wrote: >> Hi >> >> For one of my projects I need to get the contents of >> /etc/redhat-release during the configure process and assign the >> contents to a variable. I'm currently using the following: >> >> redhat_r

Re: Global autoconf cache

2012-11-19 Thread Wookey
+++ Thomas Petazzoni [2012-11-19 15:49 +0100]: > In Buildroot [1], we had support to use an autoconf cache to speed up > the build. This autoconf cache was shared amongst packages, with the > idea that once a package has verified that such or such system feature > was available or not, it would be

Re: Assigning command output to a variable

2012-11-19 Thread Eric Blake
On 11/19/2012 10:09 AM, Adam Mercer wrote: > Hi > > For one of my projects I need to get the contents of > /etc/redhat-release during the configure process and assign the > contents to a variable. I'm currently using the following: > > redhat_release=`cat /etc/redhat-release 2> /dev/null` >

Assigning command output to a variable

2012-11-19 Thread Adam Mercer
Hi For one of my projects I need to get the contents of /etc/redhat-release during the configure process and assign the contents to a variable. I'm currently using the following: redhat_release=`cat /etc/redhat-release 2> /dev/null` This works fine, but I was wondering if anyone had any bett

Re: Global autoconf cache

2012-11-19 Thread Thomas Petazzoni
Dear Richard Stallman, On Wed, 14 Nov 2012 16:49:58 -0500, Richard Stallman wrote: > The global cache that autoconf formerly used was very good for > efficiency of autoconf, especially when building lots of packages. > Without that, it is slow. > > I am told it had a problem: results depended on