WIP: Add emacs 26.1 #3352

timvisher · 2018-06-18T13:32:15Z

Problems

Though I am depending on ncurses, I get an error during the build.
Some variable appears to not be being set to allow emacs to know where
to find libncurses.so.6

./temacs --batch  --load loadup bootstrap
./temacs: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory

This feels like something I'm doing wrong here rather than something
that I'm not understanding about the emacs build process.

Motivation: Adding emacs 26.1, need help with cross-cc tooling.

Checklist

[] Build rule all-supported completed successfully
[] Package upgrade completed successfully
[] New installation of package completed successfully

timvisher · 2018-06-30T12:20:00Z

ping :)

Safihre · 2018-07-09T06:30:33Z

After it fails, did you try to find libncurses.so.6 file on your system in the spksrc folder after it stops? You probably need to somehow tell it where to look for linking.
I'm not a true expert on this myself, but managed by tweaking some of the FLAGS or command-line parameters.

ymartin59

Thanks for contributing. My understanding is that prefix value is inconsistent in configure args

cross/emacs/Makefile

spk/emacs/Makefile

timvisher · 2018-08-15T00:51:45Z

I applied all the changes you asked for. Sadly it didn't resolve my problems. FWIW, it appears that emacs is maybe using a non-standard method of determining where to look for ncurses, but I've been unable to locate any instructions on libncurses specifically regarding emacs builds.

I've picked apart the configure run command to look for potential errors in the LDFLAGS variable but it all looks good to me and the directory it mentions indeed contains libncurses.so.6.

I've reached out for help on the mailing list so maybe someone there will be able to help me out.

timvisher · 2018-08-15T12:39:43Z

Someone got back to me on the emacs list. They think this has a somewhat dubious chance of success unfortunately. But if there's anything in their message that you can speak to please do. :)

timvisher · 2018-08-21T12:08:21Z

Got some news! I was able to get the temacs step to run by hand using the advice that Noam gave me on the mailing list. Can you give me any ideas how I could work this into the spksrc build process?

vagrant@debian-8:~/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/src$ LD_LIBRARY_PATH=../../install/var/packages/emacs/target/lib/ ./temacs --batch --load loadup
bootstrap
Loading loadup.el (source)...
Using load-path (/home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp/emacs-lisp /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp/progmodes /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp/language /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp/international /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp/textmodes /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1/lisp/vc)
Loading emacs-lisp/byte-run...
…
Finding pointers to doc strings...done
Dumping under the name emacs
87479 pure bytes used

timvisher · 2018-08-21T12:12:02Z

This also made it all the way to the stripping step.

vagrant@debian-8:~/spksrc/spk/emacs$ LD_LIBRARY_PATH=$PWD/work-apollolake-6.1/install/var/packages/emacs/target/lib/ make arch-apollolake

…
===>  Stripping binaries and libraries of emacs
Stripping bin/asn1Coding... ok
Stripping bin/asn1Decoding... ok
Stripping bin/asn1Parser... ok
Stripping bin/captoinfo... ok
Stripping bin/certtool... ok
Stripping bin/clear... ok
Stripping bin/emacs... chmod: cannot operate on dangling symlink ‘/home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/staging/bin/emacs’
../../mk/spksrc.strip.mk:49: recipe for target 'strip_target' failed
make[1]: *** [strip_target] Error 1
make[1]: Leaving directory '/home/vagrant/spksrc/spk/emacs'
../../mk/spksrc.spk.mk:451: recipe for target 'arch-apollolake' failed
make: [arch-apollolake] Error 2 (ignored)

ymartin59 · 2018-08-25T06:48:04Z

cross/emacs/PLIST

@@ -0,0 +1 @@
+bin:bin/emacs


You should include here all files required to be packaged with proper "type": https://github.com/SynoCommunity/spksrc/wiki/PLIST-files
So "lnk" has to be used for bin/emacs

I will give that a try. Any ideas on the LD_LIBRARY_PATH problem?

timvisher · 2018-08-27T17:49:03Z

With that change in place I was able to run the following without error on a clean tree.

vagrant@debian-8:~/spksrc/spk/emacs$ LD_LIBRARY_PATH=$PWD/work-apollolake-6.1/install/var/packages/emacs/target/lib/ make arch-apollolake

I'm unsure exactly what I need to do to verify that emacs can launch cleanly though, and I'm still not sure how to configure LD_LIBRARY_PATH correctly.

Still: progress! Huzzah!

