On Sun, Apr 22, 2001 at 07:35:01PM -0400, Bob Hilliard wrote:
> It appears to me that the method recommended in policy section
> 11.1 to support DEB_BUILD_OPTIONS in the rules file requires the
> DEB_BUILD_OPTIONS variable to contain both `debug' and `nostrip' in
> order to generate a package
On Sun, Apr 22, 2001 at 07:35:01PM -0400, Bob Hilliard wrote:
> It appears to me that the method recommended in policy section
> 11.1 to support DEB_BUILD_OPTIONS in the rules file requires the
> DEB_BUILD_OPTIONS variable to contain both `debug' and `nostrip' in
> order to generate a package
On Sun, Apr 22, 2001 at 07:35:01PM -0400, Bob Hilliard wrote:
> It appears to me that the method recommended in policy section
> 11.1 to support DEB_BUILD_OPTIONS in the rules file requires the
> DEB_BUILD_OPTIONS variable to contain both `debug' and `nostrip' in
> order to generate a package
It appears to me that the method recommended in policy section
11.1 to support DEB_BUILD_OPTIONS in the rules file requires the
DEB_BUILD_OPTIONS variable to contain both `debug' and `nostrip' in
order to generate a package with debugging information included.
Is this correct and is this
On Sun, Apr 22, 2001 at 07:35:01PM -0400, Bob Hilliard wrote:
> It appears to me that the method recommended in policy section
> 11.1 to support DEB_BUILD_OPTIONS in the rules file requires the
> DEB_BUILD_OPTIONS variable to contain both `debug' and `nostrip' in
> order to generate a package
It appears to me that the method recommended in policy section
11.1 to support DEB_BUILD_OPTIONS in the rules file requires the
DEB_BUILD_OPTIONS variable to contain both `debug' and `nostrip' in
order to generate a package with debugging information included.
Is this correct and is thi
6 matches
Mail list logo