extra characters error : ncurses on clean install 10.15

[fspkwon]

this happens with a few builds, I wonder why because you'd think
it was saying that all these buildbots that report build successful like are they just
rebuilding their own fix for what was submitted maybe once upon a time
but doesn't work now... maybe the source isn't reflecting the portfile....

I had it built up to getting openbox working and ANY CONFORMING software

so its not an all is out the window effort , its just ok weird like I see here they add a {*} wildcard
to a command my fix was I add ${destroot}/${prefix} <- a little / there... and switching
from zsh to bash makes no difference

this again is with a clean install installing qt5-kde was the first thing I even tried to do
and stopped at ncurses on macOS 10.15

csh doesn't work either, tcsh no, ksh-no,

is there a buildbot for this with archive site?

[RJVB]

I'm sorry, you're not being clear.

my port:ncurses fails to install for you because of an "extra characters" error? Can you attach port logfile ncurses, please?

There are no buildbots for custom port trees like mine.

[fspkwon]

well I restarted from scratch... and its arguing with me about qt5 because I didn't compile qt5 because of that... I have macports prioritized first and I followed the link etc etc you dont by chance have like a discord room do you??
and to clarify its asking specifically for??? gcc-13 , clang-18 and libgcc13 .... it just says else aside its looking at the devel version which can be any literal thing in the world
the: "extra characters" error? Can you attach port logfile ncurses
is not specific its more like a plague where that didn't happen when I built the macports version but IS resident
in the portstree I see something like they try to PARSE the port files by the thousand to ensure theyre all semantically correct if im not mistaken I think I saw that ... but it may be specific to ${destroot}/${prefix} <- and why that would be I dont know everyones saying no its correct, and it also jumps from what markup language it is I think in that regard its TCL and Configure ... I may not have a log file at this second but im sure I will in a few minutes .....
-> as far as using the system on macOS 10.15 kde4 and qt4 applications have a exception error where
it says is nonconforming

[fspkwon]

ok and it just completely didn't do what I wanted.. I did : port upgrade --force qt5 +qt5kde
because qt5-kde wants qt5 there and it just reinstalled all the binaries blah blah and didn't do what I wanted
so it says copy the resources to the main repository if im not mistaken

and now for example is installing the binary of qt5webkit but not honoring qt5-kde or wait it might
it switches to qt5-base and is applying patches etc

[fspkwon]

here's the whole log file https://pastebin.com/GLcE91v4 qt5-qtbase +qt5-kde is just an example
macOS: 15.x Sequoia
What else works?: Everything if you branch it out from only GTK2/GTK3 things and OpenBox with X11....
nothing XFCE, nothing QT/KDE Related....

There WERE other errors related , saying it was using compiler flags that weren't supported I have
it all here written down:
so in this case I have to find another string: --version-script=conftest.map seemed easy enough... so flag --no-as-needed and --as-needed and -z and --fatal-warnings so lets see if I can be a straight up idiot

[fspkwon]

and proof that the actual SYSTEM ok is WORKING its just I wrant! KRAY! DRI! YI!
thats everything built from source so in my case System is Clang-16

[RJVB]

I don't know what kind of sabir you're speaking but it's not a common form of English I'm familiar with. I do understand now that you have been trying to install port:qt5-qtbase from my ports tree . I have never been able to test this port on anything other than Linux myself and I completely forgot that my tree thus masks the mainstream Qt5 port with an untested and also obsolete version. That situation should be addressed now; after pulling the latest commit from my repo you can do ```

sudo port clean "qt5-*"

``` and the try whatever it is you tried that failed on port:qt5-qtbase