New port questions
Michael C. Shultz
reso3w83 at verizon.net
Wed Feb 9 09:39:02 PST 2005
On Wednesday 09 February 2005 09:31 am, Paul Schmehl wrote:
> I'm creating a new port - security/barnyard. I *thought* I had it
> working right, and all of a sudden it's broken. Turns out some
> changes have apparently been made to the configure.in script that
> break the build.
> See this webpage for the gory details:
> Here's my problem. Not only do I have to remove the two offending
> lines in the configure.in file, which I should be able to do with sed
> (haven't tested it yet though), or can I do this: "LDFLAGS-= -lz
> But I ran into another problem. Once I remove the lines from
> configure.in, I have to run "aclocal && autoheader && automake &&
> When I ran autoheader it failed. Using locate, I discovered that I
> have three different autoheaders:
> /usr/local/bin/autoheader213 /usr/local/bin/autoheader257
> I also have three different autoconfs:
> /usr/local/bin/autoconf213 /usr/local/bin/autoconf257
> How do I solve this problem?
> Paul Schmehl (pauls at utdallas.edu)
> Adjunct Information Security Officer
> The University of Texas at Dallas
> AVIEN Founding Member
I've attached a simple script I use when ever I change
the contents of a configure.in/configure.in Makefile.am etc.
in a port.
More information about the freebsd-ports