** Changed in: system-config-printer (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778491
Title:
strange inverted commas
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/778491/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
From [email protected] Sun Apr 21 15:20:52 2013
Return-path: <[email protected]>
Envelope-to: [email protected]
Delivery-date: Sun, 21 Apr 2013 15:20:52 -0700
Received: from exprod5mx254.postini.com ([64.18.0.49] helo=psmtp.com)
by mail-archive.com with esmtp (Exim 4.76)
(envelope-from <[email protected]>)
id 1UU2cu-0003fk-Lw
for [email protected]; Sun, 21 Apr 2013 15:20:52 -0700
Received: from lists.gnu.org ([208.118.235.17]) (using TLSv1) by
exprod5mx254.postini.com ([64.18.4.10]) with SMTP;
Sun, 21 Apr 2013 14:20:52 PST
Received: from localhost ([::1]:50663 helo=lists.gnu.org)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from <[email protected]>)
id 1UU2ct-0007PX-7p
for [email protected]; Sun, 21 Apr 2013 18:20:51 -0400
Received: from eggs.gnu.org ([208.118.235.92]:42761)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from <[email protected]>) id 1UU2cl-0007PJ-VR
for [email protected]; Sun, 21 Apr 2013 18:20:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
(envelope-from <[email protected]>) id 1UU2ci-0001Lm-BR
for [email protected]; Sun, 21 Apr 2013 18:20:43 -0400
Received: from mail-ob0-x22e.google.com ([2607:f8b0:4003:c01::22e]:59262)
by eggs.gnu.org with esmtp (Exim 4.71)
(envelope-from <[email protected]>) id 1UU2ci-0001Lg-3l
for [email protected]; Sun, 21 Apr 2013 18:20:40 -0400
Received: by mail-ob0-f174.google.com with SMTP id wc20so1932322obb.5
for <[email protected]>; Sun, 21 Apr 2013 15:20:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:x-received:in-reply-to:references:date:message-id
:subject:from:to:cc:content-type;
bh=qULpYciWkbkTJGmNn1Gn7FBChbAvPy6dv/RaDxGAFX8=;
b=auqh36YD58AZslagPB5AGpCgSDENm5AoYpn41wQBD1y7nnVGE9uIg5NwAqotOGoRj1
dSxKLnmAl1UtrTmZAM1UvKRnl1kzPaCBVZjtFe3NTZ9yxhUqTCQYgMk6fm6IXB885nFf
06EogxqVuBoU6sUtqSD5s7kRCwRHgAC0ePB+6YrAZp/JVNAp9Ej2NgkBU4AL11GhcM61
484RrMI2yljHMfqcv0reyS2mPfU8s9SczpHD51hdC7lyDM34+rxAFj1jTEg5U+mA24Ud
t2KYR7AGjo7zu3GE5tfRtOf9Y3mchqvcOvulSxWCDOWK7jzK8m7cffMW/SC/XxQXX+vn
fnXw==
MIME-Version: 1.0
X-Received: by 10.182.78.41 with SMTP id y9mr12747067obw.69.1366582839393;
Sun, 21 Apr 2013 15:20:39 -0700 (PDT)
Received: by 10.60.7.169 with HTTP; Sun, 21 Apr 2013 15:20:39 -0700 (PDT)
In-Reply-To: <[email protected]>
References:
<CAKPWYQ0qdjNsR==8awoyckxv29peYQOfdtdrTwOFhBREfH=i...@mail.gmail.com>
<[email protected]>
Date: Sun, 21 Apr 2013 23:20:39 +0100
Message-ID: <CAKPWYQ2P_reQqa+nX-rV=P7T+jDPDiCQvXbKt=kv+-amafh...@mail.gmail.com>
Subject: Re: Feature suggestion: Option to generate a Makefile include file
containing assignments for all of the output variables
From: Gavin Smith <[email protected]>
To: Nick Bowler <[email protected]>
X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address
(bad octet value).
X-Received-From: 2607:f8b0:4003:c01::22e
Cc: [email protected]
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
<mailto:[email protected]?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
<mailto:[email protected]?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: [email protected]
Sender: [email protected]
X-pstn-neptune: 0/0/0.00/0
X-pstn-levels: (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390
R:95.9108 P:95.9108 M:88.1613 C:98.6951 )
X-pstn-dkim: 1 h/-/B [no valid signature]
X-pstn-settings: 3 (1.0000:1.0000) s cv gt4 gt3 gt2 gt1 r p m c
X-pstn-addresses: from <[email protected]> [320/11]
>> My suggestion would provide a simpler way which would work for most use
>> cases. It would be to generate a file (called, say, "config.mk") which
>> contained all these assignments automatically.
I thought I'd report back what I've been using. I have a m4 file which
I use with aclocal. (It actually creates two files in each
subdirectory (config.mk.in and dir.mk.in), but this would be easy to
change as appropriate.)
> Note also that just because something is AC_SUBSTed does not mean that
> it is syntactically valid to stick in a Makefile like this. Automake
> also provides AM_SUBST_NOTMAKE to suppress the automatic Makefile.in
> assignment, and you may want something similar.
I'm doing this using a patched automake which sets
am_subst_notmake_$var if var is declared with AM_SUBST_NOTMAKE.
ax_config_include.m4:
--
# Create config.mk.in and dir.mk.in in source tree.
AC_DEFUN([_AX_CONFIG_INCLUDE],
[for ac_file in $@; do
t=$srcdir/$ac_file.in
d=$srcdir/$(dirname $ac_file)/dir.mk.in
rm -f $t $d
for ac_var in $ac_subst_vars; do
eval am_var=am_subst_notmake_\$ac_var
eval am_var_val=\$$am_var
if test -n "$am_var_val"; then :; else
echo $ac_var = \@$ac_var\@ >> $t
fi
done
# These variables are substituted within config.status
# on a Makefile-by-Makefile basis.
for var in \
top_builddir top_build_prefix \
srcdir abs_srcdir top_srcdir abs_top_srcdir \
builddir abs_builddir abs_top_builddir; do
echo "$var = @$var@" >> $d
done
echo am__aux_dir = $am_aux_dir >> $d
done
])
AC_DEFUN([AX_CONFIG_INCLUDE],
[AC_CONFIG_COMMANDS_PRE([_AX_CONFIG_INCLUDE($@)])
# This will cause automake to generate rebuild rules
AC_CONFIG_FILES($@)
for ac_file in $@; do
dir_mk_name=$(dirname $ac_file)/dir.mk
AC_CONFIG_FILES([$dir_mk_name])
done
])
--
This generates a config.mk.in file as well. This is slightly against
current autoconf philosophy; otherwise config.h.in would be generated
by configure instead of the user having to remember to run autoheader.
> To be honest, most Autoconf-using packages use Automake, and it's
> unclear that Automake would be able to make use of this feature. In
> particular, Automake needs to suppress these definitions for assignments
> that are explicitly written into Makefile.am. More importantly, a
> package can have more than one Makefile.am file, some of which have
> explicit assignments and others do not. So I'm not sure if this
> feature would be useful to very many packages.
Out of interest, is there any reason why anybody would want/need to be
overriding the assignments that emanate from autoconf? (I understand
that it is done, and stopping it being done would be
backwards-incompatible.) Also on tests I did, if a variable was
defined multiple times in a makefile, make took the definition that
occurred latest in the file, so overriding definitions is possible, at
least in GNU make.
Regards,
Gavin Smith
(Apologies for the double reply.)
On Mon, Apr 1, 2013 at 3:23 PM, Nick Bowler <[email protected]> wrote:
> On 2013-03-30 14:56 +0000, Gavin Smith wrote:
>> autoconf-generated configure scripts substitute strings like @var@ in files
>> like for the value of output variables set in the configure script. Most of
>> the time, these will only be used in lines like
>>
>> var = @var@
>>
>> in Makefile.in. The Makefile.in may have many of these lines. In fact,
>> automake scans configure.ac for use of the AC_SUBST macro and automatically
>> adds such lines to the generated Makefile.in.
>>
>> It can be confusing to try to understand what it means for variables to
>> copied from one level of the build system to another. If a user writes
>> Makefile.in by hand, they will have to write out all these lines manually.
>> Also, it's hard to read Makefile.in's because of such lines.
>>
>> My suggestion would provide a simpler way which would work for most use
>> cases. It would be to generate a file (called, say, "config.mk") which
>> contained all these assignments automatically. I.e., config.mk would
>> contain lines like
>>
>> CC = cc
>> CXX = g++
>>
>> and so on. Then in the Makefile, have a line "include config.mk". The
>> output variables would be referred to in the Makefile as ordinary
>> environment variable (e.g. $(CC)).
> [...]
>
> To be honest, most Autoconf-using packages use Automake, and it's
> unclear that Automake would be able to make use of this feature. In
> particular, Automake needs to suppress these definitions for assignments
> that are explicitly written into Makefile.am. More importantly, a
> package can have more than one Makefile.am file, some of which have
> explicit assignments and others do not. So I'm not sure if this
> feature would be useful to very many packages.
>
> But the good news is that Autoconf can already be used for something
> very close to what you are asking. Totally untested, but you could add
> something like the following (perhaps with more error checking) to your
> bootstrap script:
>
> % autoconf --trace 'AC_SUBST:$1' | sed 's/.*/& = @&@/' > config.mk.in
>
> then add AC_CONFIG_FILES([config.mk]) to configure.ac.
>
> Note also that just because something is AC_SUBSTed does not mean that
> it is syntactically valid to stick in a Makefile like this. Automake
> also provides AM_SUBST_NOTMAKE to suppress the automatic Makefile.in
> assignment, and you may want something similar.
>
> Cheers,
> --
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
_______________________________________________
Autoconf mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/autoconf
