mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: Bruno Thomsen <bruno.thomsen@gmail.com>,
	Michael Olbrich <m.olbrich@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ncurses 6.3 compile error
Date: Mon, 21 Nov 2022 17:07:42 +0100	[thread overview]
Message-ID: <251d59d6-fd1d-4f8b-2fce-6882f4502235@t2data.com> (raw)
In-Reply-To: <58083585-6713-c0fd-73b2-b218698d2e2d@t2data.com>

Hi Bruno,

Did you solve your issue?

For whatever reason, I tripped on the same error.
Now, I can't follow the reasoning, the behavior, the patches or actually
anything in the ncurses development. To me it's just a black box of
strangeness.

Either way. I concluded that for unidentified reasons I needed:
https://invisible-mirror.net/archives/ncurses/6.3/ncurses-6.3-20211026.patch.gz
added to the patchset.

Literally the first in the series for 6.3.

Maybe someone more versed can make sense of the discussion here:
https://lists.gnu.org/archive/html/bug-ncurses/2021-10/msg00040.html

Regards,
Christian

On 10/30/22 20:47, Christian Melki wrote:
> On 10/30/22 15:19, Christian Melki wrote:
>> On 10/30/22 12:08, Bruno Thomsen wrote:
>>> error: expected a pathname, not ""
>>
>> Hmm. That home made horror show of configuration expects
>> --enable-pc-files if I'm not mistaken. Can that be a clue to something?
>> But it makes me wonder how on earth this worked in the first place?
>>
>> /C
>>
> 
> 
> My bad. Ignore that. Somehow missed that the configure line already
> contained it.
> 
> /C
> 




  reply	other threads:[~2022-11-21 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 18:50 Bruno Thomsen
2022-10-27 19:36 ` Christian Melki
2022-10-28 15:23   ` Michael Olbrich
2022-10-30 11:08     ` Bruno Thomsen
2022-10-30 14:19       ` Christian Melki
2022-10-30 19:47         ` Christian Melki
2022-11-21 16:07           ` Christian Melki [this message]
2022-11-22  5:54             ` Bruno Thomsen

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=251d59d6-fd1d-4f8b-2fce-6882f4502235@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=bruno.thomsen@gmail.com \
    --cc=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.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