git/list[1] front-page[2] threads[3] people[4] search[5] about
 

problem building git 1.6.0 on SuSE

From
MMichaelTiloDressel@t-online.de <michaeltilodressel@t-online.de>
Date
Aug 22, 2008, 11:47 UTC
Message-ID
<1KWV74-1aI9su0@fwd34.aul.t-online.de>
Hi,
I get the following errors when rpmbuild'ing git:
RPM build errors:
    File not found by glob:
/var/tmp/git-1.6.0-1-root-michael/usr/lib64/git-core/*svn*
    File not found by glob:
/var/tmp/git-1.6.0-1-root-michael/usr/lib64/git-core/*cvs*
    File not found:
/var/tmp/git-1.6.0-1-root-michael/usr/lib64/git-core/git-archimport
    File not found by glob:
/var/tmp/git-1.6.0-1-root-michael/usr/lib64/git-core/*email*
    File not found:
/var/tmp/git-1.6.0-1-root-michael/usr/lib64/git-core/git-gui
    File not found:
/var/tmp/git-1.6.0-1-root-michael/usr/lib64/git-core/git-citool

I have to replace %{_libexecdir} by /usr/libexec in git.spec to get around this problem.

I guess the %{_libexecdir} macro's value is not respected everywhere in configure(.in) etc.

The reason may be that on my system rpm --eval %{_libexecdir} returns: /usr/lib64 . While on others it may return /usr/libexec. And if /usr/libexec is used somewhere hard wired it won't show up that the value %{_libexecdir} is ignored.

Still I think this is potentially a general problem not only related to SuSE.

I may take care of this problem at some later point when I have some more time to learn about the git's building and packaging internals. Maybe somebody else can do it quicker.

Cheers, Michael

Message 1 of 1 in “problem building git 1.6.0 on SuSE”
  1. MichaelTiloDressel@t-online.deAug 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.