threads / discuss / 17573

libexec path

Subject: libexec path

## tl;dr

2 messages between Feb 4, 2009 and Feb 5, 2009.

replies: 1people: 2as markdown or json

Charles· Feb 4, 2009, 23:53 UTC · lore

How come in git-gui/GIT-GUI-VARS

gitexecdir is set to '/usr/local//usr/local/ libexec/git-core/'

when my configure prefix is "/usr/local" ?

Everything else ends up in /usr/local as it should, but libexec ends up in /usr/local/usr/local

I'm cloning from the latest stuff.

A Large Angry SCM· Feb 5, 2009, 02:17 UTC · re: Charles · lore

Re: libexec path

Charles wrote:

Show 11 quoted lines

> How come in git-gui/GIT-GUI-VARS
> 
> gitexecdir is set to '/usr/local//usr/local/
> libexec/git-core/'
> 
> when my configure prefix is "/usr/local" ?
> 
> Everything else ends up in /usr/local as it should, but libexec ends
> up in /usr/local/usr/local
> 
> I'm cloning from the latest stuff.

This is the same symptom as the Makefile breakage I email the list about over the weekend.

$ 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.