Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Sorry, I got stuck in Android-land for a while, but this does not fix the build on a fresh build box with python 3.4 as default system python. Switching to python 2.7 does build u-boot successfully. Note this is with u-boot v2017.05 (which does have --force in setup.py) and DE1 SoC config, which

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

On 5 April 2017 at 12:11, Simon Glass wrote: > Hi Stefan, > > On 5 April 2017 at 12:08, Stefan Agner wrote: >> On 2017-03-31 21:23, Simon Glass wrote: >>> On 29 March 2017 at 13:41, Stefan Agner wrote: From: Stefan Agner

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Hi Stefan, On 5 April 2017 at 12:08, Stefan Agner wrote: > On 2017-03-31 21:23, Simon Glass wrote: >> On 29 March 2017 at 13:41, Stefan Agner wrote: >>> From: Stefan Agner >>> >>> For some reason Python 3 seems to think it does not

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

On 2017-03-31 21:23, Simon Glass wrote: > On 29 March 2017 at 13:41, Stefan Agner wrote: >> From: Stefan Agner >> >> For some reason Python 3 seems to think it does not need to build >> the library. Using the --force parameter makes sure that the

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

On 2017-04-05 10:26, Stefano Babic wrote: > Hi Stefan, > > On 04/04/2017 20:44, Stefan Agner wrote: >> On 2017-04-04 01:53, Stefano Babic wrote: >>> Hi Stefan, >>> >>> On 03/04/2017 23:02, Stefan Agner wrote: >>> But then, I don't expect that "/usr/bin/env python" is looking at PYTHON.

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Hi Stefan, On 04/04/2017 20:44, Stefan Agner wrote: > On 2017-04-04 01:53, Stefano Babic wrote: >> Hi Stefan, >> >> On 03/04/2017 23:02, Stefan Agner wrote: >> >>> But then, I don't expect that "/usr/bin/env python" is looking at >>> PYTHON. >>> >>> As far as I understand env, it just looks up

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

On 2017-04-04 01:53, Stefano Babic wrote: > Hi Stefan, > > On 03/04/2017 23:02, Stefan Agner wrote: > >> But then, I don't expect that "/usr/bin/env python" is looking at >> PYTHON. >> >> As far as I understand env, it just looks up the current environment to >> run its COMMAND argument. > >

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Hi Stefan, On 03/04/2017 23:02, Stefan Agner wrote: > But then, I don't expect that "/usr/bin/env python" is looking at > PYTHON. > > As far as I understand env, it just looks up the current environment to > run its COMMAND argument. Agree, this is also mz understanding. > It is helpful as a

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

On 2017-04-03 10:35, Stefano Babic wrote: > Hi Stefan, > > On 03/04/2017 18:41, Stefan Agner wrote: >> Hi Stefano, >> >> On 2017-04-03 03:30, Stefano Babic wrote: >>> Hi Stefan, >>> >>> On 29/03/2017 21:41, Stefan Agner wrote: From: Stefan Agner For some

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Hi Stefan, On 03/04/2017 18:41, Stefan Agner wrote: > Hi Stefano, > > On 2017-04-03 03:30, Stefano Babic wrote: >> Hi Stefan, >> >> On 29/03/2017 21:41, Stefan Agner wrote: >>> From: Stefan Agner >>> >>> For some reason Python 3 seems to think it does not need to build

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Hi Stefano, On 2017-04-03 03:30, Stefano Babic wrote: > Hi Stefan, > > On 29/03/2017 21:41, Stefan Agner wrote: >> From: Stefan Agner >> >> For some reason Python 3 seems to think it does not need to build >> the library. Using the --force parameter makes sure that the

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

Hi Stefan, On 29/03/2017 21:41, Stefan Agner wrote: > From: Stefan Agner > > For some reason Python 3 seems to think it does not need to build > the library. Using the --force parameter makes sure that the library > gets built always. This is especially important since

Re: [U-Boot] [PATCH] libfdt: fix build with Python 3

On 29 March 2017 at 13:41, Stefan Agner wrote: > From: Stefan Agner > > For some reason Python 3 seems to think it does not need to build > the library. Using the --force parameter makes sure that the library > gets built always. This is especially

[U-Boot] [PATCH] libfdt: fix build with Python 3

From: Stefan Agner For some reason Python 3 seems to think it does not need to build the library. Using the --force parameter makes sure that the library gets built always. This is especially important since we move the library in the next step of the Makefile, hence