On Mon, Sep 17, 2018 at 12:33:08AM +0200, Aurelien Jarno wrote:
>On 2018-09-16 02:38, Alexander Huynh wrote:
>> Hello all,
>>
>> I have a branch on Salsa [0] that would provide ordering for the two files I
>> currently see placed in /etc/ld.so.conf.d/:
>>
>> * libc.conf
>> * $(uname
On 2018-09-16 02:38, Alexander Huynh wrote:
> Hello all,
>
> I have a branch on Salsa [0] that would provide ordering for the two files I
> currently see placed in /etc/ld.so.conf.d/:
>
> * libc.conf
> * $(uname -m)-linux-gnu.conf
>
> I've also done a sweep of the rest of the repo, adding
Hello all,
I have a branch on Salsa [0] that would provide ordering for the two files I
currently see placed in /etc/ld.so.conf.d/:
* libc.conf
* $(uname -m)-linux-gnu.conf
I've also done a sweep of the rest of the repo, adding ordering to other files
that could appear in
We've hit this issue recently when building software packages for multiple
architectures.
I believe the general consensus is we should order things, but another
point to discuss is the specific ordering Debian should use.
IOhannes' example lists libc.conf earlier in the ordering, putting
Package: libc-bin
Version: 2.13-35
Severity: normal
Dear Maintainer,
i'm using debian as my primary development platform.
this means that i often build custom libraries, that are installed into
/usr/local/lib/
traditionally, /usr/local/lib/ will be searched before /usr/lib/, which is great
as
5 matches
Mail list logo
