Menu
▾
▴
#8 0.4.3 autoconf fails
Sorry but this form insists on treating pasted material as markdown. autoconf configure.ac fails with the following output:
# configure is writing to config.log, and then calls config.status. # config.status does its own redirection, appending to config.log. # Unfortunately, on DOS this fails, as config.log is still kept open # by configure, so config.status won't be able to write to it; its # output is si# configure is writing to config.log, and then calls config.status. # config.status does its own redirection, appending to config.log. # Unfortunately, on DOS this fails, as config.log is still kept open # by configure, so config.status won't be able to write to it; its # output is simply discarded. So we exec the FD to /dev/null, # effectively closing config.log, so it can be properly (re)opened and # appended to b# configure is writing to config.log, and then calls config.status. # config.status does its own redirection, appending to config.log. # Unfortunately, on DOS this fails, as config.log is still kept open # by configure, so config.status won't be able to write to it; its # output is simply discarded. So we exec the FD to /dev/null, # effectively closing config.log, so it can be properly (re)opened and # appended to by config.status. When coming back to configure, we # need to make the FD available again. if test "$no_create" != yes; then ac_cs_success=: ac_config_status_args= test "$silent" = yes && ac_config_status_args="$ac_config_status_args --quiet" exec 5>/dev/null $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false exec 5>>config.log # Use ||, not &&, to avoid exiting from the if with $? = 1, which# configure is writing to config.log, and then calls config.status. # config.status does its own redirection, appending to config.log. # Unfortunately, on DOS this fails, as config.log is still kept open # by configure, so config.status won't be able to write to it; its # output is simply discarded. So we exec the FD to /dev/null, # effectively closing config.log, so it can be properly (re)opened and # appended to by config.status. When coming back to configure, we # need to make the FD available again. if test "$no_create" != yes; then ac_cs_success=: ac_config_status_args= test "$silent" = yes && ac_config_status_args="$ac_config_status_args --quiet" exec 5>/dev/null $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false exec 5>>config.log # Use ||, not &&, to avoid exiting from the if with $? = 1, which # would make configure fail if this is the last instruction. $ac_cs_success || as_fn_exit 1 fi if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} fi configure.ac:17: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:23: error: possibly undefined macro: AM_PROG_CC_C_O configure.ac:25: error: possibly undefined macro: AM_PROG_AR # would make configure fail if this is the last instruction. $ac_cs_success || as_fn_exit 1 fi if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} fi configure.ac:17: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:23: error: possibly undefined macro: AM_PROG_CC_C_O configure.ac:25: error: possibly undefined macro: AM_PROG_AR y config.status. When coming back to configure, we # need to make the FD available again. if test "$no_create" != yes; then ac_cs_success=: ac_config_status_args= test "$silent" = yes && ac_config_status_args="$ac_config_status_args --quiet" exec 5>/dev/null $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false exec 5>>config.log # Use ||, not &&, to avoid exiting from the if with $? = 1, which # would make configure fail if this is the last instruction. $ac_cs_success || as_fn_exit 1 fi if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} fi configure.ac:17: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:23: error: possibly undefined macro: AM_PROG_CC_C_O configure.ac:25: error: possibly undefined macro: AM_PROG_AR mply discarded. So we exec the FD to /dev/null, # effectively closing config.log, so it can be properly (re)opened and # appended to by config.status. When coming back to configure, we # need to make the FD available again. if test "$no_create" != yes; then ac_cs_success=: ac_config_status_args= test "$silent" = yes && ac_config_status_args="$ac_config_status_args --quiet" exec 5>/dev/null $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false exec 5>>config.log # Use ||, not &&, to avoid exiting from the if with $? = 1, which # would make configure fail if this is the last instruction. $ac_cs_success || as_fn_exit 1 fi if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} fi configure.ac:17: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:23: error: possibly undefined macro: AM_PROG_CC_C_O configure.ac:25: error: possibly undefined macro: AM_PROG_AR
EDIT by Rescuezilla: surrounded output with triple backticks (```)
Discussion
Anonymous
Diff:
Hi Dan,
You can place output between two triple backtick (```) strings to display the text correctly as an unformatted block. I have edited your post to fix the formatting.
What operating system are you trying to compile on? And which version of the operating system?
The following works for me on Debian 10 (Buster), but I don't recall the build dependencies:
The launches imagemount correctly. But partclone-util's v0.4.3's imagemount is not that useful due to a number of issues (see tickets).
Given the absence of anybody else fixing the issues, I will try and improve things for the upcoming Rescuezilla v2.3 (scheduled for release in November 2021).
Last edit: Rescuezilla 2021-08-18
Thanks.
I could not figure out how to edit it. Any tips?
EDIT by Rescuezilla: Remove quoting of entire previous reply.
Last edit: Rescuezilla 2021-08-18
I have edited your post to fix the formatting.
What platform are you trying to compile partclone-utils for? I see from some of your previous comments you mention macOS. I haven't yet tried partclone-utils on that platform, and won't be for some time. It may work, though I don't know macOS's level of support for the required Network Block Device dependency.
You may prefer to create a Rescuezilla USB stick for an easy environment that can run on Intel-based Mac machines, and then you can open a Terminal to run partclone-nbd (or try it the Image Explorer (beta) feature).
Whatever tool you use, large compressed images (>5GB) are too slow to be useful.
This was for linux. After much searching I found out how to install without needing to build (I think).
I was tring to find a use for my mac mini but my machine configuration was so unstable that it would spontaneously restart or freeze.
I just sold it and am in the process of building a new linux box.
Thanks for your assistance,
Dan
EDIT by Rescuezilla: Remove quoting of entire previous reply.
Last edit: Rescuezilla 2021-08-19
OK that sounds good.
Just to re-iterate, your best bet is definitely to create a Rescuezilla USB stick and use Rescuezilla to create uncompressed images.
Uncompressed images will mount quickly and easily using its "Image Explorer" feature in Rescuezilla. Do not use Image Explorer with the default compressed images (because compressed images will cause instability).
I will close this ticket now.
Thanks again for the guidance on this
EDIT by Rescuezilla: Remove quoting of entire previous reply.
Last edit: Rescuezilla 2021-09-08