[vim/vim] When cross compiling, after running `make install` the system strip is used rather than the cross toolchain's strip (Issue #11740)

OldWorldOrdr

unread,

Dec 23, 2022, 11:22:40 AM12/23/22

to vim/vim, Subscribed

Steps to reproduce

cross compile vim
run make install
the wrong strip is used and it errors

Expected behaviour

it should use the cross toolchain's strip, usually named -strip for example arm-unknown-linux-musl-strip

Version of Vim

9.0.1090

Environment

OS: arch linux
Terminal: kitty
$TERM: xterm-kitty
Shell: zsh 5.9
cross compiling for arm-apple-darwin11 (iOS 5)

my temporary fix is a symlink in my path named strip that points to /usr/bin/true

Logs and stack traces

No response

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Dec 23, 2022, 4:06:53 PM12/23/22

to vim/vim, Subscribed

> ### Steps to reproduce

>
> cross compile vim
> run make install
> the wrong strip is used and it errors

I don't quite understand how you can use "make install" after cross
compiling, since cross compiling means you build Vim for another system,
while "make install" installs it on the local system. Please explain.

> it should use the cross toolchain's strip, usually named <tripple>-strip for example arm-unknown-linux-musl-strip

You can specify a different one with $STRIP.

--
The early bird gets the worm. If you want something else for
breakfast, get up later.

/// Bram Moolenaar -- ***@***.*** -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

OldWorldOrdr

unread,

Dec 24, 2022, 10:24:08 AM12/24/22

to vim/vim, Subscribed

@brammool its to make packaging easy.
make DESTDIR=/some/dir install puts everything in the right places

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Dec 30, 2022, 10:32:15 AM12/30/22

to vim/vim, Subscribed

Well, you'll need to configure what strip to use then. So can't you use:

make STRIP=/bin/true DESTDIR=/some/dir install

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

OldWorldOrdr

unread,

Dec 30, 2022, 9:06:47 PM12/30/22

to vim/vim, Subscribed

@chrisbra I could, but the configure script is supposed to automatically detect the strip command.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Dec 31, 2022, 7:06:27 AM12/31/22

to vim/vim, Subscribed

> @chrisbra I could, but the configure script is supposed to
> automatically detect the strip command.

You may have to make sure the path for your strip command comes before
the system strip command. It's not very clear, but this stackoverflow
article may provide some help:
https://stackoverflow.com/questions/43753707/cross-compiling-with-autoconf

I could not find a good example of how to make the configure script do
this better. Perhaps:

AC_CHECK_PROG(STRIP, strip, strip, :)

Should use AC_CHECK_TOOL()?

--
What do you get when you cross a joke with a rehtorical question?

/// Bram Moolenaar -- ***@***.*** -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

—

Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Un1q32

unread,

Feb 10, 2025, 2:07:34 PM2/10/25

to vim/vim, Subscribed

Seems to be fixed

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Un1q32

unread,

Feb 10, 2025, 2:07:36 PM2/10/25

to vim/vim, Subscribed

Closed #11740 as completed.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward