Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xrootd: update to 5.5.1
Date: Tue, 14 Feb 2023 22:10:24 +0100	[thread overview]
Message-ID: <20230214211024.HzxO3NQOYJfWuA2ILnsSKs5eMYcP33SFu4DrdPeSUPQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42076@inbox.vuxu.org>

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

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/pull/42076#issuecomment-1430382513

Comment:
@amadio If I try to build 5.5.2 with the present template on `x86_64-musl` (and openssl1.1 series), I encounter the error
```
[492/583] Building CXX object src/CMakeFiles/XrdOssCsi-5.dir/XrdOssCsi/XrdOssCsiFile.cc.o
FAILED: src/CMakeFiles/XrdOssCsi-5.dir/XrdOssCsi/XrdOssCsiFile.cc.o 
/usr/bin/g++ -DHAVE_ATOMICS -DHAVE_CRYPT -DHAVE_DH_PADDED -DHAVE_FSTATAT -DHAVE_GETHBYXR -DHAVE_GETIFADDRS -DHAVE_LIBZ -DHAVE_NAMEINFO -DHAVE_READLINE -DHAVE_SENDFILE -DHAVE_SETRESUID -DHAVE_SHADOWPW -DHAVE_SIGWTI -DHAVE_SSL -DHAVE_STRLCPY -DHAVE_XRDCRYPTO -DXRDPLUGIN_SOVERSION=\"5\" -DXrdOssCsi_5_EXPORTS -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I/builddir/xrootd-5.5.2/src/.. -I/builddir/xrootd-5.5.2/src/. -I/builddir/xrootd-5.5.2/src -I/builddir/xrootd-5.5.2/build/src -DNDEBUG -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2    -ffile-prefix-map=/builddir/xrootd-5.5.2/build=. -Wall -Wextra -Wno-unused-parameter -fPIC -std=gnu++14 -MD -MT src/CMakeFiles/XrdOssCsi-5.dir/XrdOssCsi/XrdOssCsiFile.cc.o -MF src/CMakeFiles/XrdOssCsi-5.dir/XrdOssCsi/XrdOssCsiFile.cc.o.d -o src/CMakeFiles/XrdOssCsi-5.dir/XrdOssCsi/XrdOssCsiFile.cc.o -c /builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiFile.cc
In file included from /builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiFile.cc:34:
/builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiTagstoreFile.hh: In member function 'int XrdOssCsiTagstoreFile::MarshallAndWriteHeader()':
/builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiTagstoreFile.hh:176:46: error: 'bswap_32' was not declared in this scope
  176 |       if (fileIsBige_ != machineIsBige_) y = bswap_32(y);
      |                                              ^~~~~~~~
/builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiTagstoreFile.hh:180:46: error: 'bswap_64' was not declared in this scope
  180 |       if (fileIsBige_ != machineIsBige_) x = bswap_64(x);
      |                                              ^~~~~~~~
/builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiTagstoreFile.hh:184:46: error: 'bswap_32' was not declared in this scope
  184 |       if (fileIsBige_ != machineIsBige_) y = bswap_32(y);
      |                                              ^~~~~~~~
/builddir/xrootd-5.5.2/src/XrdOssCsi/XrdOssCsiTagstoreFile.hh:188:47: error: 'bswap_32' was not declared in this scope
  188 |       if (machineIsBige_ != fileIsBige_) cv = bswap_32(cv);
      |                                               ^~~~~~~~
```
Do you know how to fix this?

  parent reply	other threads:[~2023-02-14 21:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 16:55 [PR PATCH] " dkwo
2023-02-06 13:10 ` amadio
2023-02-06 19:27 ` dkwo
2023-02-14 21:10 ` dkwo [this message]
2023-02-14 21:27 ` [PR PATCH] [Updated] " dkwo
2023-02-14 21:30 ` BenJarg
2023-02-14 21:31 ` BenJarg
2023-02-14 21:46 ` [PR PATCH] [Updated] " dkwo
2023-02-14 21:47 ` dkwo
2023-02-15  9:19 ` amadio
2023-03-02 22:43 ` dkwo
2023-03-03  8:03 ` amadio
2023-05-15 15:01 ` xrootd: update dkwo
2023-05-16  6:09 ` amadio
2023-05-16  6:10 ` amadio
2023-05-16 14:44 ` dkwo
2023-05-23  8:01 ` amadio
2023-05-23 11:31 ` dkwo
2023-05-23 12:03 ` amadio
2023-05-23 12:19 ` amadio
2023-05-23 12:20 ` amadio
2023-05-23 12:21 ` amadio
2023-05-23 14:49 ` dkwo
2023-05-23 14:53 ` [PR PATCH] [Updated] " dkwo
2023-06-24 14:45 ` [PR PATCH] [Merged]: " Duncaen

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=20230214211024.HzxO3NQOYJfWuA2ILnsSKs5eMYcP33SFu4DrdPeSUPQ@z \
    --to=dkwo@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).