Opened 4 years ago
Closed 4 years ago
#61268 closed defect (fixed)
fdupes: error: possibly undefined macro: AC_SEARCH_LIBS and AC_ERROR
Reported by: | iefdev (Eric F) | Owned by: | grimreaper (Eitan Adler) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.3 |
Keywords: | Cc: | chrstphrchvz (Christopher Chavez) | |
Port: | fdupes |
Description
When upgrading to 2.1.2 in trace mode, I got 2 errors:
:info:configure autoreconf: running: /opt/local/bin/autoconf :info:configure configure.ac:18: error: possibly undefined macro: AC_SEARCH_LIBS :info:configure If this token and others are legitimate, please use m4_pattern_allow. :info:configure See the Autoconf documentation. :info:configure configure.ac:18: error: possibly undefined macro: AC_ERROR :info:configure autoreconf: /opt/local/bin/autoconf failed with exit status: 1 :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_github.com_macports_macports-ports_sysutils_fdupes/fdupes/work/fdupes-2.1.2" && autoreconf --install --verbose :info:configure Exit code: 1
It did upgrade without trace, but I guess it should work regardless of mode.
Attachments (1)
Change History (6)
Changed 4 years ago by iefdev (Eric F)
Attachment: | fdupes_-vst_destroot_main.log added |
---|
comment:1 Changed 4 years ago by grimreaper (Eitan Adler)
comment:2 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
This error is encountered by all builders which have tried building the 2.1.2 update: https://ports.macports.org/port/fdupes/builds
comment:3 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
Cc: | chrstphrchvz added |
---|
comment:4 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
A PR addressing this was opened: https://github.com/macports/macports-ports/pull/8631
comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Hi,
Mac OS X 10.7 seems quite old and thus difficult for me to test in the event its related to that. that said, its more likely this is me missing a dependency: can you try
and let me know if this fixes it.