Opened 13 years ago
Closed 13 years ago
#32641 closed defect (wontfix)
Build of gdbm fails
Reported by: | j.renz@… | Owned by: | neverpanic (Clemens Lang) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | lack-of-interest | Cc: | |
Port: | gdbm |
Description (last modified by neverpanic (Clemens Lang))
This error happens with both compilers
sudo port install gdbm configure.compiler=llvm-gcc-4.2 ---> Computing dependencies for gdbm ---> Fetching archive for gdbm ---> Attempting to fetch gdbm-1.10_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/gdbm ---> Fetching gdbm ---> Verifying checksum(s) for gdbm ---> Extracting gdbm ---> Configuring gdbm Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details) Log for gdbm is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_gdbm/gdbm/main.log Error: Status 1 encountered during processing.
Attachments (1)
Change History (7)
Changed 13 years ago by j.renz@…
comment:1 Changed 13 years ago by neverpanic (Clemens Lang)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to cal@… |
Status: | new → assigned |
Please remember to use WikiFormatting when pasting shell output into a ticket.
The problem is apparently caused by gdbm's configure script detecting your nawk install, which it prefers over /usr/bin/awk. However, I cannot reproduce your problem with the current nawk from MacPorts installed, although configure picks it up correctly. Can you attach the config.log?
A quickfix for your problem would probably be to uninstall nawk or install mawk or gawk, because those are preferred over nawk in gdbm's configure.
comment:2 Changed 13 years ago by j.renz@…
Hi tahnks for the tipp, the suggested workaround worked. BUt after installing it looks like there in no config.log anymore?
comment:3 Changed 13 years ago by neverpanic (Clemens Lang)
MacPorts cleans the config.log on successful builds, unless you specify the -k flag. Only the config.log of the failed build is interesting anyway, though, and that one is probably gone now.
comment:4 Changed 13 years ago by neverpanic (Clemens Lang)
Are you still interested in getting this resolved or do you consider the workaround sufficient?
comment:6 Changed 13 years ago by neverpanic (Clemens Lang)
Keywords: | lack-of-interest added |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
Logfile