@kas1e

thanks

nah, that bug i pointed out in scummvm was fixed a while ago...I just never came around doing another binutils test.

will do asap and report back...probably in november...

@MigthyMax
@kas1e

thank you both...will try to give it a whirl

where can i get the latest 2.40 package?
still on roman"s site?

@MartinW

be carefull now...it seems this created "symlink", or whatever it is, is nasty...

@elfpipe

will do, thank you

@elfpipe

not your fault

reconstructing it is easy but time consuming

btw...I had to reformat the partition to get rid of those strange files

@elfpipe

ok, i have all of that, clib4.library in place too (otherwise it won't run)...but I still get those crazy loop in loop directory which points to itself.

i can't delete or rename them, because, as I said, they point to itself

i also just killed my whole porting subdir by trying to back it up...backup told me
ERROR: some directories too deep
so i guess there is some kind of loophole in those directories called "Development:porting"

not sure and as it seems I'm the only one having this strange problem

@rjd324

i can point you to the project i was trying to port (small)
https://files.musepack.net/source/musepack_src_r475.tar.gz

just start

and let it run until it hits memcmp

the configure script probably needs some (heavy?) editing still, i just wanted to see how far it will go w/o changing anything

@elfpipe

I'm not using clib4 et al, still on newlib...
Do i need to switch to clib4 for cmake?

I'm only ever assuming

i do have a home: assign, but it points to another partition (i think i introduced it when i installed ssh the other day)
Does the home: assign need to be on the same partition as the cmake-amiga: assign?

seems i have to learn still...

@all

as it seems newlib doesnt have

any way to work around it?

@rjd324

yes, looks like some kind of repeating path bug, maybe stemming from the fact it cant write to the given path in the first place for some reason

@elfpipe

nope, exact same error as above with .unix in place

@elfpipe

heh, i missed the .unix part since i had the assign already on place fore the older cmake (just adapted it to the new path)

I have now

I'll try and see if *that* error is gone

@elfpipe

You won't get much from me i'm afraid, just starting to understand (and thats an *understatement*) cmake, but here you go...

Just downloaded SDL-main and let your alpha loose on it

and if i do the same command a second thime i get this

What is worse is that there is some kind of "soft-link" added to the build subdirectory, which is called and points to "Development:Porting" (yes, the name of the link or directory is violently using ":" in it`s name...

...i have yet to see how to get rid of it again, without deleting all of my development stuff

...Still, nice to see cmake not immediately crashing on start

@elfpipe

do you have a preference to where the bugreports should go?

here or guthub?

@Hypex

k, thank you

@elfpipe

nice, thanks alot for your work

is there a prebuilt binary somewhere available, or do I need to build it myself...not that i would mind

@hotrod

that only comes up if the update is a paid update and you haven't got a licence bought.

why it needs to be bought for a .01 version jump is beyond me, though

probably wait for the next bigger release (if there will be any more, that is) before paying for something you don't need

@Hypex

so, is the 2.40 "release" considered "stable", at least to the point non-beta users can/should install and use it?

@Rigo

would there be a possibility to share some of *what* is happening "internally" exactly with mere end-users?

i mean, i don't need no nda stuff, but the "outside community" is what this is meant to be aimed for, isn't it?

being a non-betatester nowadays feels like being a windows or linux users...no news, no updates and, with every passing day, not really caring anymore either sadly...

actually, i'm reached the point of, whenever my hardware should die, I'd drop the amiga game completely...with the lack of PR and completely over the board secrecy going on regarding the os, I'd rather not spend any more hard earned money, time and nerves

thank you

@rjd324

i get the same on the x1000.

doing a hard reset software-side with available "reboot" programs doesn't cut it all the time.

i reverted to manually pressing the reboot button.

for me it always seems to stop at the [GOLO] [GOT ] hardware level part in cfe, but i haven't checked for quite some time as the physical reset button works just fine.