Re: [Xen-devel] [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0

[Doug Goldstein <cardoe@xxxxxxxxxx>]

On 2/5/16 10:07 PM, Luis R. Rodriguez wrote:
> On Fri, Feb 05, 2016 at 10:52:01PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Feb 05, 2016 at 05:48:37PM -0800, Luis R. Rodriguez wrote:
>>> On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
>>> <mcgrof@xxxxxxxxxxxxxxxx> wrote:
>>>> From: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>
>>>>
>>>> Here's a slew of build fixes as well as build warning fixes
>>>> required when using the latest build tools, at least gcc 5 and
>>>> binutils 2.25.0.
>>>
>>> One good reason for some folks to get discouraged to work with Xen:
>>
>> s/Xen/Any Open Source project/
>>
>> Take a look in Documentation/SubmittingPatches, the " Don't get discouraged
>> - or impatient" section. It mentions 'pinging'.
> 
> I delays on pinging for new features, etc, things still being broken with
> compiling the latest and greatest however is not.
> 
>>> Patches for fixes on builds last ages to get merged
>>>
>>> In this case Mark Pryor <pryorm09@xxxxxxxxx> reported an issue and
>>> offered a fix on October 8, 2015 [0]. That did not go in as Jan noted
>>> it was probably not the right fix. Last year in November I provided
>>> what I think is a proper replacement set which I think addressed Jan's
>>> concerns.
>>>
>>> ***Four*** months later and Xen still does not compile with the latest
>>> and greatest. I have to go digging out in my git basement somewhere
>>> some fixes I last used to build Xen to try to test some new
>>> features...
>>
>> Odd it does compile for me - albeit I've had issues with the VNC
>> part which also needs another patch.
> 
> Is there an auto build test going on with different distros going ?
> If not that might help.

Trying to make that happen here:
http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg00984.html

Currently its only on Ubuntu 14.04 but with a few different compilers.
I've got follow on work that adds CentOS and will show others how they
can easily add more.


> 
>> But I hadn't had the chance to
>> see whether the patch would break builds on much older version of
>> distros.
> 
> A static inline to define the new method in the old way of doing
> things should suffice as well I think.
> 
>>> What's up folks? How can this process be made smoother, did I do
>>> something wrong, what can I do to help better? What can you do to help
>>> ensure these types of things don't fall through the cracks.
>>
>> ping? The same thing you would do on LKML.
> 
> 0 day build tests the kernel all the time, even if my patch gets
> missed, after a few days other will immediately notice. These days
> its extremely hard for me to build linux-next and have a build
> issue.
> 
> I recommend we push on the momentum to see if we can piggy back
> on doing regular 0 day build tests with Xen too if possible.
> 
>    Luis

Got links to where this is run? I'm assuming its using Autotest [1]?

[1] https://autotest.github.io/

-- 
Doug Goldstein

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel