#13454 closed defect (fixed)
postgresql82 on 10.4.11 machine with macports 1.5 fails to install
Reported by: | xelldran1@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.5.2 |
Keywords: | postgresql82 10.4.11 | Cc: | boeyms@… |
Port: |
Description
Trying to install postgresql82 and get the following error:
$ sudo port install -v postgresql82 +python +krb5 +perl ---> Fetching postgresql82 ---> Attempting to fetch postgresql-base-8.2.5.tar.bz2 from ftp://ftp2.ch.postgresql.org/mirror/postgresql/source/v8.2.5 ---> Attempting to fetch postgresql-base-8.2.5.tar.bz2 from ftp://ftp.postgresql.org/pub/source/v8.2.5 ---> Attempting to fetch postgresql-opt-8.2.5.tar.bz2 from ftp://ftp2.ch.postgresql.org/mirror/postgresql/source/v8.2.5 ---> Attempting to fetch postgresql-opt-8.2.5.tar.bz2 from ftp://ftp.postgresql.org/pub/source/v8.2.5 ---> Attempting to fetch postgresql-test-8.2.5.tar.bz2 from ftp://ftp2.ch.postgresql.org/mirror/postgresql/source/v8.2.5 ---> Attempting to fetch postgresql-test-8.2.5.tar.bz2 from ftp://ftp.postgresql.org/pub/source/v8.2.5 ---> Verifying checksum(s) for postgresql82 ---> Extracting postgresql82 ---> Configuring postgresql82 ---> Building postgresql82 ^[ORError: Target org.macports.build returned: shell command "cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_postgresql82/work/postgresql-8.2.5/contrib/adminpack/ && {unset LD_PREBIND LD_PREBIND_ALLOW_OVERLAP && gnumake}" returned error 127 Command output: sh: line 1: {unset: command not found Error: Status 1 encountered during processing.
It looks like the adminpack contribution is what is fouling up the build . . . normally i would just remove that but I kind of need it for what I'm doing so a fix would be much appreciated.
Change History (3)
comment:1 Changed 17 years ago by boeyms@…
Cc: | boeyms@… added |
---|---|
Milestone: | → Port Bugs |
Owner: | changed from macports-dev@… to mww@… |
comment:2 Changed 17 years ago by mww@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
This has been fixed with port version 1.6 and the latest postgresql82 (and postgresl81 and postgresql83) Portfile.
If the problem persists, please re-open this ticket will a full trace!
Note: See
TracTickets for help on using
tickets.
(Reassigning to one of the port's maintainers)
From the comments on ticket:12994, in particular comment:ticket:12994:44, comment:ticket:12994:45, and comment:ticket:12994:46, this problem should have been fixed in changeset:31614. Please run a
port selfupdate
if you haven't done so recently, try building postgresql82 again, and let us know whether or not it now works.