Hi, Wes. The file you want begins with "sane-". That is, it is "sane-backends-1.0.31.tar.gz", not "backends-1.0.31.tar.gz". The second link that you circled should work.
i thought that this problem had been silently fixed. I apologize for steering you wrong about it. I assume that these confusing links are automatically generated by gitlab. Just to be clear, I downloaded a tar file with a configure script from this URL: https://gitlab.com/sane-project/backends/uploads/8bf1cae2e1803aefab9e5331550e5d5d/sane-backends-1.0.31.tar.gz Here is a little log, just to show that it has a configure file: home-pc$ wget https://gitlab.com/sane-project/backends/uploads/8bf1cae2e1803aefab9e5331550e5d5d/sane-backends-1.0.31.tar.gz --2020-09-03 21:49:42-- https://gitlab.com/sane-project/backends/uploads/8bf1cae2e1803aefab9e5331550e5d5d/sane-backends-1.0.31.tar.gz Resolving gitlab.com (gitlab.com)... 172.65.251.78, 2606:4700:90:0:f22e:fbec:5bed:a9b9 Connecting to gitlab.com (gitlab.com)|172.65.251.78|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 7301484 (7.0M) [application/x-gzip] Saving to: 'sane-backends-1.0.31.tar.gz' sane-backends-1.0.3 100%[===================>] 6.96M 10.1MB/s in 0.7s 2020-09-03 21:49:43 (10.1 MB/s) - 'sane-backends-1.0.31.tar.gz' saved [7301484/7301484] home-pc$ tar tfz sane-backends-1.0.31.tar.gz | grep configure sane-backends-1.0.31/configure sane-backends-1.0.31/configure.ac Please let me know if you still have problems. Adam On Thu, Sep 3, 2020 at 2:26 PM Wes Rishel <[email protected]> wrote: > Olaf and everyone -- thanks for your help. > > re: "*Our* source tarballs contain everything needed to build starting > with a > > ./configure" > > I'm not sure if I understand where to find "our" tarballs. I haveused the > ones from gitlab shown in the image at [1] > > In these archives, there is no command file named "configure" (as above) > but the README calls for starting with ./autogen.sh. When I do that the > process appears to be in an infinite loop terminated by a segmentation > fault. The complete output is at [2] below. I suspect that the significant > issue is highlighted in red below, but if so, I don;t know what I should do. > > This is pretty much a stock Ubuntu 18.04 system. > > [1] selected tarballs > > [image: image.png] > > *[2] command output from ./autoconfigure* > > autoreconf: Entering directory `.' > autoreconf: running: autopoint --force > Copying file po/Rules-quot > autoreconf: running: aclocal --force --warnings=all -I m4 > fatal: not a git repository (or any of the parent directories): .git > configure.ac:14: error: AC_INIT should be called with package and version > arguments > /usr/share/aclocal-1.15/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:14: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > aclocal: error: echo failed with exit status: 1 > autoreconf: aclocal failed with exit status: 1 > patching file ./ltmain.sh > Hunk #1 FAILED at 9708. > Hunk #2 FAILED at 10166. > 2 out of 2 hunks FAILED -- saving rejects to file ./ltmain.sh.rej > (*** The above line repeated about 12000 times ***) > patch: **** Can't create file ./ltmain.sh.orig : Too many open files > patch: **** Can't create file ./ltmain.sh.orig./autogen.sh: line 6: 13306 > Segmentation fault (core dumped) patch "$srcdir/ltmain.sh" > "$srcdir/ltmain.sh.patch" > patching file ./po/Rules-quot > fatal: not a git repository (or any of the parent directories): .git > configure.ac:14: error: AC_INIT should be called with package and version > arguments > /usr/share/aclocal-1.15/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:14: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > aclocal: error: echo failed with exit status: 1 > autoreconf: aclocal failed with exit status: 1 > > > On Thu, Sep 3, 2020 at 4:02 AM Olaf Meeuwissen <[email protected]> > wrote: > >> Hi Adam, >> >> Adam Richter writes: >> >> > Hi, Wes ald Ralph. >> > >> > I am sorry for not noticing this thread earlier. This is a known bug >> > with the .tar.gz source releases before 1.0.31 and is in the bug >> > tracking system at >> > https://gitlab.com/sane-project/backends/-/issues/248 . 1.0.31 should >> > build for you. >> >> Thanks for trying to help! But I must correct you a little bit. *Our* >> source tarballs contain everything needed to build starting with a >> >> ./configure >> >> The problem is that GitLab automatically adds *their* source tarballs >> that only include what we keep in the git repository. I've submitted >> an [issue][1] with GitLab to get this addressed. >> >> [1]: https://gitlab.com/gitlab-org/gitlab/-/issues/232074 >> >> Similarly, people also seem to use the download functionality in the web >> interface to get GitLab created source tarballs. These are just a top >> skim of the repository at a given point in the project's history. They >> are the same as you would get from a >> >> git archive >> >> > The issue is that the releases in a certain range of versions were >> > made from git snapshots which did not include ./configure and related >> > files that are normally built for a release, and the version of >> > configure.ac invokes "git describe --dirty" to figure out the version >> > number, which requires a .git directory tree, which is not included in >> > the .tar.gz source release. >> >> That'd be the GitLab provided "source archives". >> Our [releases][2] include good source archives as long as you download >> the sane-backends-$version.tar.gz from the Other section in the Assets. >> >> [2]: https://gitlab.com/sane-project/backends/-/releases >> >> > Any of the following three solutions should work: >> > (a) edit autogen.sh to replace "[git describe --ditry]" with the >> > version number you want, >> > (b) build 1.0.31 instead, >> > (c) build from git clone (you can check out the versions using version >> > branch names, which you can see with "git branch -a"). >> > >> > I encourage you to report back if any of the above three options do >> > not work for you or if all are inadequate for your situation. >> >> :+1: >> >> > Adam >> >> Hope this helps, >> -- >> Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 >> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >> Support Free Software https://my.fsf.org/donate >> Join the Free Software Foundation https://my.fsf.org/join >> >
