[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/6] tools/include: adjustments to the population of xen/


  • To: Jan Beulich <jbeulich@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Thu, 10 Sep 2020 14:51:43 +0100
  • Authentication-results: esa3.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none
  • Cc: Ian Jackson <iwj@xxxxxxxxxxxxxx>, Wei Liu <wl@xxxxxxx>
  • Delivery-date: Thu, 10 Sep 2020 13:51:51 +0000
  • Ironport-sdr: 4GyIGLCF4JhovU3x5A2/xZLTMC8bxHJNsb+lRoxTzSJXX+qpw6TFGpXSwFNtjCIrQMTBvDxFJb osZJcVsC3Z+mlmEJ0UIDRzCAu0LnJ9sZDiPZgsovA5asF/Q36F3acLFYDs6drNU4rvJy0tZ2oE R6zjnpoDKgkOVNliCaTQbozTGjKbmwRUZUzp1/c4TJa6q+6Bxd8YjdYmkxDXIdjyBhoW1FuHH0 v+ViIC9lKIjRGwt2KGc/LqyICUi8QiYIwJwv2Mn/Gi3L2pQPmLNW3rJ4/xDq+uID7taJvABdK+ qbk=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 10/09/2020 13:09, Jan Beulich wrote:
> While looking at what it would take to move around libelf/
> in the hypervisor subtree, I've run into this rule, which I
> think can do with a few improvements and some simplification.

I realise this might be a controversial move, but can we *please*
address this by removing our use of symlinking, rather than kicking the
problem down the road.

For header files in particular, there is no need to symlink at all. 
Some properly formed -I runes for the compiler will do the right thing,
and avoid all intermediate regeneration issues.

~Andrew



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.