ymartin59 · 2018-08-30T19:54:58Z

You have to include required libraries or other resources in PLIST file so everything is embedded in package.

Refer to documentation: https://github.com/SynoCommunity/spksrc/wiki/PLIST-files
Inspire from ffmpeg: https://github.com/SynoCommunity/spksrc/blob/master/cross/ffmpeg/PLIST

It is expected you cannot run binary "as is" because dynamic linkage expects some specific location you may inspect with ldd.

timvisher · 2018-08-31T12:40:32Z

I added

lnk:lib/libncurses.so
lnk:lib/libncurses.so.6
lib:lib/libncurses.so.6.1

to the changeset and ran:

vagrant@debian-8:~/spksrc/spk/emacs$ make arch-apollolake

and failed again at the temacs step.

And again, make clean then

vagrant@debian-8:~/spksrc/spk/emacs$ LD_LIBRARY_PATH=$PWD/work-apollolake-6.1/install/var/packages/emacs/target/lib/ make arch-apollolake

worked. Any thoughts on how to inform spksrc that LD_LIBRARY_PATH needs to be set for this build to include the target lib dir or similar?

timvisher · 2018-10-02T12:43:23Z

Ping. :)

timvisher · 2018-10-30T00:23:39Z

Ping. :)

timvisher · 2018-12-05T02:07:09Z

Any new thoughts here?

m4tt075 · 2018-12-05T20:22:58Z

@timvisher Just looked into this, trying to help. Unfortunately, I've not been able to find a quick fix either. This does not mean anything. Others might be able to help you. In any case, I found some insights that cross-compilation of emacs might not be straight-forward in the answer linked here:
https://stackoverflow.com/questions/46746976/how-to-cross-compile-emacs-for-ios
Maybe(!), there is is way building emacs natively first (like for the mono package for instance), but frankly, not sure it is worth the effort, if you can use nano instead.

timvisher · 2018-12-05T20:50:10Z

@m4tt075 Thanks for trying to help! In this instance I have basically no interest in emacs as an editor and much interest in emacs as an IRC client. :)

nano is fine for a readline based editor, as you pointed out, and I really don't want to take the plunge into irssi.

m4tt075 · 2018-12-05T21:00:47Z

@timvisher Ah, ok. Interesting. And znc?

timvisher · 2018-12-06T14:56:29Z

@m4tt075 Yeah. I just really like my emacs set up. :)

https://xkcd.com/1782/

m4tt075 · 2018-12-06T20:06:27Z

@timvisher Ahhh, that is YOU! LOL
Very well. You have my empathy! Good luck with your package. Maybe someone else can step in...

ymartin59 · 2018-12-08T08:27:58Z

@timvisher Please configure your Git client - your commits' author is "vagrant@debian-8.10-amd64" at the moment

ymartin59 · 2018-12-08T08:53:16Z

I have found out what is wrong. After emacs binary is cross-compiled, build process goes on compiling lisp thanks to temacs binary - which may not be runnable on compile system (if for another architecture like ARM).
My option is that lisp compilation has to be postponed to package postinstallation where temacs binary is runnable - the same way Python compiles its libaries https://github.com/SynoCommunity/spksrc/blob/master/spk/python3/src/service-setup.sh#L18

ymartin59 · 2018-12-08T09:01:36Z

References:

So there is chance a package can be created "easily" for x64 platforms but other architecture would require to tweak Emacs build process.

ymartin59 · 2018-12-09T10:35:27Z

Even try to go further building x64 for amd64 only adding export LD_LIBRARY_PATH=/spksrc/spk/emacs/work-x64-5.2/install/var/packages/emacs/target/lib/
but then "dumping" complains:

Dumping under the name emacs
**************************************************
Warning: Your system has a gap between BSS and the
heap (12297400 bytes).  This usually means that exec-shield
or something similar is in effect.  The dump may
fail because of this.  See the section about
exec-shield in etc/PROBLEMS for more information.
**************************************************

Because building in Docker context if I guess right.

Problems -------- - Though I am depending on ncurses, I get an [error during the build][]. Some variable appears to not be being set to allow emacs to know where to find libncurses.so.6 ``` ./temacs --batch --load loadup bootstrap ./temacs: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory ``` This feels like something I'm doing wrong here rather than something that I'm not understanding about the emacs build process.

- update emacs - include all binaries in PLIST - use SPK_COMMANDS variable (avoid service-setup.sh) - use cross/ncursesw to fix error with ncurses - TODO: build tools for host to fix build for cross compiled packages

