From: phodina <phodina@protonmail.com>
To: help-guix@gnu.org
Cc: "Wiktor Żelazny" <wz@freeshell.de>
Subject: Re: Packaging hwinfo
Date: Sat, 24 Jul 2021 18:20:18 +0000 [thread overview]
Message-ID: <aKMMxxQKuB1T67sxo6MAGbzvRwUnQFXpY-MZN-8mwq8FabjLAHdnLAJpcAjRvRI8FD06YSp_yWETqA5Rp0bUdw5VcL6fWqtmX0Os0_HE53Y=@protonmail.com> (raw)
In-Reply-To: <20210724174430.pqcwdndxqljm34bl@wzguix>
> Hi phodina,
>
> Do you come across this issue also while compiling by hand, rather than
>
> via the Guix daemon?
>
> Here [1], you can see the same problem tackled by Gentoo community. It
>
> was 2005 and related to another package, rather than directly hwinfo,
>
> but maybe it would be worth taking a look at the current hwinfo Gentoo
>
> recipe [2]. At some point, it says
>
> Workaround from Arch, if using source tarballs from github
> ==========================================================
>
> Here’s [3] how Arch folks do it. There’s this line
>
> CFLAGS+="-fPIC -I$srcdir/$pkgname/src/hd -w" \
>
> Could it be related to libhd?
>
> Good luck,
>
> WŻ
>
> [1]: https://bugs.gentoo.org/show_bug.cgi?id=60848#c3
>
> [2]: https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/hwinfo/hwinfo-21.74.ebuild
>
> [3]: https://github.com/archlinux/svntogit-community/blob/packages/hwinfo/trunk/PKGBUILD
Hello Wiktor,
Yes, this is due to the libhd. I probably didn't hightlight it in the description.
As you suggested I already had look at Arch (previous user).
I built it successfully on Arch using the PKGBUILD.
They pass the include flag with the dir -I . Without it points to $(TOPDIR)/src/libhd hence the substitution of as otherwise it expands into -I../../src/hd
I applied this flag but the build is still failing. Besides I also opened an issue on [1] though nobody probably even noticed :-(
[1]: https://github.com/openSUSE/hwinfo/issues/103
next prev parent reply other threads:[~2021-07-24 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 15:56 Packaging hwinfo phodina
2021-07-24 17:44 ` Wiktor Żelazny
2021-07-24 18:20 ` phodina [this message]
2021-07-24 19:50 ` Wiktor Żelazny
2021-07-24 20:57 ` Tobias Geerinckx-Rice
2021-07-26 6:09 ` phodina
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='aKMMxxQKuB1T67sxo6MAGbzvRwUnQFXpY-MZN-8mwq8FabjLAHdnLAJpcAjRvRI8FD06YSp_yWETqA5Rp0bUdw5VcL6fWqtmX0Os0_HE53Y=@protonmail.com' \
--to=phodina@protonmail.com \
--cc=help-guix@gnu.org \
--cc=wz@freeshell.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).