Pierre Labastie neuf.fr> writes:
>
> But I am worried about this new output for 32 bit build. Doesn't it mean
> we should have a symlink lib32->lib, as we have lib64->lib for 64 bit?
> How many packages do rely on having libs in lib32 rather than lib?
>
> Pierre
>
No lib32 folder was ever cre
Em 18-02-2014 12:22, Pierre Labastie escreveu:
> Le 18/02/2014 16:09, Fernando de Oliveira a écrit :
>> Em 18-02-2014 11:59, Fernando de Oliveira escreveu:
>>
>>> No /usr/local/lib32, but I am not sure if the dummy is run by jhalfs.
>> "dummy test"
>>
>>
> The "dummy test" is run in jhalfs (look at
On 02/18/2014 04:22 PM, Pierre Labastie wrote:
> Le 18/02/2014 16:09, Fernando de Oliveira a écrit :
>> Em 18-02-2014 11:59, Fernando de Oliveira escreveu:
>>
>>> No /usr/local/lib32, but I am not sure if the dummy is run by jhalfs.
>> "dummy test"
>>
>>
> The "dummy test" is run in jhalfs (look at
Le 18/02/2014 16:09, Fernando de Oliveira a écrit :
> Em 18-02-2014 11:59, Fernando de Oliveira escreveu:
>
>> No /usr/local/lib32, but I am not sure if the dummy is run by jhalfs.
> "dummy test"
>
>
The "dummy test" is run in jhalfs (look at the end of /jhalfs/logs/081-gcc).
Actually, from your pr
Em 18-02-2014 11:59, Fernando de Oliveira escreveu:
> No /usr/local/lib32, but I am not sure if the dummy is run by jhalfs.
"dummy test"
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information pa
Em 18-02-2014 11:44, Armin K. escreveu:
> On 02/18/2014 03:25 PM, Arthur Radley wrote:
>> Everything went smoothly. I only wanted to mention one new thing that
>> happened and one old thing.
>>
>> The new thing: In section 6.17. GCC-4.8.2 when verifying that the new linker
>> is being used with th
On 02/18/2014 03:25 PM, Arthur Radley wrote:
> Everything went smoothly. I only wanted to mention one new thing that
> happened and one old thing.
>
> The new thing: In section 6.17. GCC-4.8.2 when verifying that the new linker
> is being used with the correct search paths, the result had some ex
Everything went smoothly. I only wanted to mention one new thing that
happened and one old thing.
The new thing: In section 6.17. GCC-4.8.2 when verifying that the new linker
is being used with the correct search paths, the result had some extra lines
for /lib32 which I haven't seen before and wh
