On Wed, Jan 30, 2002 at 03:37:58PM -0700, Jeremy Wadsack wrote:
>
> KEVIN ZEMBOWER ([EMAIL PROTECTED]):
>
> > One of the things which was disquieting to me while trying to
> > troubleshoot my problems with TCP and UDP ports was the inability to
> > check what options I had compiled with using "a
On Wed, Jan 30, 2002 at 03:37:58PM -0700, Jeremy Wadsack wrote:
>
> KEVIN ZEMBOWER ([EMAIL PROTECTED]):
>
> > One of the things which was disquieting to me while trying to
> > troubleshoot my problems with TCP and UDP ports was the inability to
> > check what options I had compiled with using "a
>Well, each args that went into ./configure has some effect on the
>code. So the code that it affects can add the appropriate arg to a
>common string.
That's hundreds of entries and a maintenance nightmare. No thanks :-).
>I honestly know nothing about autoconf, but I do know that the PHP
>inst
John R. Jackson ([EMAIL PROTECTED]):
>>How about an amadmin command like 'configure-options' that allows you
>>to do something like this when upgrading:
>>
>> ./configure `amadmin configure-options`
> That would be almost impossible. Amanda does not have that much control
> over ./configure.
>How about an amadmin command like 'configure-options' that allows you
>to do something like this when upgrading:
>
> ./configure `amadmin configure-options`
That would be almost impossible. Amanda does not have that much control
over ./configure. You would need to know all the args that went
KEVIN ZEMBOWER ([EMAIL PROTECTED]):
> One of the things which was disquieting to me while trying to
> troubleshoot my problems with TCP and UDP ports was the inability to
> check what options I had compiled with using "amadmin version".
> I've pasted in the results of my system at the end of th
