On Sat, 2017-11-25 at 11:36:27 +0100, Ole Streicher wrote:
> Guillem Jover writes:
> > The point is that the Multi-Arch concept in Debian is all about the
> > interfaces. How packages and files interface with each other, and
> > what is possible and allowed. Some examples:
> >
> > * A script mig
Guillem Jover writes:
> The point is that the Multi-Arch concept in Debian is all about the
> interfaces. How packages and files interface with each other, and
> what is possible and allowed. Some examples:
>
> * A script might be arch-independent in the contents sense; i.e., it
> is the sam
Hi!
On Fri, 2017-11-24 at 13:59:40 +0100, Ole Streicher wrote:
> Guillem Jover writes:
> > On Fri, 2017-11-24 at 09:52:23 +0100, Ole Streicher wrote:
> >> So, how can I canonically (ideally from C) retrieve a sorted list of
> >> supported multi arch paths at runtime? Or is there another good way
Hi Guillem,
thanks for the quick answer.
Guillem Jover writes:
> On Fri, 2017-11-24 at 09:52:23 +0100, Ole Streicher wrote:
>> /usr/lib/${DEB_TARGET_MULTIARCH}/iraf
>
> It that was to be used, then it should be DEB_HOST_MULTIARCH, the
> _TARGET_ variants are for canadian cross-compilers. :) If t
Hi!
On Fri, 2017-11-24 at 09:52:23 +0100, Ole Streicher wrote:
> I want to package a software, "iraf" (with extensions) that uses some
> system dependent binaries internally. Some of the extensions will be
> available in 32 bit only, so this is a good use case for
> Multi-Arch. That means, that th
Hi,
I want to package a software, "iraf" (with extensions) that uses some
system dependent binaries internally. Some of the extensions will be
available in 32 bit only, so this is a good use case for
Multi-Arch. That means, that the binaries will go to
/usr/lib/${DEB_TARGET_MULTIARCH}/iraf
At ru
6 matches
Mail list logo
