[GNC-dev] Build error with scm-engine on current master

[Christian Gruber]

This thread is related to the build issue I encountered when finally 
building PR #574  locally.


Invoking "make all" on current master lead to the following build error 
when compiling libgnucash/engine/engine-utilities.scm:


Backtrace:    1 (primitive-load-path 
"gnucash/engine/gnc-numeric") In ice-9/boot-9.scm:    752:25  0 
(dispatch-exception _ _ _) ice-9/boot-9.scm:752:25: In procedure 
dispatch-exception: In procedure primitive-load-path: Unable to find 
file "gnucash/engine/gnc-numeric" in load path


File libgnucash/engine/engine-utilities.scm is built with target 
scm-engine-1, therefore the same build error can be reproduced by 
invoking "make scm-engine-1" or "make scm-engine" as well.


According to PR #574   I 
can preclude, that this is due to reusing a maint build directory, since 
I built in a clean and fresh build dir.


Next I tried to build again after moving directories 
/usr/lib/x86_64-linux-gnu/gnucash/gnucash and files 
/usr/lib/x86_64-linux-gnu/gnucash/libgnc*.so.


After that I uninstalled my GnuCash 3.5, which was installed before from 
distros package manager.


Finally I searched my whole system for gnucash directories and removed 
them in /usr/local/... where I previously installed GnuCash built from 
source repo.


Everytime I built in a clean and fresh build dir, but the build error 
was always the same.


Finally I further investigated sources and found a maybe important 
change in file libgnucash/engine/engine.scm made in commit 53f59f7. 
Therefore I tried two builds at the end, one with commit 53f59f7 and the 
second with commit cb50f7a, which is one commit before 53f59f7. The 
result was, that commit 53f59f7 leads to the mentioned build error, but 
commit cb50f7a could successfully be built.


Any ideas?

Christian

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Building debian files within Docker

[Stephen M. Butler]

I tried.  Got rid of the snap version of docker and then hung up on this
step:

sudo add-apt-repository \
>    "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
>    $(lsb_release -cs) \
>    stable"
Err:1 https://download.docker.com/linux/ubuntu disco InRelease
  Invalid response from proxy: HTTP/1.0 403 CONNECT denied (ask the
admin to allow HTTPS tunnels) [IP: 127.0.0.1 3142]
Hit:2 http://archive.canonical.com/ubuntu disco
InRelease  

Hit:3 http://archive.ubuntu.com/ubuntu disco
InRelease   
  

Hit:4 http://us.archive.ubuntu.com/ubuntu disco
InRelease
Hit:5 http://security.ubuntu.com/ubuntu disco-security
InRelease 
Hit:6 http://ppa.launchpad.net/malteworld/ppa/ubuntu bionic
InRelease
Hit:7 http://us.archive.ubuntu.com/ubuntu disco-updates
InRelease
Hit:8 http://ppa.launchpad.net/subsurface/subsurface/ubuntu disco InRelease
Hit:9 http://us.archive.ubuntu.com/ubuntu disco-backports InRelease
Hit:10 http://ppa.launchpad.net/teejee2008/ppa/ubuntu disco InRelease
Reading package lists... Done
W: Failed to fetch
https://download.docker.com/linux/ubuntu/dists/disco/InRelease  Invalid
response from proxy: HTTP/1.0 403 CONNECT denied (ask the admin to allow
HTTPS tunnels) [IP: 127.0.0.1 3142]
W: Some index files failed to download. They have been ignored, or old
ones used instead.

So, how do I allow HTTPS tunnels?

--Steve

On 9/10/19 6:27 PM, Dale Phurrough wrote:
> I'm not a good resource to troubleshoot snap. In the error message you
> got, it gave a url. I clicked and there's a lot of information at that
> post on the topic. Perhaps it can help you.
>
> Meanwhile, the stable docker 19.03 just appeared today on Docker's
> official package repos. And it supports Ubuntu Disco. You can use 
> https://get.docker.com/ if you want for easy install. Or follow the
> written instructions
> at https://docs.docker.com/install/linux/docker-ce/ubuntu/
>
> Timing! ;-)
>
> --Dale
>
>
>
>
> On Wed, Sep 11, 2019 at 12:23 AM Stephen M. Butler  > wrote:
>
> Dale,
>
> I got the message about missing /snap/bin in the Path, but it is
> there. 
> Any ideas on how to proceed?
>
> steve@SteveLaptop:~$ sudo snap install docker
> Connect docker:firewall-control to core:firewall-control
>  Warning: /snap/bin was not found in your $PATH. If you've not
> restarted your session since you
>  installed snapd, try doing that. Please see
> https://forum.snapcraft.io/t/9469 for more
>  details.
>
> docker 18.06.1-ce from Canonical✓ installed
>
> steve@SteveLaptop:~$ echo $PATH
> 
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>
> steve@SteveLaptop:~$ snap version
> snap    2.41
> snapd   2.41
> series  16
> ubuntu  19.04
> kernel  5.0.0-27-generic
>
> steve@SteveLaptop:~$ cat /etc/os-release
> NAME="Ubuntu"
> VERSION="19.04 (Disco Dingo)"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 19.04"
> VERSION_ID="19.04"
> HOME_URL="https://www.ubuntu.com/;
> SUPPORT_URL="https://help.ubuntu.com/;
> BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
> 
> PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
> VERSION_CODENAME=disco
> UBUNTU_CODENAME=disco
>
> steve@SteveLaptop:~$ ps
>   PID TTY  TIME CMD
>  2746 pts/0    00:00:00 bash
>  4469 pts/0    00:00:00 ps
>
> And I can see the /snap/bin folder.
>
> --Steve
>
> On 9/9/19 6:12 AM, Dale Phurrough wrote:
> > Hi, thanks for checking in. I've never tested using the dev-docker
> > containers to build .deb within them. Long-term I would like it to
> > build containerized apps like snap, flatpak, etc. and maybe
> deb's come
> > along for free.
> >
> > I vaguely remember reading "each package manager/person maintains
> > their own blahblah to create their distro's packages" If that's true
> > and this package metadata it isn't centrally kept by the core
> GnuCash
> > team...then I suspect it's technically possible to build deb
> packages
> > within the containers (since they are full OSs), but that the
> GnuCash
> > team doesn't yet have it automated because they don't
> coordinate/have
> > the packager(s) metadata for each distro.
> >
> > True, no stable release of a Docker package to run on Disco yet.
> As an
> > alternative, you could run the testing release of Docker.
> Or...run the
> > snap for Docker. Running the snap removes your OS version conflict +
> > gives you the stable Docker 18.06 which is a very well tested
> and rich
>

Re: [GNC-dev] [GNC] Announcement: GnuCash 3.7 Released

[Stephen M. Butler]

Tommy,

I am replying via the GnC Dev list as others may have thoughts or
appreciate having the information.  This is a great community of like
minded individuals and working together produces more than individually.

Other comments throughout the following.

On 9/11/19 9:30 AM, Tommy Trussell wrote:
> Stephen:
> Replying off list. (like I did in May)
>
> It's been months since I contacted you and you subsequently posted the
> instructions to the list for creating your builds (my notes say your
> email was on May 21st). I really appreciate that "head start." And
> thank you for your time!
>
> I just wanted to let you know I have been working on this off-and-on
> (more "on" in just the past couple of weeks) even though I haven't
> contacted you again. 
>
> It's very possible I am tackling something that's too far beyond my
> expertise. (As I mentioned before, my professional experience is in
> technical writing, though I am comfortable looking at code.)

No worries there.  While my background is development the last few
decades were as an Oracle database administrator (DBA) and then a dev
manager.  Thankfully they let me do some of the database back-end
coding.  I still haven't learned C++ yet.


>
> I am continuing to attempt to get GnuCash to build properly on Ubuntu
> Bionic (18.04). 
> I have two reasons -- 
> 1) that's what I use in my office and want to upgrade to GnuCash 3.x and 
> 2) There are lots of "child" distros based on Bionic, so this will
> continue to be relevant to a lot of folks until at least next summer.

That's why I started doing the debian package.  Then I moved up to 19.04
and can't do it for 18.04/18.10 any more.  Still working on figuring
that out myself.

>
> I believe this week I MAY have stumbled upon the underlying reason the
> Bionic builds fail, but I have not yet learned enough to know what to
> do about it. 
>
> I am hoping maybe to connect better to your work.
>
> QUESTIONS:
>
> 1) Do you keep your debian GnuCash package code on github or another
> git repository?


I use the git repository that the GnC developers provide for the source
code. 

https://github.com/Gnucash/gnucash.git 

They are not interested (nor should they) in the debian specific files needed 
to build the debian based package.
I got most of this from the debian version repository.  You are free to do with 
it as you choose. (esp for 1a and 1b below).

>
> 1a) If not, can I help that happen? I have been pushing myself to
> become comfortable with basic git by committing and reverting and
> adding tags and such to my own local gits. I do have a github account.)
>
> 1b) If you don't have the code in git may I upload your debian package
> code from Google Drive to my GitHub account? (Basically I want an easy
> way to literally build on your success.) ;-) I want it in github
> because it makes it easier to tinker with the version control "safety
> net." If you don't mind, I will do it and send you the link. I don't
> see any versioning in Google Drive so I will only have two "snapshots"
> to start with.
>
> 2) Are you using irc or some other service to discuss this? (I'm not a
> big irc user but I realize that's the way to get immediate assistance
> sometimes.) If not I don't mind email. It's a lot easier except I tend
> to get too wordy.


I know that the GnC team have an irc.  I have not hooked up with that. 
So far, I am available via email.

>
> I have not yet put your instructions on a GnuCash wiki page, though
> that would be another way to collaborate.

There are instructions for doing a Linux build already at
https://wiki.gnucash.org/wiki/Building.  This is maintained by others
and I made heavy use of it to get myself to the point of doing a local
build for myself.  Someone else supplied a dependency script for Linux
which I just pushed up to my Google drive if that helps you get to the
point of doing your own build.  Look for
gnucash-development-depndency-setup.sh


Once you are able to build for yourself, then we can take the additional
steps to setup to create a .deb file for others on Ubuntu 18.x and
derivatives.  This group can provide a lot of help to get you setup to
compile locally for yourself.


--Steve


>  
>
>
> On Sun, Sep 8, 2019 at 9:07 PM Stephen M. Butler  > wrote:
>
> Build attempt was clean on first try.  Thanks John.
>
> Debian files for Disco have been uploaded to: 
> https://drive.google.com/open?id=1M04Ci8m0KthlooxgSVyLq0eyHymzRu6u
> Sorry, I'm still not able to build debian files for pre-Disco
> versions.
>
> Version: 3.7  Build ID: git 3.7-3-gb1d0dd7d5+(2019-09-08)
> Finance::Quote: 1.47
>
> Download the three .deb files located in that folder.  Make sure they
> are the only files in your download folder that contain 3.7 in the
> file
> names.
> cd to the Downloads folder.  Be sure to include the leading ./ in the
> below file name
>
> sudo apt install ./*3.7*.deb
>
> You should see