From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel@gnu.org
Subject: Trying to build a .deb on Ubuntu 20.04 wiht native-comp
Date: Wed, 28 Apr 2021 07:41:30 +0200 [thread overview]
Message-ID: <CAO48Bk9pEOkwYi27Bc+2MXZN_iX35j3RqruORAiomGiTT1QYZA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
Hi
I'm trying to build Debian packages for Ubuntu20.04 with native-comp on and
I regularly end up:
gcc: error: fringe.o: No such file or directory
gcc: error: image.o: No such file or directory
gcc: error: xgselect.o: No such file or directory
gcc: error: terminfo.o: No such file or directory
gcc: error: lastfile.o: No such file or directory
make[3]: *** [Makefile:632: temacs] Error 1
make[3]: Leaving directory '/home/paag/Devel/emacs/emacs/build/gtk/src'
make[2]: *** [Makefile:425: src] Error 2
make[2]: Leaving directory '/home/paag/Devel/emacs/emacs/build/gtk'
dh_auto_build: error: cd build/gtk && make -j4 NATIVE_FULL_AOT=1 returned
exit code 2
make[1]: *** [debian/rules:114: override_dh_auto_build] Error 2
make[1]: Leaving directory '/home/paag/Devel/emacs/emacs'
make: *** [debian/rules:172: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2
The only flag I have enabled is for native compilation. If I disable native
compilation, I can build emacs28 flawlessly. Is anyone else trying
something similar? I'd like to exchange experiences. having the Debian
packages is more cumbersome than just compiling, but it allows me to switch
between versions easier
Best, /PA
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
[-- Attachment #2: Type: text/html, Size: 1785 bytes --]
next reply other threads:[~2021-04-28 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 5:41 Pedro Andres Aranda Gutierrez [this message]
2021-04-28 7:42 ` Trying to build a .deb on Ubuntu 20.04 wiht native-comp Andrea Corallo via Emacs development discussions.
2021-04-28 9:59 ` Pedro Andres Aranda Gutierrez
2021-04-28 19:07 ` Andrea Corallo via Emacs development discussions.
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=CAO48Bk9pEOkwYi27Bc+2MXZN_iX35j3RqruORAiomGiTT1QYZA@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-devel@gnu.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).