On 2025-10-01 04:54, Adam Dinwoodie via Cygwin-apps wrote:
I have to bisect a package config failure on a small local clone.
There are only about 80 commits, and checkout and get prep make only take a
minute until failure.
But running with SRC_URI=. or GIT_URI=. does not work!
Anyone handled such a task or have advice on doing so?
I wouldn't expect `GIT_URI=.` to work unless the cygport file is in
the root of the source directory you're working in, and even then I'm
not sure it wouldn't cause problems.
I'm currently doing something similar with the git codebase itself.
The changes I needed to make to the .cygport file were thus:
1. Stop setting SRC_URI and SRC_DIR
2. Add the following:
GIT_URI=/home/adam/git
GIT_REV="$(git -C /home/adam/git rev-parse HEAD)"
inherit git
Thanks - did not think it would be as easy as specifying $PWD/ko!
3. Optionally change the definition of VERSION; for git, I've set it
to the following, which mimics the behaviour when building from git
itself.
VERSION="$(git -C /home/adam/git describe | sed 's/-/./')
$ git describe || git describe --tags
fatal: No annotated tags can describe
'4bbf8721a3ac6401ced6a0454956801f6ba37256'.
However, there were unannotated tags: try --tags.
v0.5.12
~= VERSION so not always worth the effort.
I haven't (yet) tried making this work with `git bisect run`, but I'd
expect that to be straightforward once you have the builds working or
failing as desired when running the cygport commands manually.
It only runs autogen.sh aclocal && autoheader && automake && autoconf: cygport
autoreconfig does the same, so can I skip that?
I don't see why not, although it would obviously depend on the
specific problem you're seeing. If the cygport script is simple
enough, it might be easier to bisect by just running the build
commands directly rather than using cygport.
It appears to work, but is different from the tar, as the Cygwin autoreconf
fails every Cygwin build in config.status, which guarantees reproduction of my
issue in every commit tested, and eliminates needing bisect!
So now I need a way to avoid that and I have an issue raised with autoconf
support suggesting the culprit in lib/autoconf/status.m4!
Of course, whether that is the problem or just another symptom is the issue, as
that could lead back to something else, but I am hoping to hear back.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
