On Fri, Mar 15, 2013 at 02:07:12AM +0800, Matthias Klose wrote:
> sorry, didn't comment about this patch because it didn't seem to affect
> multiarch. However this patch assumes that every system does have at least a
> */lib64 symlink, if it doesn't have a */lib64 directory. I think that is a
> w
Am 14.03.2013 16:37, schrieb Marcus Shawcroft:
> On 8 March 2013 09:32, Jakub Jelinek wrote:
>> On Fri, Mar 08, 2013 at 09:04:19AM +, Marcus Shawcroft wrote:
>>> On 07/03/13 16:45, Jakub Jelinek wrote:
On Thu, Mar 07, 2013 at 08:29:06AM -0800, Andrew Pinski wrote:
> On Thu, Mar 7, 201
On 8 March 2013 09:32, Jakub Jelinek wrote:
> On Fri, Mar 08, 2013 at 09:04:19AM +, Marcus Shawcroft wrote:
>> On 07/03/13 16:45, Jakub Jelinek wrote:
>> >On Thu, Mar 07, 2013 at 08:29:06AM -0800, Andrew Pinski wrote:
>> >>On Thu, Mar 7, 2013 at 3:15 AM, Jakub Jelinek wrote:
>> >>>AFAIK aarch
On Thu, Mar 7, 2013 at 8:45 AM, Jakub Jelinek wrote:
> On Thu, Mar 07, 2013 at 08:29:06AM -0800, Andrew Pinski wrote:
>> On Thu, Mar 7, 2013 at 3:15 AM, Jakub Jelinek wrote:
>> > AFAIK aarch64 libraries are supposed to go into /usr/lib64 etc.
>> > directories similarly to x86-64 etc., but as aarc
On Fri, Mar 08, 2013 at 09:04:19AM +, Marcus Shawcroft wrote:
> On 07/03/13 16:45, Jakub Jelinek wrote:
> >On Thu, Mar 07, 2013 at 08:29:06AM -0800, Andrew Pinski wrote:
> >>On Thu, Mar 7, 2013 at 3:15 AM, Jakub Jelinek wrote:
> >>>AFAIK aarch64 libraries are supposed to go into /usr/lib64 etc
On 07/03/13 16:45, Jakub Jelinek wrote:
On Thu, Mar 07, 2013 at 08:29:06AM -0800, Andrew Pinski wrote:
On Thu, Mar 7, 2013 at 3:15 AM, Jakub Jelinek wrote:
AFAIK aarch64 libraries are supposed to go into /usr/lib64 etc.
directories similarly to x86-64 etc., but as aarch64 isn't a true
multilib
On Thu, Mar 07, 2013 at 08:29:06AM -0800, Andrew Pinski wrote:
> On Thu, Mar 7, 2013 at 3:15 AM, Jakub Jelinek wrote:
> > AFAIK aarch64 libraries are supposed to go into /usr/lib64 etc.
> > directories similarly to x86-64 etc., but as aarch64 isn't a true
> > multilib target (having two different
On Thu, Mar 7, 2013 at 3:15 AM, Jakub Jelinek wrote:
> Hi!
>
> AFAIK aarch64 libraries are supposed to go into /usr/lib64 etc.
> directories similarly to x86-64 etc., but as aarch64 isn't a true
> multilib target (having two different backends for 32-bit vs. 64-bit code),
> currently gcc -print-mu
Hi!
AFAIK aarch64 libraries are supposed to go into /usr/lib64 etc.
directories similarly to x86-64 etc., but as aarch64 isn't a true
multilib target (having two different backends for 32-bit vs. 64-bit code),
currently gcc -print-multi-os-directory prints . instead of ../lib64.
The following pat
