KAYVEN RIESE wrote:
On Tue, 22 May 2007, Andrew Lankford wrote:
After reading the most recent /usr/ports/UPDATING and deciding to go
ahead and upgrade to X 7.2, I'm wondering where the script
"xorg-upgrade" is and why it wasn't simply added to the ports tree.
If it's there, I sure as heck ca
On Tue, 22 May 2007, Brooks Davis wrote:
On Tue, May 22, 2007 at 09:46:47PM -0400, Andrew Lankford wrote:
After reading the most recent /usr/ports/UPDATING and deciding to go ahead
and upgrade to X 7.2, I'm wondering where the script "xorg-upgrade" is and
why it wasn't simply added to the po
On Tue, May 22, 2007 at 09:46:47PM -0400, Andrew Lankford wrote:
> After reading the most recent /usr/ports/UPDATING and deciding to go ahead
> and upgrade to X 7.2, I'm wondering where the script "xorg-upgrade" is and
> why it wasn't simply added to the ports tree. If it's there, I sure as h
On Tue, 22 May 2007, Andrew Lankford wrote:
After reading the most recent /usr/ports/UPDATING and deciding to go ahead
and upgrade to X 7.2, I'm wondering where the script "xorg-upgrade" is and
why it wasn't simply added to the ports tree. If it's there, I sure as heck
can't find it.
call m
On Tue, 22 May 2007 21:46:47 -0400
Andrew Lankford <[EMAIL PROTECTED]> wrote:
> After reading the most recent /usr/ports/UPDATING and deciding to go
> ahead and upgrade to X 7.2, I'm wondering where the script
> "xorg-upgrade" is and why it wasn't simply added to the ports tree.
> If it's there,
After reading the most recent /usr/ports/UPDATING and deciding to go
ahead and upgrade to X 7.2, I'm wondering where the script
"xorg-upgrade" is and why it wasn't simply added to the ports tree. If
it's there, I sure as heck can't find it.
Andrew Lankford
Hi;
I thought this would be a simple question but it looks like I was mistaken ;)
A couple of people kindly responded, but I'm at a loss as to how they meant to
address my question ;)
Would someone kindly simply edit the following, if that's possible (if I'm not
too far off how it
Robert Huff wrote:
> As I understand it, the FreeBSD-supplied defaults for this type
> of variable are set in /etc/defaults/make.conf (which should never
> be edited),
There is no /etc/defaults/make.conf any more -- it was moved to
/usr/share/examples/etc in the 5.x series of releases.
Eve
Rachel Florentine writes:
>MAKE_ENV = {
> '/usr/ports/net/openldap23-server' => [
> 'CC=gcc',
> 'CPPFLAGS="-I/usr/local/include/openssl/"'
> 'LDFLAGS="-L/usr/local/lib/"'
As I understand it, the FreeBSD-supplied defaults for this type
of variable are set in /etc/d
- Original Message
From: Robert Huff <[EMAIL PROTECTED]>
> Rachel Florentine writes:
>> Can someone please tell me how to add options to a port build?
>> For example, I want to rebuild my openldap with something like
>> this:
>
>Start here:
>
>man make.conf
>man pkgtools.
Rachel Florentine writes:
> Can someone please tell me how to add options to a port build?
> For example, I want to rebuild my openldap with something like
> this:
Start here:
man make.conf
man pkgtools.conf
Robert Huff
_
Hi;
Can someone please tell me how to add options to a port build? For example, I
want to rebuild my openldap with something like this:
env \
CC=gcc CPPFLAGS="-I/usr/local/include/openssl/" \
LDFLAGS="-L/usr/local/lib/" \
./configure \
--localstatedir=/var/run/slapd \
--enable-spasswd \
12 matches
Mail list logo
