mingw-cross-env-list
[Top][All Lists]
Advanced

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

Trying to understand a build failure for package pair aubio/waf


From: Filippo Rusconi
Subject: Trying to understand a build failure for package pair aubio/waf
Date: Wed, 21 Jun 2023 00:29:24 +0200

Greetings, I do not know if the GitHub issues place is largely frequented, so I
elected to put my issue here also:

I did a git clone today and the proceeded with

make MXE_TARGETS='x86_64-w64-mingw32.shared'

After a long while, the build fails with the following error:

[build] aubio x86_64-w64-mingw32.shared
Failed to build package aubio for target x86_64-w64-mingw32.shared!

File 
"/home/rusconi/devel/mxe/tmp-aubio-x86_64-w64-mingw32.shared/aubio-0.4.2.build_/waf-1.8.17/.waf3-1.8.17-daa67386b71d29ad7cda321d44eb497a/waflib/Utils.py",
 line 87, in readf

f=open(fname,m)
^^^^^^^^^^^^^
ValueError: invalid mode: 'rUb'
make[1]: *** [Makefile:901: build-only-aubio_x86_64-w64-mingw32.shared] Error 2
make[1]: Leaving directory '/home/rusconi/devel/mxe'

The full log is here:

https://paste.debian.net/1283663/

Since I am new to MXE, I wanted to check the file and put some debugging trace
code. So I opened the Utils.py file from the path provided above. I put some
print()-based debug statements in the relevant function and ran make again. But
only to discover that the directory was overwritten anew probably from the
pkg/waf-1.8.17.tar.bz2 archive.

So, I unpackacked that archive in a tmp dir, edited the file, saved it, make a
new tar.bz2 archive, copied it to pkg/, computed the shasum for it and edited
src/waf.mk accordingly. Then I ran make again. But that did not work.

Then I discovered that the aubio package itself ships a copy of the waf
software.  So I modified that copy of the waf software (file Utils.py) in the
aubio package and updated everything.  I also modified the Utils.py file in the
waf package itself, in case. And I updated everything (that is, the checksum
value in the src/<package>.mk file and the bz2 archive itself in the pkg/ 
directory).

What I do not understand is how the 
.waf3-1.8.17-daa67386b71d29ad7cda321d44eb497a directory below is created:

mxe/tmp-aubio-x86_64-w64-mingw32.shared/aubio-0.4.2.build_/waf-1.8.17/.waf3-1.8.17-daa67386b71d29ad7cda321d44eb497a/waflib/Utils.py

Any help ?
Sincerely,
Filippo

--

⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Researcher at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄⠀⠀⠀⠀  http://msxpertsuite.org
          http://www.debian.org

~~~~
book: BLOCKEDlavoisier[.]fr/livre/notice[.]asp?id=3LKW2OAR2KROWZBLOCKED
http://books.google.fr/books?id=2NmguxmEI1sC&printsec=frontcover&dq=rusconi+f+lavoisier&hl=fr&sa=X&ei=nGGOUt2SH_Ly0gX0uIHoBQ&ved=0CDUQ6AEwAA#v=onepage&q&f=false
~~~~
Institut Diversité, Écologie et Évolution du Vivant
Unité Génétique Quantitative et Évolution
Plateforme PAPPSO

Université Paris-Saclay, INRAE, UMR CNRS 8120, AgroParisTech
12, route 128, Bâtiment 680
91272 Gif-sur-Yvette
France

http://moulon.inrae.fr/ & http://pappso.inrae.fr/
Tel : +33 (0)1 69 33 23 54
Fax : +33 (0)1 69 33 23 40




reply via email to

[Prev in Thread] Current Thread [Next in Thread]