Open eenblam opened 6 years ago
The build did complete, but something is breaking during autoconf with the resulting .bin
. Tried twice; not going to debug that further until I resolve the zlib1g issue.
@eenblam Looks like might just need to change end of version number from '1' to '1.1' over here https://github.com/sudomesh/sudowrt-firmware/blob/master/Dockerfile#L7
Or just remove version pin alltogether, per discussion https://github.com/sudomesh/sudowrt-firmware/pull/141#issuecomment-402907816
Would do myself but wifi is blocking ssh ports :/
@gobengo I gave that a go last week. Firmware built without showing any errors, but the resulting image couldn't autoconf because curl
wasn't included for some reason.
@eenblam @paidforby I found myself wondering 'if this is broken then why does travis pass?'. https://travis-ci.org/sudomesh/sudowrt-firmware/builds
I'm guessing travis doesn't try this 'super easy mode' (IMO more explicit description/title of this build style would be helpful). Any reason it can't?
Note - when I got a complete build last week using 1.1 instead of 1, I did use "easy mode" instead of "super easy mode." The latter rebuilds the docker container from scratch, so it's easier but takes longer.
@eenblam latest commit might fix "super easy mode" (renamed to "building on a remote server"). auto_build just needed to be updated to reflect new build process. Though I'm pretty sure it will only work the first time because to do a rebuild, you should only run,
git pull
docker cp . sudowrt-build:/usr/local/sudowrt-firmware
docker start -a sudowrt-build
@gobengo agreed about more descriptive titles, it took me very long to understand the why the "hard" way was harder... addressed this in latest commit, along with some other minor revisions.
@eenblam when you get a chance you should try re-running the firmware build "on a remote server" and see if it works. I believe the root cause of your issue has been resolved.
@paidforby Might have some time some evening this week; thanks for the heads-up!
I tried following the super easy way to build the firmware, first on
master
then onfixmeshonbootrebased
. Got the same problem both times.Steps:
ssh root@[ip build machine] 'bash -s' < create_build_machine.sh
ssh root@[ip build machine] '/opt/sudowrt-firmware/auto_build > /var/log/build.log 2>&1 &'
Got this during build:
I noticed the Dockerfile specified Ubuntu 14.04, so I tried the same with a 14.04 instance on Digital Ocean and got the same results.