[Nasm-bugs] [Bug 3392449] New: "cannot stat './nasm.1': No such file or directory" when building from Git
no-reply at bugzilla-nasm.gorcunov.org
no-reply at bugzilla-nasm.gorcunov.org
Mon Nov 6 12:30:39 PST 2017
https://bugzilla.nasm.us/show_bug.cgi?id=3392449
Bug ID: 3392449
Summary: "cannot stat './nasm.1': No such file or directory"
when building from Git
Product: NASM
Version: unspecified
Hardware: All
OS: All
Status: OPEN
Severity: normal
Priority: Medium
Component: Assembler
Assignee: nobody at nasm.us
Reporter: werner.robitza at gmail.com
CC: gorcunov at gmail.com, hpa at zytor.com, nasm-bugs at nasm.us
Obtained from: Built from git using configure
I am using Ubutu 16.04 (fresh Docker image), trying to install NASM from Git
instead of the tarball.
I run:
cd ~/ffmpeg_sources && \
git clone --depth 1 git://repo.or.cz/nasm.git && \
cd nasm && \
./autogen.sh && \
PATH="$HOME/bin:$PATH" ./configure --prefix="$HOME/ffmpeg_build"
--bindir="$HOME/bin" && \
make && \
make install
But in the last step, I get:
mkdir -p /root/bin
/usr/bin/install -c nasm /root/bin/nasm
/usr/bin/install -c ndisasm /root/bin/ndisasm
mkdir -p /root/ffmpeg_build/share/man/man1
/usr/bin/install -c -m 644 ./nasm.1 /root/ffmpeg_build/share/man/man1/nasm.1
/usr/bin/install: cannot stat './nasm.1': No such file or directory
Makefile:340: recipe for target 'install' failed
make: *** [install] Error 1
When instead I use the latest release, everything works fine:
cd ~/ffmpeg_sources
wget http://www.nasm.us/pub/nasm/releasebuilds/2.13.01/nasm-2.13.01.tar.bz2
tar xjvf nasm-2.13.01.tar.bz2
cd nasm-2.13.01
./autogen.sh
PATH="$HOME/bin:$PATH" ./configure --prefix="$HOME/ffmpeg_build"
--bindir="$HOME/bin"
make
make install
Returns:
mkdir -p /root/bin
/usr/bin/install -c nasm /root/bin/nasm
/usr/bin/install -c ndisasm /root/bin/ndisasm
mkdir -p /root/ffmpeg_build/share/man/man1
/usr/bin/install -c -m 644 ./nasm.1 /root/ffmpeg_build/share/man/man1/nasm.1
/usr/bin/install -c -m 644 ./ndisasm.1
/root/ffmpeg_build/share/man/man1/ndisasm.1
--
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.
More information about the Nasm-bugs
mailing list