Can't build 1.2.2

HandBrake for Windows support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
andrewk89
Regular User
Posts: 59
Joined: Thu Jun 13, 2013 4:29 pm

Can't build 1.2.2

Post by andrewk89 »

Description of problem or question:
Goal is to build 1.2.2 for Windows x64 with HE-AAC enabled.

Building on Ubuntu 18.04 (Windows subsystem for Linux) using some older instructions https://forum.videohelp.com/threads/383 ... or-Windows. I've used these instructions quite a few times. Last used to get .dll for Windows 1.2.0 (HE-AAC currently working).

Home folder was clean when I started. instructions borked pretty early - seems to be unable to build Mingw. See output below. Contrary to the messages, there isn't a log file in the toolchains folder. Only thing there is mingw-w64-5.0.3-gcc-7.3.0 folder.

Steps to reproduce the problem (If Applicable):

HandBrake version (e.g., 1.0.0):

Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):
Ubuntu 18.04 (Windows Subsystem for Linux)

HandBrake Activity Log ***required*** (see How-to get an activity log)

Code: Select all

andrew@Andrew-PC:~/HandBrake$ git checkout tags/1.2.2
Note: checking out 'tags/1.2.2'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 4eb9f7b2f MacGui: upgrade Sparkle to version 1.21.3
andrew@Andrew-PC:~/HandBrake$ cd
andrew@Andrew-PC:~$ HandBrake/scripts/mingw-w64-build x86_64
Downloading [03/08] mingw-w64 5.0.3 unable to download from urls: http://downloads.sourceforge.net/project/mingw-w64/mingw-w64/mingw-w64-release/mingw-w64-v5.0.3.tar.bz2
unable to download to file: /home/andrew/toolchains/mingw-w64-5.0.3-gcc-7.3.0/pkg/mingw-w64-v5.0.3.tar.bz2
error: subprocess returned non-zero error code (1)
logs and temporary files may exist at /home/andrew/toolchains
andrew@Andrew-PC:~$ cd HandBrake
andrew@Andrew-PC:~/HandBrake$ cd scripts
andrew@Andrew-PC:~/HandBrake/scripts$ ls
build-presets.sh            create_resources.py  manicure.rb      quotestring.py  tag-release.sh
create_flatpak_manifest.py  mac-toolchain-build  mingw-w64-build  repo-info.sh    tst.aspect
andrew@Andrew-PC:~/HandBrake/scripts$ cd
andrew@Andrew-PC:~$ HandBrake/scripts/mingw-w64-build x86_64
Downloading [03/08] mingw-w64 5.0.3 unable to download from urls: http://downloads.sourceforge.net/project/mingw-w64/mingw-w64/mingw-w64-release/mingw-w64-v5.0.3.tar.bz2
unable to download to file: /home/andrew/toolchains/mingw-w64-5.0.3-gcc-7.3.0/pkg/mingw-w64-v5.0.3.tar.bz2
error: subprocess returned non-zero error code (1)
logs and temporary files may exist at /home/andrew/toolchains
andrew@Andrew-PC:~$
User avatar
s55
HandBrake Team
Posts: 9860
Joined: Sun Dec 24, 2006 1:05 pm

Re: Can't build 1.2.2

Post by s55 »

Downloading [03/08] mingw-w64 5.0.3 unable to download from urls: http://downloads.sourceforge.net/projec ... .3.tar.bz2

unable to download to file:


That file is available here so you appear to have an issue your end.
mduell
Veteran User
Posts: 7264
Joined: Sat Apr 21, 2007 8:54 pm

Re: Can't build 1.2.2

Post by mduell »

Or the ever-decaying sourceforge had a problem at the time of his attempted download.
andrewk89
Regular User
Posts: 59
Joined: Thu Jun 13, 2013 4:29 pm

Re: Can't build 1.2.2

Post by andrewk89 »

Tried again later and the download worked.

This morning the build still hadn't finished. No CPU or I/O activity, either. Pressed <Space> and it went a little further and stopped. That went on a couple of more times until it finished. I/O is terrible under Windows Subsystem for Linux, but not 16 hours bad (1.2.0 .dll took ~2 hours). It's almost like it was piping the output through the more or less commands "forcing" you to read the output during the build.

Code: Select all

-------------------------------------------------------------------------------
time end: Sun Feb 24 08:54:48 2019
duration: 15 hours, 59 minute, 46 seconds (57586.67s)
result: SUCCESS
-------------------------------------------------------------------------------
Build is finished!
You may now cd into ./build and examine the output.
Post Reply