> On 12 May 2020, at 11:07, Andreas Schultz <andreas.schu...@travelping.com> 
> wrote:
> 
> 
> 
> Am Di., 12. Mai 2020 um 10:42 Uhr schrieb Damjan Marion <dmar...@me.com 
> <mailto:dmar...@me.com>>:
> 
> 
>> On 12 May 2020, at 10:10, Andreas Schultz <andreas.schu...@travelping.com 
>> <mailto:andreas.schu...@travelping.com>> wrote:
>> 
>> 
>> 
>> Am Di., 12. Mai 2020 um 10:00 Uhr schrieb Damjan Marion via lists.fd.io 
>> <http://lists.fd.io/> <dmarion=me....@lists.fd.io 
>> <mailto:me....@lists.fd.io>>:
>> 
>> 
>> 
>> > On 12 May 2020, at 03:40, Lijian Zhang <lijian.zh...@arm.com 
>> > <mailto:lijian.zh...@arm.com>> wrote:
>> > 
>> > 
>> >> -----Original Message-----
>> >> From: Damjan Marion <dmar...@me.com <mailto:dmar...@me.com>>
>> >> Sent: 2020年5月12日 0:46
>> >> To: Lijian Zhang <lijian.zh...@arm.com <mailto:lijian.zh...@arm.com>>
>> >> Cc: vpp-dev <vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>>; nd 
>> >> <n...@arm.com <mailto:n...@arm.com>>
>> >> Subject: Re: [vpp-dev] clang-9
>> >> 
>> >> 
>> >> Hi Lijian,
>> >> 
>> >> If I got it right, neither gcc or clang available in ubuntu 18.04 LTS are 
>> >> able to
>> >> produce N1 optimised binaries. correct?
>> > Yes, that's right. Support for optimized compiling for N1 starts with 
>> > gcc-9.2.0 and clang-10, which are not available in Ubuntu-18.04 yet.
>> >> 
>> >> If yes, can we just add clang-10 from: https://apt.llvm.org 
>> >> <https://apt.llvm.org/> to vpp build scripts?
>> >> 
>> > Currently clang-10/clang-11 Aarch64 packages are not available at 
>> > apt.llvm.org <http://apt.llvm.org/> yet. Arm compiler team is working on 
>> > getting AArch64 packages available at apt.llvm.org <http://apt.llvm.org/>. 
>> > It may take a couple of weeks.
>> 
>> So let’s wait then. For people who wants to use N1 probably there is more 
>> sense in
>> using ubuntu 20.04 anyway, and 20.04 is coming with clang10.
>> 
>> Yeah, but Ubuntu 20.04 and Debian Sid are in the process of removing python2 
>> support and that creates a whole bunch of other problems. Removing the 
>> python2 deb references from `make install-dep` is relatively simple, but 
>> cleaning up the debian rules and control files without breaking support for 
>> older Ubuntu and Debian releases is more complicated.
> 
> Can you explain what exactly is more complicated?
> 
> Debian Sid has completely removed python2, but the debs still depend on them. 
> Making this more flexible requires some creative changes to the rules files.
> We have worked around that [1],[2] by removing the python2 dependencies, but 
> that would probably break builds on older Debian/Ubuntu versions.
> 
> [1]: 
> https://github.com/travelping/vpp/commit/77acccae792180f0ae94058a3b1ca7db0f995dd0
>  
> <https://github.com/travelping/vpp/commit/77acccae792180f0ae94058a3b1ca7db0f995dd0>
>   
> [2]: 
> https://github.com/travelping/vpp/commit/7d52fd387b4c8a3a2f33c27f031b283d260301f2
>  
> <https://github.com/travelping/vpp/commit/7d52fd387b4c8a3a2f33c27f031b283d260301f2>—
>  

something like:

https://gerrit.fd.io/r/c/vpp/+/27010

Changes in ./Makefile probably require a bit of brain police form somebody 
fluent in python….



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16325): https://lists.fd.io/g/vpp-dev/message/16325
Mute This Topic: https://lists.fd.io/mt/73327785/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to