hgy59 · 2023-07-13T23:30:24Z

closing due to lack of support for cross compilation (see https://stackoverflow.com/questions/46746976/how-to-cross-compile-emacs-for-ios)

ymartin59 requested changes Jul 15, 2018

View reviewed changes

cross/emacs/Makefile Outdated Show resolved Hide resolved

spk/emacs/Makefile Outdated Show resolved Hide resolved

spk/emacs/Makefile Outdated Show resolved Hide resolved

spk/emacs/Makefile Outdated Show resolved Hide resolved

ymartin59 mentioned this pull request Jul 15, 2018

debian-chroot: Permissions to shared folders on volume1 #3286

Closed

timvisher force-pushed the spk/emacs branch from 9506030 to c85d429 Compare August 15, 2018 00:35

ymartin59 reviewed Aug 25, 2018

View reviewed changes

ymartin59 added the status/work-in-progress label Nov 30, 2018

vagrant and others added 4 commits October 5, 2020 14:19

WIP: Feedback

20f0a13

bin:bin/emacs → lnk:bin/emacs

6ff60ca

Minor improvements in tentative to cross-compile

e5c2b33

timvisher force-pushed the spk/emacs branch from fc0620a to e5c2b33 Compare October 5, 2020 18:21

emacs: update to v27.2

6ac412f

- update emacs - include all binaries in PLIST - use SPK_COMMANDS variable (avoid service-setup.sh) - use cross/ncursesw to fix error with ncurses - TODO: build tools for host to fix build for cross compiled packages

hgy59 closed this Jul 13, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WIP: Add emacs 26.1 #3352

WIP: Add emacs 26.1 #3352

timvisher commented Jun 18, 2018 •

edited

timvisher commented Jun 30, 2018

Safihre commented Jul 9, 2018

ymartin59 left a comment

timvisher commented Aug 15, 2018

timvisher commented Aug 15, 2018

timvisher commented Aug 21, 2018

timvisher commented Aug 21, 2018 •

edited

ymartin59 Aug 25, 2018

timvisher Aug 27, 2018

timvisher commented Aug 27, 2018 •

edited

ymartin59 commented Aug 30, 2018

timvisher commented Aug 31, 2018

timvisher commented Oct 2, 2018

timvisher commented Oct 30, 2018

timvisher commented Dec 5, 2018

m4tt075 commented Dec 5, 2018

timvisher commented Dec 5, 2018

m4tt075 commented Dec 5, 2018

timvisher commented Dec 6, 2018

m4tt075 commented Dec 6, 2018

ymartin59 commented Dec 8, 2018

ymartin59 commented Dec 8, 2018

ymartin59 commented Dec 8, 2018 •

edited

ymartin59 commented Dec 9, 2018

hgy59 commented Jul 13, 2023

		@@ -0,0 +1 @@
		bin:bin/emacs

WIP: Add emacs 26.1 #3352

WIP: Add emacs 26.1 #3352

Conversation

timvisher commented Jun 18, 2018 • edited

Problems

Checklist

timvisher commented Jun 30, 2018

Safihre commented Jul 9, 2018

ymartin59 left a comment

Choose a reason for hiding this comment

timvisher commented Aug 15, 2018

timvisher commented Aug 15, 2018

timvisher commented Aug 21, 2018

timvisher commented Aug 21, 2018 • edited

ymartin59 Aug 25, 2018

Choose a reason for hiding this comment

timvisher Aug 27, 2018

Choose a reason for hiding this comment

timvisher commented Aug 27, 2018 • edited

ymartin59 commented Aug 30, 2018

timvisher commented Aug 31, 2018

timvisher commented Oct 2, 2018

timvisher commented Oct 30, 2018

timvisher commented Dec 5, 2018

m4tt075 commented Dec 5, 2018

timvisher commented Dec 5, 2018

m4tt075 commented Dec 5, 2018

timvisher commented Dec 6, 2018

m4tt075 commented Dec 6, 2018

ymartin59 commented Dec 8, 2018

ymartin59 commented Dec 8, 2018

ymartin59 commented Dec 8, 2018 • edited

ymartin59 commented Dec 9, 2018

hgy59 commented Jul 13, 2023

timvisher commented Jun 18, 2018 •

edited

timvisher commented Aug 21, 2018 •

edited

timvisher commented Aug 27, 2018 •

edited

ymartin59 commented Dec 8, 2018 •

edited