On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
Hi Julian!
The problem I have is that I have a library with same host architecture
but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Hi Julian!
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Build-Depends: libc-arm-version (=2.1) [arm]
See policy section 7.1 for details.
I
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
Hi Julian!
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Hi!
Can I put a different Build-Depends for each binary package in a control
file or can there only be a Build-Depends for the source package?
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
dietlibc-dev
On Tue, Jun 19, 2001 at 11:50:52AM +0200, Abraham vd Merwe wrote:
Hi!
Can I put a different Build-Depends for each binary package in a control
file or can there only be a Build-Depends for the source package?
You can only have one Build-Depends in the control file for the source
package.
Hi Julian!
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Build-Depends: libc-arm-version (=2.1) [arm]
See policy section 7.1 for details.
I
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
Hi Julian!
The problem I have is that I have a library with same host architecture
but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
7 matches
Mail list logo