From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: 64806@debbugs.gnu.org
Subject: bug#64806: 29.0.92; build process outside srcdir gets stuck
Date: Tue, 25 Jul 2023 15:08:08 +0300 [thread overview]
Message-ID: <834jlsqjmf.fsf@gnu.org> (raw)
In-Reply-To: <202307250636.36P6aNXV016429@sdf.org> (message from Van Ly on Tue, 25 Jul 2023 06:36:23 GMT)
> Date: Tue, 25 Jul 2023 06:36:23 GMT
> From: Van Ly <van.ly@sdf.org>
> Cc: 64806@debbugs.gnu.org
>
> > Date: Sun, 23 Jul 2023 18:32:56 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: 64806@debbugs.gnu.org
> >
> > You configure with
> >
> > ../emacs-29.0.92/configure --srcdir=/usr/X/23/pkg/emacs-29.0.92
> >
> > but the build says
> >
> > Entering directory '/mnt/606/2023/pkg/emacs-29'
> >
> > which doesn't seem to be consistent with the configure command. I
> > think this is the reason for the problem you see.
> >
>
> The 29.1 release candidate seems to accommodate that symlink anomaly
> as I was able to build to completion using configure with
>
> /usr/X/23/src/emacs/emacs-29.1/configure --srcdir=/usr/X/23/src/emacs/emacs-29.1
>
> from current workdir /usr/X/23/pkg/emacs/emacs-29.1
Yes, because that's how builds outside of the source tree are supposed
to be configured and built.
So I guess we can close this issue?
next prev parent reply other threads:[~2023-07-25 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 14:49 bug#64806: 29.0.92; build process outside srcdir gets stuck Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-23 15:32 ` Eli Zaretskii
2023-07-23 17:34 ` Stephen Berman
2023-07-25 6:36 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-25 12:08 ` Eli Zaretskii [this message]
2023-07-25 13:00 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-25 13:48 ` Eli Zaretskii
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=834jlsqjmf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64806@debbugs.gnu.org \
--cc=van.ly@sdf.org \
/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).