What's new

amcfwm - AsusWRT-Merlin Custom Firmware Manager

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Nothing should be compiled off master/HEAD. I haven't tried compiling it in many months, it's only used to apply repository-wide changes (like package updates). All the GPL-related changes are applied directly to their respective branches.
yea i would only recommend building off of mainline .
 
The 18.04 LTS upgrade path to 20.04 LTS won't be enabled by Canonical until this summer.
 
@Adamm very minor issue, but it appears that the changelog text file that is included in the zip is pulled form the mainline branch, not the ax branch for ax models. I ran a build on an AX88U which shows gpl merge and 384.18 alpha, but the changelog in the zip still referenced 384.17. Looking at your script, it looks like it pulls the txt from $SRC_LOC which in my casse is /home/user/amng. If i look in the /home/user/amng.ax88 folder i see the expected changelog.

Thanks for all your contributions to the Merlin community!
 
Thank you Adamm, your script saves us (rookies) from a lot of hassle.
I followed the steps with caution, but my AX56U image does not compile (also tried the force-mode).
The output is here: https://pastebin.com/dkaSfrCx
Could you guys point me in the right direction?

Thanks!
After a lot of fiddling, I managed to run the script by skipping two preliminary tests (edited asuswrt-merlin.ng/release/src-rt-5.02axhnd.675x/make.common) :
Code:
prebuild_checks:
#    @echo "shell is $(SHELL).  Bash version is $(shell echo $$BASH_VERSION)"
#    @if [ -z "$(shell echo $$BASH_VERSION)" ]; then \
#        echo "***************************************************"; \
#        echo "ERROR: $(SHELL) does not invoke bash shell"; \
#        echo "***************************************************"; \
#        exit 1; \
#    fi
#    @if [ $(shell whoami) == root ]; then \
#        echo "***************************************************"; \
#        echo "ERROR: Attempting to build as root."; \
#        echo "***************************************************"; \
#        exit 1; \
#    fi

I don't know exactly what I'm doing, but if anyone has the same problem, it seems to work. Cheers!
 
You need to set your default shell to bash. By default, Ubuntu will use dash instead.

Code:
sudo dpkg-reconfigure dash

Then tell it to NOT use dash.
 
I really want to jump in to this but fear it is over my head. Looks like it was well thought out though. Great work @Adamm ;)
 
Thank you @RMerlin for the whole Dash and Bash solution :) I got mine working finally
YES.png
 
@Adamm i've been using this since the initial release with no issue really. Even got it to run on 20.04, but starting this week, builds for my AX88U have been dying because the vm is running out of memory. Im not sure if an os update has broken something. I've set up fresh 18.04 and 20.04 vm's and its still happening on both. Since 2004 is not supported, i'll stick with logs from 18.04

what I observe in system monitor is about 2-3 minutes after seeing all builds launched please wait in the terminal, the memory balloons up from about 20% to 100% then the swap file hits 100%, the screen freezes and then starts throwing out of memory errors. Both old and new sets of 18.04 and 20.04 vm's have 8GB ram.

1st part of build output https://pastebin.com/Tx7LFkXP
2nd part of build output https://pastebin.com/hJAafmi5
Config: https://pastebin.com/367pKcci

Thanks for any input you have.
 
@Adamm i've been using this since the initial release with no issue really. Even got it to run on 20.04, but starting this week, builds for my AX88U have been dying because the vm is running out of memory. Im not sure if an os update has broken something. I've set up fresh 18.04 and 20.04 vm's and its still happening on both. Since 2004 is not supported, i'll stick with logs from 18.04

what I observe in system monitor is about 2-3 minutes after seeing all builds launched please wait in the terminal, the memory balloons up from about 20% to 100% then the swap file hits 100%, the screen freezes and then starts throwing out of memory errors. Both old and new sets of 18.04 and 20.04 vm's have 8GB ram.

1st part of build output https://pastebin.com/Tx7LFkXP
2nd part of build output https://pastebin.com/hJAafmi5
Config: https://pastebin.com/367pKcci

Thanks for any input you have.

Disable the cleanup tree setting, it is broken IIRC. Beyond that you should be able to compile images on a stock Ubuntu build, my NAS only has an Intel I3-8100T and 2gig of ram dedicated for the VM and works without issues;

RVtYt8c.png
 
@fields987, anything special you had to do on 20.04 to get this working?

I am planning on installing 20.04 on a raspberry pi 4 to play around with as well as continue the learning curve. I have a 20.04 Server now working as a DC and another VM, but I have not found the time yet to play with building merlin.
 
Disable the cleanup tree setting, it is broken IIRC. Beyond that you should be able to compile images on a stock Ubuntu build, my NAS only has an Intel I3-8100T and 2gig of ram dedicated for the VM and works without issues;

RVtYt8c.png
@Adamm, no luck. I've tried disabling that setting and resetting amcfwm to default settings and still see the same behavior. I was able to build some .19alpha builds. Wonder if any of the commits in the last few days are the culprit?

@fields987, anything special you had to do on 20.04 to get this working?

I am planning on installing 20.04 on a raspberry pi 4 to play around with as well as continue the learning curve. I have a 20.04 Server now working as a DC and another VM, but I have not found the time yet to play with building merlin.
@Jeffrey Young, when it was working, i just followed the install guide for AMCFWM for 18.04 and included
sudo apt install automake-1.15 per Merlin's guide on compling using wsl2. https://github.com/RMerl/asuswrt-merlin.ng/wiki/Compiling-under-WSL2
 
@Adamm, no luck. I've tried disabling that setting and resetting amcfwm to default settings and still see the same behavior. I was able to build some .19alpha builds. Wonder if any of the commits in the last few days are the culprit?

Builds from the ax branch currently fail due to recent changes, this happens from time to time during the development process, nothing to-do with amcfwm.
 
Builds from the ax branch currently fail due to recent changes, this happens from time to time during the development process, nothing to-do with amcfwm.
Thanks, @Adamm, I forked the asuswrt-merlin.ng repo, pointed amcfwm to it and played around some this morning. If i reverted "build: enable parallel kernel building on AX models" my build worked. If i merged master into ax which contains "build: fix processor count for parallel building" my build worked. I suspect once Eric merges master again, we'll be good. Thanks again for the help.
 
@Adamm, I read the amcfwm output text and noticed this line happens a hundred times or more... ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. I had problems after the .19 build was put in github.
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top