public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: pmacct marked as SKIP during IPFire build
Date: Thu, 15 Jul 2021 14:53:02 +0200	[thread overview]
Message-ID: <d992d6d3-d3c8-e822-5623-627ae984047a@ipfire.org> (raw)
In-Reply-To: <060F230A-3911-489E-A6B5-8DEDD72D22AC@ipfire.org>

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

Hi Michael,

On 15/07/2021 13:55, Michael Tremer wrote:
> Hey,
> 
> I am not the export here, but I believe this was disabled because libcdada does not build with GCC 11.
> 
> Is there an update maybe?
I have had a look and there is an update for libcdada. Doesn't mention anything about problems with gcc in its changelog.
Will give a go to testing with existing and also with the new libcdada version and see how it goes.
> 
> You can just enable it again (remove the SUP_ARCHES line) and see what happens. Feel free to post the log here.
Will do so if I have any problems.

Thanks for the info.

Regards,
Adolf.
> 
> Best,
> -Michael
> 
>> On 15 Jul 2021, at 11:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi All,
>>
>> I have been doing some update builds and while doing that with "next" I noticed that pmacct and its dependency libcdada were both marked as SKIP and so didn't get built.
>>
>> What is the reason for this? Has there been some problem that needs to be fixed?
>>
>>
>> Regards,
>>
>> Adolf.
>>
> 

  reply	other threads:[~2021-07-15 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 10:58 Adolf Belka
2021-07-15 11:55 ` Michael Tremer
2021-07-15 12:53   ` Adolf Belka [this message]
2021-07-15 16:10     ` Adolf Belka
2021-07-15 16:40       ` Michael Tremer
2021-07-15 17:48         ` Adolf Belka
2021-07-19 11:28           ` Michael Tremer

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=d992d6d3-d3c8-e822-5623-627ae984047a@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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