From: Robert Pluim <rpluim@gmail.com>
To: joakim@verona.se
Cc: 53038@debbugs.gnu.org
Subject: bug#53038: 28.0.50; problem building
Date: Fri, 07 Jan 2022 16:05:51 +0100 [thread overview]
Message-ID: <87wnjb60xc.fsf@gmail.com> (raw)
In-Reply-To: <87zgo7r3rk.fsf@tanaka.verona.se> (joakim@verona.se's message of "Fri, 07 Jan 2022 15:58:55 +0100")
>>>>> On Fri, 07 Jan 2022 15:58:55 +0100, joakim@verona.se said:
>> Sure. And for completeness, from a clean checkout without symlinks in
>> /mnt/fast somewhere.
joakim> I tried building in several different directories which were not
joakim> symlinked.
joakim> Further datapoint:
joakim> I managed to build emacs inside a docker container on the host,
joakim> FROM fedora:34
joakim> RUN dnf -y install make gcc gtk3-devel libXpm-devel gnutls-devel giflib-devel ncurses-devel texinfo libjpeg-turbo-devel findutils
joakim> RUN dnf -y install git # why is this neeed for the build? Error: (file-missing "Searching for program" "No such file or directory" "git")
The build uses git to embed the repository version in the build (but
only when building a checkout, not a tarball)
joakim> COPY emacs.clean emacs
joakim> WORKDIR emacs
joakim> RUN make -j32 # i have 32 threads...
joakim> this managed to build, and i can also run the resulting emacs inside the
joakim> container.
joakim> fedora:34 is the same as on the host, which should rule out that there
joakim> is something weird with fedora:34 as such.
Right, so itʼs most likely an issue with the build system exposed by
your directory structure.
Another thing to try: does building in a separate directory work? ie
mkdir build && cd build && ../emacs/configure && make
Robert
--
next prev parent reply other threads:[~2022-01-07 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 20:35 bug#53038: 28.0.50; problem building joakim
2022-01-06 23:44 ` bug#53038: more info, build problems joakim
2022-01-07 6:56 ` bug#53038: 28.0.50; problem building Eli Zaretskii
2022-01-07 8:44 ` joakim
2022-01-07 11:44 ` Eli Zaretskii
2022-01-07 12:08 ` joakim
2022-01-07 12:24 ` Eli Zaretskii
2022-01-07 12:39 ` joakim
2022-01-07 12:55 ` Eli Zaretskii
2022-01-07 15:13 ` joakim
2022-01-07 15:25 ` Robert Pluim
2022-01-07 12:36 ` Robert Pluim
2022-01-07 12:55 ` joakim
2022-01-07 13:43 ` Robert Pluim
2022-01-07 14:58 ` joakim
2022-01-07 15:05 ` Robert Pluim [this message]
2022-01-07 15:09 ` Lars Ingebrigtsen
2022-01-07 15:32 ` joakim
2022-01-12 17:49 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnjb60xc.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=53038@debbugs.gnu.org \
--cc=joakim@verona.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).