On Wed, Feb 18, 2004 at 06:33:37PM -0800, DK Smith wrote:
> Has anyone successfully used "--enable-static" ?
> I have not been able to determine the appropriate syntax.
>
> I have tried these three ways:
>
> --enable-static
Try "--disable-shared". The options say whether to *build* the
static o
PROTECTED]
Twiki: http://twiki.wrs.com/do/view/Main/JasonBrooks
Senior Systems Administration Analyst
Wind River Systems
8905 SW Nimbus ~ Suite 255
Beaverton, Or 97008
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of DK Smith
Sent: Wednesday, Febru
Has anyone successfully used "--enable-static" ?
I have not been able to determine the appropriate syntax.
I have tried these three ways:
--enable-static
--enable-static="yes"
--enable-static="list of individual package names such as amcheck"
Cheers,
DK
sometimes I do not see the forest for the trees...
I looked briefly at the line above that one... ugh
--enable-shared=PKGSbuild shared libraries default=yes
thanks!
I hope you are well!
Don't know for sure, but --enable-static sounds like a winner.
On Wed, Feb 18, 2004 at 02:30:05PM -0800, DK Smith wrote:
> Hello all,
>
> I was experimenting with a different installation strategy... That is,
> in order to not install amanda on every host... I am attempting to
> place a single amanda installation on a file server; making it
> available via
DK Smith wrote:
I was experimenting with a different installation strategy... That is,
in order to not install amanda on every host... I am attempting to place
a single amanda installation on a file server; making it available via
an NFS share. The nfs-clients of the same architecture (in this c
Hello all,
I was experimenting with a different installation strategy... That is,
in order to not install amanda on every host... I am attempting to
place a single amanda installation on a file server; making it
available via an NFS share. The nfs-clients of the same architecture
(in this case
