On 2018年06月15日 14:54, Alexander Kanavin wrote:
Thanks! Mingli, can you try this please?
Sure,
Alex
2018-06-15 9:44 GMT+03:00 Khem Raj :
On 6/1/18 12:34 PM, Alexander Kanavin wrote:
On 06/01/2018 09:33 PM, Khem Raj wrote:
The .s file is not generated and it does not contain any
Thanks! Mingli, can you try this please?
Alex
2018-06-15 9:44 GMT+03:00 Khem Raj :
>
>
> On 6/1/18 12:34 PM, Alexander Kanavin wrote:
>>
>> On 06/01/2018 09:33 PM, Khem Raj wrote:
The .s file is not generated and it does not contain any .file
directives. The .o file also does not
On 6/1/18 12:34 PM, Alexander Kanavin wrote:
On 06/01/2018 09:33 PM, Khem Raj wrote:
The .s file is not generated and it does not contain any .file
directives. The .o file also does not contain the path. It appears in
the final .so library at linking stage.
Can you share the linker cmdline
On 2018年06月01日 16:36, Alexander Kanavin wrote:
2018-06-01 8:38 GMT+03:00 Yu, Mingli :
I did investigate the path a lot before send out the patch, but didn't
figure out why it introduce the path for make_x86_64_sysv_elf_gas.o whose
source file is make_x86_64_sysv_elf_gas.S.
Anyway, I will
On 06/01/2018 09:33 PM, Khem Raj wrote:
The .s file is not generated and it does not contain any .file
directives. The .o file also does not contain the path. It appears in
the final .so library at linking stage.
Can you share the linker cmdline ?
https://pastebin.com/WK9GVDfj
Note that of
On 6/1/18 10:56 AM, Alexander Kanavin wrote:
> 2018-06-01 20:07 GMT+03:00 Khem Raj :
>> these symbols are added by assembler, if you have .file asm directive
>> either explicitly added to .s file or emitted by compiler, compiler
>> would emit it if the path specified to source file is absolute
2018-06-01 20:07 GMT+03:00 Khem Raj :
> these symbols are added by assembler, if you have .file asm directive
> either explicitly added to .s file or emitted by compiler, compiler
> would emit it if the path specified to source file is absolute during
> compiler invocation, it will take it
On 5/31/18 10:38 PM, Yu, Mingli wrote:
>
>
> On 2018年06月01日 13:08, Alexander Kanavin wrote:
>> 2018-06-01 4:39 GMT+03:00 Yu, Mingli :
>>
This looks very unlikely to ever make it upstream. Rather than carrying
a patch to boost forever would we want to just strip the file in
2018-06-01 8:38 GMT+03:00 Yu, Mingli :
> I did investigate the path a lot before send out the patch, but didn't
> figure out why it introduce the path for make_x86_64_sysv_elf_gas.o whose
> source file is make_x86_64_sysv_elf_gas.S.
>
> Anyway, I will try to dig more.
>
> If you have any ideas,
On 2018年06月01日 13:08, Alexander Kanavin wrote:
2018-06-01 4:39 GMT+03:00 Yu, Mingli :
This looks very unlikely to ever make it upstream. Rather than carrying
a patch to boost forever would we want to just strip the file in
question with a custom command?
Thanks very much Richard for your
2018-06-01 4:39 GMT+03:00 Yu, Mingli :
>> This looks very unlikely to ever make it upstream. Rather than carrying
>> a patch to boost forever would we want to just strip the file in
>> question with a custom command?
>
>
> Thanks very much Richard for your respond!
> I did try to strip only file
On 2018年05月31日 21:13, Richard Purdie wrote:
On Wed, 2018-05-30 at 23:20 -0700, mingli...@windriver.com wrote:
From: Mingli Yu
boost_context includes some assembly source
files and will export the assembly object file
make_x86_64_sysv_elf_gas.o which contains host
path as below:
$ readelf
On Wed, 2018-05-30 at 23:20 -0700, mingli...@windriver.com wrote:
> From: Mingli Yu
>
> boost_context includes some assembly source
> files and will export the assembly object file
> make_x86_64_sysv_elf_gas.o which contains host
> path as below:
> $ readelf --wide --symbols
From: Mingli Yu
boost_context includes some assembly source
files and will export the assembly object file
make_x86_64_sysv_elf_gas.o which contains host
path as below:
$ readelf --wide --symbols
14 matches
Mail list logo
