discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] status of trunk on NetBSD (distcheck ~works), BSD


From: Greg Troxel
Subject: Re: [Discuss-gnuradio] status of trunk on NetBSD (distcheck ~works), BSD make (almost)
Date: Mon, 21 Aug 2006 10:28:57 -0400
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (berkeley-unix)

  Thanks for testing. I should have mentioned the revision number (r3357)
  that had the fixes; you were trying r3356 yesterday.

I had started that build before the last fix, and I had spare cpu
cycles anyway.

  It seems we need a way to automatically determine when LDFLAGS and
  CPPFLAGS need to be initialized to the values you listed.  I wouldn't
  want to require a --with argument to configure for anyone's default
  configuration, which yours seems to be.

NetBSD's approach is that even pkgsrc and other things are not in the
default paths, which is a bias towards controlled builds rather than
convenience.  Putting a --with-prereqs=/usr/pkg on the configure
command line to add the include path to CPPFLAGS and -L/-R to LDFLAGS
would seem fine to me.

But, people compiling typically have /usr/pkg/bin in their path, so
programs that configure via foo-config or pkg-config are found.
pkg-config is from pkgsrc, not the base system, so it searches
/usr/pkg/lib/pkgconfig.  So the controlled build part is only
partially true for builds by normal users who haven't cleaned their
environments.

But, having it default to /usr/pkg so the configure script notices
/usr/pkg and adds it in would be ok too, on systems with /usr/pkg present.

-- 
    Greg Troxel <address@hidden>

Attachment: pgpFGewkLPTa1.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]