Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not determine kind of name for C.GIT_BLAME_IGNORE_WHITESPACE #711

Closed
utkarsh2102 opened this issue Dec 6, 2020 · 3 comments · Fixed by #724
Closed

Could not determine kind of name for C.GIT_BLAME_IGNORE_WHITESPACE #711

utkarsh2102 opened this issue Dec 6, 2020 · 3 comments · Fixed by #724

Comments

@utkarsh2102
Copy link

Hey,

Whilst building git2go v31.4.3 with libgit2 v1.0.1, I get a build failure with the following error:
src/gopkg.in/libgit2/git2go.v31/blame.go:51:54: could not determine kind of name for C.GIT_BLAME_IGNORE_WHITESPACE

I am not sure what's wrong, any ideas?

@lhchavez
Copy link
Contributor

lhchavez commented Dec 6, 2020

per https://github.com/libgit2/git2go#which-go-version-to-use it should be v30, not v31 if you need compatibility with libgit2 v1.0. v31 requires libgit2 v1.1.

@lhchavez lhchavez closed this as completed Dec 6, 2020
@utkarsh2102
Copy link
Author

Aah, I am terribly sorry for not taking a look at that earlier. Thanks for your work, anyhow! :)

@lhchavez
Copy link
Contributor

lhchavez commented Dec 6, 2020

Aah, I am terribly sorry for not taking a look at that earlier. Thanks for your work, anyhow! :)

no worries :)

lhchavez added a commit to lhchavez/git2go that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: libgit2#711
Fixes: libgit2#617
lhchavez added a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
github-actions bot pushed a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
(cherry picked from commit 4b2ac7c)
github-actions bot pushed a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
(cherry picked from commit 4b2ac7c)
github-actions bot pushed a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
(cherry picked from commit 4b2ac7c)
lhchavez added a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
(cherry picked from commit 4b2ac7c)

Co-authored-by: lhchavez <lhchavez@lhchavez.com>
lhchavez added a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
(cherry picked from commit 4b2ac7c)

Co-authored-by: lhchavez <lhchavez@lhchavez.com>
lhchavez added a commit that referenced this issue Dec 13, 2020
This change renames the build files so they come lexicographically
before any source files. This makes the compile errors (due to
mismatched libgit2 versions) easier to understand, since the
`Build_*.go` files will be tried before the rest, and the `#error` in
those files will kick in, leading to a much better experience.

This unfortunately goes a bit against the defacto standard of using only
lowercase characters in filenames, but the better developer experience
(and better self-diagnosis when things go wrong instead of having to
open a new issue) is worth the deviation.

Fixes: #711
Fixes: #617
(cherry picked from commit 4b2ac7c)

Co-authored-by: lhchavez <lhchavez@lhchavez.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants