Re-Building from source error

Add-Ons
1

I am trying to build a new add-on.

I worked through the building from source(from docs) and created iso and worked fine installing.
I then moved to create new git branch and add code for simple add-on.
Now I cannot get to finish a compile. It never even gets close to where I added my add-on at end.
Keeps failing on ruby and looks like it added a new version this time.
I have tried make.sh clean and build repeatedly now and fails everytime.

Does ipfire build process pull latest of packages everytime it compiles??

Any info would be helpful.

2

Hallo @nilrods

Welcome to the IPFire community.

First thing let’s see which version of the git repo you have in your system.

If you look in the path ipfire-2.x/config/rootfiles/core/ then there will be a directory labelled 195 currently if your git repo is based on master and it will be labelled 196 currently if your git repo is based on next.

No it does not. To get an updated version of the git repo into your local repo you would need to run the command git pull

If you are on the next repo and did a git pull then you could have ended up with a ruby lfs that had some errors. This has been corrected about 5 days ago so doing a git pull now should give you a repo that will build successfully.

If you do have a git repo that is based on next and are using it to build addons that you want to install locally then your better bet would be to make a clone of the master branch rather than next as master will either be the latest released version or the current Testing version. Either way, it will be unlikely to have potentially broken packages in it, while next does have that risk.

Of course any broken packages do get fixed after some time and a new git pull will bring your next branch up to date with the latest version in the IPFire git repo.

If your results do not match with the above comments, then feedback the info you find from the directory and also provide a copy of the failing message from your build.

3

Adolf,
Thanks for the response.
Looks like you are correct, somehow I ended up with the next branch (196) I don’t remember picking any branch, but at least I know now why it is happening.

I haven’t done any git pull since I created, I am somewhat of git newbie. Only created my own branch to start my add-on build.

Anyway, sounds like I need to start from scratch with master. Just really odd built fine over weekend and now doesn’t but it is what it is.

Thanks,
Chris

4

Well good luck with your master git clone and build.

If you run into any issues then just ask back here again and we will try and help you.

5

Hi all,
I have had such situations by tracking origin/next (using -t origin/next) instead of origin/master.
If you accidentally base your local branch on origin/next, this can happen.

As an idea :wink: ,

Best,

Erik

6

Erik,
I think you are on the right track.

I pulled from website documentation I used for build-howto

Step 8 Create project branch
which says “git checkout -b -t origin/next”

I am guessing that may be how I got to next branch.

Thanks all!!

7

So may you do not need to take the walk to go from scratch again…

You can checkout the tracking relation via git branch -vv . If you want to change back to origin/master , try git branch --set-upstream-to=origin/master and visa verce.

As an idea :slight_smile: ,

Best,

Erik