[sr #110416] documentation: ordering of basic macros?

[Karl Berry]

Follow-up Comment #2, sr #110416 (project autoconf):

Thanks Zack. That's helpful. The "Autoconf Input Layout" node, with its
example, seems pretty good. I don't see any obvious changes to make, at least.
Fine with me to close this, if you want. (I'll add some text to the Automake
manual about it.)

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110403] autoconf-2.70 trips bug in here-doc handling in OmniOS /bin/sh

[Bob Friesenhahn]

Follow-up Comment #11, sr #110403 (project autoconf):

I see that https://www.illumos.org/issues/13405 addresses updating Illumos
ksh93 to a recent version.  The description says that the task is 'hard' but
the task is showing progress made.

Regardless, a note about the bug is certainly useful since a fix would not be
deployed and available to all for some time.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110403] autoconf-2.70 trips bug in here-doc handling in OmniOS /bin/sh

[Zack Weinberg]

Update of sr #110403 (project autoconf):

  Status:   Need Info => Not Autoconf   
 Open/Closed:Open => Closed 

___

Follow-up Comment #10:

I have filed https://www.illumos.org/issues/13434 for the shell bug.  Do you
think it's worth mentioning this issue in the Autoconf release notes?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110398] autoconf 2.70 breaks coreutils-8.32

[Ross Burton]

Follow-up Comment #5, sr #110398 (project autoconf):

FWIW this is fixed in autoconf git.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110418] Unable to specify build and target perl in cross builds

[Ross Burton]

URL:
  

 Summary: Unable to specify build and target perl in cross
builds
 Project: Autoconf
Submitted by: rossburton
Submitted on: Tue 05 Jan 2021 01:18:27 PM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
Operating System: None

___

Details:

When compiling autoconf in cross builds the location of the target perl binary
might be different to the host perl binary used at build time.

However, the same variable is used for both of these: autoconf.in uses @PERL@
in the shebang (target perl) but man/autoconf.w executes $PERL at buildtime
(build perl).

Might be possible to just remove the use of PERL in man/local.mk?




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110417] Do not generate a back up file when running autoreconf

[anonymous]

URL:
  

 Summary: Do not generate a back up file when running
autoreconf
 Project: Autoconf
Submitted by: None
Submitted on: Tue 05 Jan 2021 12:35:46 PM UTC
Category: None
Priority: 5 - Normal
Severity: 1 - Wish
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: nuquaquara...@gmail.com
 Open/Closed: Open
 Discussion Lock: Any
Operating System: None

___

Details:

Moving from autoconf v2.69 to v2.70, autoconf started to generate back-up
files of the configure script by appending a tilde ~. Give the opportunity to
the user to disable this behaviour, that is, do never generate a configure~.

The following is the response from Zack Weinberg to this request in the
mailing list on 04/Jan/2021: 

> It is not currently possible to disable this.  (The offending code is
> `sub update_file` in $prefix/share/autoconf/Autom4te/FileUtils.pm; if
> you look at it, you will see that the suffix used for the backup file
> can be changed with the $SIMPLE_BACKUP_SUFFIX environment variable,
> but there isn't any way to tell it not to create the backup at all.)

> Because FileUtils.pm is shared with Automake, changes require
> coordination between the two projects and take even longer than
> normal.  Would you please file an issue for this feature request,
> using https://savannah.gnu.org/support/?func=additem&group=autoconf
> (you may need to create an account) so we don't forget about it?






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/