Opened 10 years ago
Closed 10 years ago
#43773 closed defect (fixed)
gmp: nawk: syntax error at source line 1 source file ./conf5pflxn/subs.awk
Reported by: | didier.regniaud@… | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | gmp |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi
When i tried to install bmp by
sudo port -v install gmp
i get the error:
... checking for readline/history.h... yes checking readline detected... yes checking for bison... bison -y checking for flex... flex checking lex output file root... lex.yy checking lex library... -ll checking whether yytext is a pointer... yes checking for ranlib... (cached) ranlib creating config.m4 configure: creating ./config.status config.status: creating demos/pexpr-config.h nawk: syntax error at source line 1 source file ./conf5pflxn/subs.awk context is >>> BEGIN <<< { nawk: bailing out at source line 255 config.status: error: could not create demos/pexpr-config.h Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.0.0" && ./configure --prefix=/opt/local --enable-cxx Exit code: 1 Error: Failed to configure gmp, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.0.0/config.log Error: org.macports.configure for port gmp returned: configure failure: command execution failed Warning: targets not executed for gmp: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port gmp for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port bmp failed
Any ideas?
Thanks
Didier
Change History (7)
comment:1 follow-ups: 2 3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to mcalhoun@… |
Summary: | mac port install gmp fail on Maverick → gmp: nawk: syntax error at source line 1 source file ./conf5pflxn/subs.awk |
comment:2 Changed 10 years ago by didier.regniaud@…
HI and thx a lot
It's ok when i desactivate nawk
Didier
ps : howto to close the ticket?
comment:3 Changed 10 years ago by cooljeanius (Eric Gallager)
Replying to ryandesign@…:
It looks like you have nawk installed, and gmp is incompatible with it. Try deactivating nawk, then building gmp, then (if desired) reactivating nawk again.
sudo port clean gmp sudo port -f deactivate nawk sudo port install gmp sudo port activate nawkIf that fixes it, we should add "conflicts_build nawk" to the port.
Or instead add a build dependency on gawk, which saves the user the trouble of having to deactivate nawk.
comment:5 follow-up: 6 Changed 10 years ago by neverpanic (Clemens Lang)
Or, try explicitly specifying a version of awk, e.g.
configure.env-append AWK=/usr/bin/awk
comment:6 Changed 10 years ago by cooljeanius (Eric Gallager)
Replying to cal@…:
Or, try explicitly specifying a version of awk, e.g.
configure.env-append AWK=/usr/bin/awk
Actually I suppose in this specific port's case that might be the better idea, because gawk might be installed with its +mpfr
variant, which would lead to a circular dependency... the mawk port does not experience the circular dependency issue though, and it gets checked between gawk
and nawk
in the AC_PROG_AWK
macro, so adding a build dependency on mawk could also work...
comment:7 Changed 10 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in r127048.
Thanks for the report.
It looks like you have nawk installed, and gmp is incompatible with it. Try deactivating nawk, then building gmp, then (if desired) reactivating nawk again.
If that fixes it, we should add "conflicts_build nawk" to the port.
I've seen many configure scripts be incompatible with nawk, so you may want to consider not re-activating nawk, and using a different awk implementation instead, such as gawk.