From: littlewing7 <littlewing7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libtickit and libvterm update
Date: Fri, 28 Apr 2023 09:10:24 +0200 [thread overview]
Message-ID: <20230428071024.IE9vNO5ypWvU9Oo3A913yRNebdS5bSI0fDS9HcQz3Ak@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43532@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3013 bytes --]
New comment by littlewing7 on void-packages repository
https://github.com/void-linux/void-packages/pull/43532#issuecomment-1527096864
Comment:
HI guys,
./xbps-src clean doesn't resolve the issue.
At this point I suspects a different problem, relative to the Makefile/template of libtickit tar.gz who became incompatible with the newest versions of libtool/workflow used for building packages.
This because if you aren't able to build the actual released version of libtickit-0.4.1 who is published in the official repository, then something externally to the package libtickit-0.4.1.tar.gz was changed between the time of successful build and now.
I'm able to build successfully the package libvterm-0.3.1.tar.gz (created from the same author )
I suspect something a little bit different for the libtickit-04.3.tar.gz, for the above reasons, because i try to add the post_extract command to the template of libtickit as the one on libvterm:
but the build continue to fail with this error:
` /usr/arm-linux-gnueabihf/usr/bin/libtool --quiet --mode=compile --tag=CC arm-linux-gnueabihf-gcc -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv6 -mfpu=vfp -mfloat-abi=hard -I/usr/arm-linux-gnueabihf/usr/include -ffile-prefix-map=/builddir/libtickit-0.4.3=. -Wall -Iinclude -Isrc -std=c99 -DHAVE_UNIBILIUM -o src/window.lo -c src/window.c
/usr/arm-linux-gnueabihf/usr/bin/libtool --quiet --mode=link --tag=CC arm-linux-gnueabihf-gcc -rpath /usr/lib -version-info 3:0:0 -o libtickit.la src/bindings.lo src/debug.lo src/evloop-default.lo src/mockterm.lo src/pen.lo src/rect.lo src/rectset.lo src/renderbuffer.lo src/string.lo src/term.lo src/termdriver-ti.lo src/termdriver-xterm.lo src/tickit.lo src/utf8.lo src/window.lo -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -L/usr/arm-linux-gnueabihf/usr/lib -lunibilium -ltermkey
/usr/bin/ld: src/.libs/bindings.o: relocations in generic ELF (EM: 40)
/usr/bin/ld: src/.libs/bindings.o: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
make: *** [Makefile:62: libtickit.la] Error 1
=> ERROR: libtickit-0.4.3_1: do_build: '${make_cmd} CC="$CC" CXX="$CXX" LD="$LD" AR="$AR" RANLIB="$RANLIB" CPP="$CPP" AS="$AS" OBJCOPY="$OBJCOPY" OBJDUMP="$OBJDUMP" CFLAGS="$CFLAGS" CXXFLAGS="$CXXFLAGS" LDFLAGS="$LDFLAGS" PREFIX=/usr prefix=/usr ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/gnu-makefile.sh:9
`
many thanks for the patience and help.
Max
next prev parent reply other threads:[~2023-04-28 7:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 22:05 [PR PATCH] " littlewing7
2023-04-19 22:09 ` [PR PATCH] [Updated] " littlewing7
2023-04-19 22:14 ` mhmdanas
2023-04-19 22:15 ` mhmdanas
2023-04-20 6:40 ` [PR PATCH] [Updated] " littlewing7
2023-04-20 10:17 ` littlewing7
2023-04-20 11:59 ` [PR PATCH] [Updated] " abenson
2023-04-20 12:04 ` abenson
2023-04-20 12:06 ` abenson
2023-04-20 12:07 ` abenson
2023-04-20 13:51 ` littlewing7
2023-04-26 13:59 ` littlewing7
2023-04-26 15:26 ` abenson
2023-04-26 20:23 ` [PR REVIEW] " mhmdanas
2023-04-26 20:23 ` mhmdanas
2023-04-26 20:23 ` mhmdanas
2023-04-26 22:04 ` littlewing7
2023-04-27 11:36 ` abenson
2023-04-27 11:39 ` littlewing7
2023-04-27 20:32 ` mhmdanas
2023-04-28 7:09 ` littlewing7
2023-04-28 7:10 ` littlewing7 [this message]
2023-04-28 8:43 ` littlewing7
2023-05-03 16:44 ` [PR PATCH] [Updated] " littlewing7
2023-05-03 16:55 ` littlewing7
2023-05-03 17:03 ` [PR PATCH] [Updated] libtickit update littlewing7
2023-05-03 17:05 ` littlewing7
2023-05-03 17:16 ` littlewing7
2023-05-03 17:19 ` littlewing7
2023-05-03 17:27 ` [PR PATCH] [Closed]: " abenson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230428071024.IE9vNO5ypWvU9Oo3A913yRNebdS5bSI0fDS9HcQz3Ak@z \
--to=littlewing7@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).