Date: Wed, 30 Nov 2005 15:25:45 -0500 From: Chris McCormick <the.athenaeum@gmail.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Problem with aclocal when trying to install phppgadmin from port Message-ID: <8d3cd92e0511301225v6adc50c4ke5e397d61b68b08d@mail.gmail.com> In-Reply-To: <438E075C.3010401@infracaninophile.co.uk> References: <8d3cd92e0511301118i3357fa86y923b8b7795121bdd@mail.gmail.com> <438E075C.3010401@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew, Thank you for your explanation. I'll look into the ideas you put out there, which will probably lead to more questions. And just so I don't seem like a complete idiot, let me say that I am aware that I am re-installing phppgadmin (which administers PostgreSQL dbs) after an install of MySQL. I can't explain why this is so, but when I went to pkg_delete the MySQL client 4.0 package, it told me that it could not because (of all things) phppgadmin depended upon it. Why that is, I couldn't tell you, but when I uninstalled phppgadmin, I was able to uninstall (and then upgrade) the MySQL client successfully. The irony of all of this is that I am a heavy user of postgres, but I onl= y recently decided to upgrade MySQL to use it with a blog. Previously, I hadn't really used it. Now, as a result, I have to manage my postgres install through the command line until I get this fixed. Thanks again for your help, Chris On 11/30/05, Matthew Seaman <m.seaman@infracaninophile.co.uk> wrote: > > Chris McCormick wrote: > > Hello all, > > I am still somewhat of a newbie with FreeBSD, so feel free to direct > me to > > any better resources, or a better place to ask this question. > > > > I had to to a pkg_delete on phppgadmin, as I was re-installing mysql. > > After that, I pulled down a newer version of phppgadmin and tried to > install > > it. I got the follwoing output: > > Errr... Perhaps you might find phpMyAdmin works better with mysql. Or > conversely that postgresql works better with phpPgAdmin. > > > > -------------------------------------------------------------------------= ------------------------------------------------------------ > > > > www# pwd > > /usr/ports/databases/phppgadmin > > www# make install > > =3D=3D=3D> Installing for phppgadmin-4.0 > > =3D=3D=3D> phppgadmin-4.0 depends on file: /usr/local/include/php/mai= n/php.h > - > > found > > =3D=3D=3D> phppgadmin-4.0 depends on file: > /usr/local/lib/php/20020429/pgsql.so > > - not found > > =3D=3D=3D> Verifying install for /usr/local/lib/php/20020429/pgsql.s= o in > > /usr/ports/databases/php4-pgsql > > =3D=3D=3D> php4-pgsql-4.4.1_2 depends on executable: phpize - found > > =3D=3D=3D> php4-pgsql-4.4.1_2 depends on file: /usr/local/bin/autocon= f259 - > > found > > =3D=3D=3D> php4-pgsql-4.4.1_2 depends on shared library: pq.3 - found > > =3D=3D=3D> PHPizing for php4-pgsql-4.4.1_2 > > aclocal: not found > > *** Error code 1 > > > > Stop in /usr/ports/databases/php4-pgsql. > > *** Error code 1 > > > > Stop in /usr/ports/databases/phppgadmin. > > www# > > aclocal is part of the automake port -- or rather, it's part of /one/ of > the > automake ports. There are at least three versions of automake in ports, > and > they've been modified so that the different versions can all be installed > simultaneously. Similarly for autoconf. Thats because there are > incompatible > changes between different versions of the Gnu autotools, and software > using the > Gnu configure system can't be upgraded to use a more recent version of > them > without quite a lot of work. So those upgrades tend not to happen. > > Anyhow, for the ports to work using autotools, you need to install > automake, etc > from the ports. Usually that will happen automatically, but if you've > installed, > say, automake directly from the Gnu tarball without reference to ports, i= t > can > cause problems. The program names will be tagged with the version > numbers. > > Also, as aclocal and automake are perl scripts, and as they have formerly > been > infamous for causing mayhem by including the perl version number into > themselves, > you may have needed to re-install the automake ports after upgrading > perl. That > bug was squashed relatively recently, so this might still apply to your > system. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. Flat 3 > 7 Priory Courtyard > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > Kent, CT11 9PW, UK > > > -- --------------------------------------------------------------------- Chris McCormick, webmaster The Athenaeum - Interactive Humanities Online http://www.the-athenaeum.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d3cd92e0511301225v6adc50c4ke5e397d61b68b08d>