Re: waf and Python 3.7

>> First of all: I tried a pdf build. But I receive the same error >> on a html build. > > I do not see this error. > >> See attached log for the complete output with python2 >> on the current HEAD (75f24638b3f). > > I cannot see what is wrong. There is a waf configure option to add verbose > le

Re: waf and Python 3.7

On 19/12/2018 21:36, Christian Mauderer wrote: > > Libbsd is updated. For some reason the ticket in Track hasn't picked up > the change. Did I make some error in the description? > > https://git.rtems.org/rtems-libbsd/commit/?id=91566dda7f52b5eba04df159770b4797ba652f20 > Looks fine. Please crea

Re: waf and Python 3.7

Am 19.12.18 um 10:46 schrieb Chris Johns: > On 19/12/18 8:20 pm, Christian Mauderer wrote: >> I think you are discussing some other bug(s) than the one I originally >> meant. > > Yes we are discussing something else that is wrong with the docs builds. Sorry > about hijacking the thread. > No pr

Re: waf and Python 3.7

On 19/12/18 8:20 pm, Christian Mauderer wrote: > I think you are discussing some other bug(s) than the one I originally > meant. Yes we are discussing something else that is wrong with the docs builds. Sorry about hijacking the thread. > First of all: I tried a pdf build. But I receive the same

Re: waf and Python 3.7

Am 19.12.18 um 06:20 schrieb Chris Johns: > On 19/12/2018 14:10, Joel Sherrill wrote: >> On Tue, Dec 18, 2018, 7:31 PM Chris Johns > wrote: >> On 19/12/2018 11:49, Joel Sherrill wrote: >> > On Tue, Dec 18, 2018 at 5:33 PM Chris Johns >

Re: waf and Python 3.7

On 19/12/2018 14:10, Joel Sherrill wrote: > On Tue, Dec 18, 2018, 7:31 PM Chris Johns wrote: > On 19/12/2018 11:49, Joel Sherrill wrote: > > On Tue, Dec 18, 2018 at 5:33 PM Chris Johns > >

Re: waf and Python 3.7

On Tue, Dec 18, 2018, 7:31 PM Chris Johns On 19/12/2018 11:49, Joel Sherrill wrote: > > On Tue, Dec 18, 2018 at 5:33 PM Chris Johns > > wrote: > > On 19/12/2018 06:12, Christian Mauderer wrote: > > > I updated waf in rtems-tools with a reference to the ticket. I'm

Re: waf and Python 3.7

On 19/12/2018 11:49, Joel Sherrill wrote: > On Tue, Dec 18, 2018 at 5:33 PM Chris Johns > wrote: > On 19/12/2018 06:12, Christian Mauderer wrote: > > I updated waf in rtems-tools with a reference to the ticket. I'm still a > > little unsure about our tickets: S

Re: waf and Python 3.7

On Tue, Dec 18, 2018 at 5:33 PM Chris Johns wrote: > On 19/12/2018 06:12, Christian Mauderer wrote: > > I updated waf in rtems-tools with a reference to the ticket. I'm still a > > little unsure about our tickets: Should I create separate tickets for > > that problem in rtems-docs, rtems-libbsd (

Re: waf and Python 3.7

On 19/12/2018 06:12, Christian Mauderer wrote: > I updated waf in rtems-tools with a reference to the ticket. I'm still a > little unsure about our tickets: Should I create separate tickets for > that problem in rtems-docs, rtems-libbsd (both have the same problem) > and examples-v2 (I haven't test

Re: waf and Python 3.7

Am 17.12.18 um 22:32 schrieb Chris Johns: > On 18/12/2018 07:38, Joel Sherrill wrote: >> On Mon, Dec 17, 2018, 2:21 PM Christian Mauderer > wrote: >> >> Hello, >> >> I have trouble building rtems-tools (via source builder) on an >> Arch-Linux machine with a P

Re: waf and Python 3.7

On 18/12/2018 07:38, Joel Sherrill wrote: > On Mon, Dec 17, 2018, 2:21 PM Christian Mauderer wrote: > > Hello, > > I have trouble building rtems-tools (via source builder) on an > Arch-Linux machine with a Python 3.7. I searched for the problem and > f

Re: waf and Python 3.7

On Mon, Dec 17, 2018, 2:21 PM Christian Mauderer Hello, > > I have trouble building rtems-tools (via source builder) on an > Arch-Linux machine with a Python 3.7. I searched for the problem and > found out that it is due to an old waf version in the rtems-tools repo. > The bug is fixed since 9 mon

waf and Python 3.7

Hello, I have trouble building rtems-tools (via source builder) on an Arch-Linux machine with a Python 3.7. I searched for the problem and found out that it is due to an old waf version in the rtems-tools repo. The bug is fixed since 9 months and newer versions of waf don't have a problem with it