On 22/08/17 09:57, Christian Seiler wrote:
> Not programs, but packages, yes. Not all library packages in Debian
> have been updated to use the Multi-Arch scheme yet (in some cases
> other aspects of the package may make this difficult, even if it
> is easy to put the .so file into the new location
Thanks everybody for the explanation (note that I did not make the
original question). I had been wondering about why some of my “.so” were
in “/usr/lib/x86_64-linux-gnu” instead of just “/usr/lib”.
What about the ELF shared objects that *are* under “/usr/lib”? Are these
programs that do not have
Am 2017-08-22 16:47, schrieb Mario Castelán Castro:
What about the ELF shared objects that *are* under “/usr/lib”? Are
these
programs that do not have support for multi-arch?
Not programs, but packages, yes. Not all library packages in Debian
have been updated to use the Multi-Arch scheme yet
On 08/21/2017 09:12 PM, Dutch Ingraham wrote:
> For example, Fedora (and Gentoo,
> etc. )
> also installs glibc for both 32- and 64-bit on the same machine, but
> they have not
> relocated these header files. So are you saying this was just Debian's
> method
> of solving the multi-arch issue, and
On Mon, Aug 21, 2017 at 09:55:18PM +0200, to...@tuxteam.de wrote:
> On Mon, Aug 21, 2017 at 02:12:05PM -0500, Dutch Ingraham wrote:
> > On 08/21/2017 09:06 AM, Kushal Kumaran wrote:
> > > Dutch Ingraham writes:
> > >
> > >> Hi everyone -
> > >>
> > >> It seems Debian has moved some header director
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 21, 2017 at 02:12:05PM -0500, Dutch Ingraham wrote:
> On 08/21/2017 09:06 AM, Kushal Kumaran wrote:
> > Dutch Ingraham writes:
> >
> >> Hi everyone -
> >>
> >> It seems Debian has moved some header directories, like /usr/include/bits
> >>
On 08/21/2017 09:06 AM, Kushal Kumaran wrote:
> Dutch Ingraham writes:
>
>> Hi everyone -
>>
>> It seems Debian has moved some header directories, like /usr/include/bits
>> (and
>> sys, and asm, etc.) from /usr/include/ to, e.g.,
>> /usr/include/i386-linux-gnu/bits/
>> (arch-specific).
>>
>> My
On 08/21/2017 09:02 AM, to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, Aug 21, 2017 at 08:37:14AM -0500, Dutch Ingraham wrote:
>> Hi everyone -
>>
>> It seems Debian has moved some header directories, like /usr/include/bits
>> (and
>> sys, and asm, etc.) from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 21, 2017 at 07:06:17AM -0700, Kushal Kumaran wrote:
[...]
> There are several directories configured for searching header files.
> The command "gcc -xc -E -v - < /dev/null" will print those paths out.
HAH. Thanks. That's what was missing
Dutch Ingraham writes:
> Hi everyone -
>
> It seems Debian has moved some header directories, like /usr/include/bits (and
> sys, and asm, etc.) from /usr/include/ to, e.g.,
> /usr/include/i386-linux-gnu/bits/
> (arch-specific).
>
> My first question is: Why?
>
This is so that headers that are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 21, 2017 at 08:37:14AM -0500, Dutch Ingraham wrote:
> Hi everyone -
>
> It seems Debian has moved some header directories, like /usr/include/bits (and
> sys, and asm, etc.) from /usr/include/ to, e.g.,
> /usr/include/i386-linux-gnu/bits/
Hi everyone -
It seems Debian has moved some header directories, like /usr/include/bits (and
sys, and asm, etc.) from /usr/include/ to, e.g.,
/usr/include/i386-linux-gnu/bits/
(arch-specific).
My first question is: Why?
My second question is: How does this work? There are no symlinks, yet a f
12 matches
Mail list logo
