Github messages for voidlinux
 help / color / mirror / Atom feed
From: jtbx <jtbx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Ldc cross compile
Date: Fri, 26 Jan 2024 07:52:12 +0100	[thread overview]
Message-ID: <20240126065212.B4C2827D6B@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45973@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

New comment by jtbx on void-packages repository

https://github.com/void-linux/void-packages/pull/45973#issuecomment-1911572368

Comment:
Is this still active? Building libcurl on your branch fails:
```
  CC       vssh/libcurl_la-libssh2.lo
  CC       vssh/libcurl_la-libssh.lo
  CC       vssh/libcurl_la-wolfssh.lo
  CCLD     libcurl.la
/usr/bin/ld: /usr/lib64/gcc/x86_64-unknown-linux-gnu/12.2.0/../../../../lib64/libnghttp2.a(nghttp2_map.o): warning: relocation against `stderr@@GLIBC_2.2.5' in read-only section `.text'
/usr/bin/ld: /usr/lib64/gcc/x86_64-unknown-linux-gnu/12.2.0/../../../../lib64/libnghttp2.a(nghttp2_map.o): relocation R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1696: libcurl.la] Error 1
make[2]: Leaving directory '/builddir/curl-8.4.0/lib'
make[1]: *** [Makefile:1503: all] Error 2
make[1]: Leaving directory '/builddir/curl-8.4.0/lib'
make: *** [Makefile:1273: all-recursive] Error 1
=> ERROR: curl-8.4.0_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR:   in do_build() at common/build-style/gnu-configure.sh:15
```

  parent reply	other threads:[~2024-01-26  6:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 14:44 [PR PATCH] " sgn
2023-09-09  3:56 ` [PR PATCH] [Updated] " sgn
2023-10-23  7:53 ` sgn
2023-10-23 23:43 ` sgn
2023-10-23 23:43 ` sgn
2023-10-25 15:57 ` [PR PATCH] [Updated] " sgn
2023-10-25 16:42 ` sgn
2023-10-26  4:44 ` sgn
2023-10-26 10:45 ` sgn
2023-10-26 16:25 ` sgn
2023-10-26 17:01 ` sgn
2024-01-25  1:48 ` github-actions
2024-01-26  6:52 ` jtbx [this message]
2024-04-26  1:45 ` github-actions
2024-05-10  1:47 ` [PR PATCH] [Closed]: " github-actions

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=20240126065212.B4C2827D6B@inbox.vuxu.org \
    --to=jtbx@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).