CMake 3.29 Native (OS4)

	Bottom Previous Topic Next Topic
Register To Post

« 1 2 3 4 (5) 6 »

jabirulo

Re: CMake 3.29 Native (OS4)

Posted on: 9/28 15:55 #81

Just can't stay away

@elfpipe

same problem:


#assign

Volúmenes:

BASURA [Montado]

Devel [Montado]

...

Workbench [Montado]



Asignaciones:

AMISSL         <DEVS:AmiSSL>

C              Workbench:C

CLASSES        Workbench:Classes

CLIPS          RAM Disk:Clipboards

cmake-amiga    Devel:cmake-amiga

...



#cd build/

#cmake ..

-- CMAKE_HOST_SYSTEM_VERSION : 53.18

-- The C compiler identification is GNU 11.2.0

-- The CXX compiler identification is GNU 11.2.0

-- Detecting C compiler ABI info

CMake Error: Generator: execution of make failed. Make command was: /Devel/cmake-amiga/bin/cmake -E env VERBOSE=1 /SDK/C/gmake -f Makefile cmTC_629ed/fast

-- Detecting C compiler ABI info - failed

-- Check for working C compiler: /SDK/gcc/bin/gcc

CMake Error: Generator: execution of make failed. Make command was: /Devel/cmake-amiga/bin/cmake -E env VERBOSE=1 /SDK/C/gmake -f Makefile cmTC_9582e/fast

-- Check for working C compiler: /SDK/gcc/bin/gcc - broken

CMake Error at /Devel/cmake-amiga/share/cmake-3.29/Modules/CMakeTestCCompiler.cmake:67 (message):

  The C compiler



    "/SDK/gcc/bin/gcc"



  is not able to compile a simple test program.



  It fails with the following output:



    Change Dir: '/Devel/SDK/ejemplos/SDL2/game/build/CMakeFiles/CMakeScratch/TryCompile-TXPYHS'

    

    Run Build Command(s): /Devel/cmake-amiga/bin/cmake -E env VERBOSE=1 /SDK/C/gmake -f Makefile cmTC_9582e/fast

    SIGHUP

    Generator: execution of make failed. Make command was: /Devel/cmake-amiga/bin/cmake -E env VERBOSE=1 /SDK/C/gmake -f Makefile cmTC_9582e/fast

    



  



  CMake will not be able to correctly generate this project.

Call Stack (most recent call first):

  CMakeLists.txt:3 (project)





-- Configuring incomplete, errors occurred!

But will do ASAP a new SDK install and see if I "missed" something.

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 9/28 20:31 #82

Home away from home

@jabirulo

I *think* you may still have the wrong path set up

from the cmake amigaos4 readme
Quote:

setenv PATH /SDK/gcc/bin:/SDK/C:/SDK/local/C:/cmake-amiga/bin
path cmake-amiga:bin ADD

also make sure that the old path to 3.29 is gone completely...

Best way to use them without using the old path setup is to do a reboot

because, if you look at your last CMake error it's still pointing to the old cmake3.29 install:
Quote:

CMake Error at /Devel/cmake-amiga/share/cmake-3.29/Modules/CMakeTestCCompiler.cmake:67 (message):
The C compiler

"/SDK/gcc/bin/gcc"

is not able to compile a simple test program.

--

game box/art scans
scummvm infrequent builds

jabirulo

Re: CMake 3.29 Native (OS4)

Posted on: 9/29 10:03 #83

Just can't stay away

@Raziel

Old cmake 3.29 ¿:-/

Sorry don't get it, v3.29 (beta3) is latest version and package has such directory struct:


#list cmake-amiga:share/

Directory "cmake-amiga:share" on Sunday 29-Sep-24

cmake-3.29                      Dir ----rwed Tuesday    18:37:43

aclocal                         Dir ----rwed Tuesday    18:41:05

bash-completion                 Dir ----rwed Tuesday    18:41:05

3 directories - 6 used blocks

#

My "setup" is:


#Devel:cmake-amiga/

#type cmake_init 

Assign cmake-amiga: Devel:cmake-amiga

SetEnv PATH /SDK/gcc/bin:/SDK/C:/SDK/local/C:/cmake-amiga/bin

Path cmake-amiga:bin ADD

Stack 1000000

#bin/cmake --version

cmake version 3.29.3



CMake suite maintained and supported by Kitware (kitware.com/cmake).

#

elfpipe

Re: CMake 3.29 Native (OS4)

Posted on: 9/29 11:20 #84

Just can't stay away

@jabirulo

Your setup looks correct. I don't know what to suggest. Maybe a run with snoopy?

Edited by elfpipe on 2024/9/29 11:41:20

elfpipe

Re: CMake 3.29 Native (OS4)

Posted on: 9/29 16:42 #85

Just can't stay away

@jabirulo

I have changed my theory : I believe now, that it is your compiler, that fails to build an executable. The step that fails would be some call on try_compile() (in the ABI detection script). This could potentially happen, if the setup you are working with requires, say, "-athread=native" in order to compile (and not fail).

Could you please try and change the compiler version with the

SDK:Tools/set_defGCC

tool?

EDIT: It could also potentially be caused by the spelling of symlink names in the version control of the SDK. This might be different in different version.

elfpipe

Re: CMake 3.29 Native (OS4)

Posted on: 9/29 17:28 #86

Just can't stay away

@thread

I have not fixed case sensitivity issues in cmake, since it never came up in my tests. I will try and find time to address this issue. In the meantime, be aware, that spelling (upper-lower case) in path names might be the subject of success/failure of calls during generation/build.

joerg

Re: CMake 3.29 Native (OS4)

Posted on: 9/29 17:39 #87

Just can't stay away

@elfpipe
Quote:

I have not fixed case sensitivity issues in cmake, since it never came up in my tests. I will try and find time to address this issue.

Don't do that, it may break more than it fixes.
For example I could build OWB on AmigaOS 4.x only if the sources were on case sensitive formatted SFS partitions.
On any other file system, default on AmigaOS is upper=lower case for the ASCII chars, it failed because it had different files with the same names where only the case of some chars differed.

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 9/29 23:04 #88

Home away from home

@jabirulo

yeah, just ignore me, wrong glasses

--

game box/art scans
scummvm infrequent builds

MartinW

Re: CMake 3.29 Native (OS4)

Posted on: 9/30 2:06 #89

Not too shy to talk

This doesn't particularly help anyone with their troubles, but I did manage to get 20 minutes just now to update my copy of cmake and can confirm that for me, everything still works as it did before. I haven't had a chance to progress to a more complex program yet - real life getting in the way!

Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 10/3 12:39 #90

Home away from home

@elfpipe

a first test with a small project shows that it works for me now

one policy warning (more on a bigger project) but that's it.
I take it those warning are the same as with compiler warnings, i can suppress them with flags, but it would be better to fix them?


CMake Deprecation Warning at CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):

  Compatibility with CMake < 3.5 will be removed from a future version of

  CMake.



  Update the VERSION argument <min> value or use a ...<max> suffix to tell

  CMake that the project does not need compatibility with older versions.





-- CMAKE_HOST_SYSTEM_VERSION : 53.18

-- The C compiler identification is GNU 11.3.0

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Check for working C compiler: /SDK/gcc/bin/gcc - skipped

-- Detecting C compile features

-- Detecting C compile features - done

-- Configuring done (8.8s)

CMake Warning (dev) at src/CMakeLists.txt:3 (add_library):

  Policy CMP0115 is not set: Source file extensions must be explicit.  Run

  "cmake --help-policy CMP0115" for policy details.  Use the cmake_policy

  command to set the policy and suppress this warning.



  File:



    /Development/Porting/musepack/libreplaygain_r475/src/gain_analysis.c

This warning is for project developers.  Use -Wno-dev to suppress it.



-- Generating done (0.2s)

-- Build files have been written to: /Development/Porting/musepack/libreplaygain_r475/build

Thanks a lot

Now, off to play

edit:

I have yet to find a way to reproduce it, but after some time all the cmake binaries turn non-executable...i get the error message that this binary is not exectuable (all three cmake, ctest and cpack)

Edited by Raziel on 2024/10/3 13:27:41

--

game box/art scans
scummvm infrequent builds

elfpipe

Re: CMake 3.29 Native (OS4)

Posted on: 10/4 15:33 #91

Just can't stay away

@Raziel

Quote:

I take it those warning are the same as with compiler warnings,

Those warnings should be there. It indicates, that it is an old project and should be updated.

Quote:

i get the error message that this binary is not exectuable (all three cmake, ctest and cpack)

Have you checked your memory consumption? There is a memory leak that we haven't trapped yet. More on this latter.

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 10/4 15:54 #92

Home away from home

@elfpipe

nope, I didn't, but eill do now...it happened mostly after jumping between two projects

--

game box/art scans
scummvm infrequent builds

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 10/4 17:01 #93

Home away from home

@elfpipe

yep, that seems to be it, eats away upto 770 MB, i still should have roughly the same left, but it looks like it's either hellishly fragmented or the display is wrong.

once the "file is not executable" comes up not even odyssey starts up anymore

--

game box/art scans
scummvm infrequent builds

elfpipe

Re: CMake 3.29 Native (OS4)

Posted on: 10/4 17:39 #94

Just can't stay away

@Raziel

That'a all good fun. Maybe we will have time this weekend to trap the memory gnome. Good to see, though, that the software actually runs somewhere in the outer universe.

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 10/4 18:53 #95

Home away from home

@elfpipe

take your time

--

game box/art scans
scummvm infrequent builds

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 10/5 11:11 #96

Home away from home

@elfpipe

found another problem
It seems to add superflous slashes to pathes

this is the line i'm using:


cmake .. -DCMAKE_SYSTEM_NAME=Generic -DCMAKE_SYSTEM_VERSION=1 -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=/development/scripting/cmake/dynamic.cmake

and this is the output from cmake


-- CMAKE_HOST_SYSTEM_VERSION : 53.18

-- The C compiler identification is GNU 11.3.0

-- The CXX compiler identification is GNU 11.3.0

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Check for working C compiler: ///SDK/gcc/bin/ppc-amigaos-gcc - skipped

-- Detecting C compile features

-- Detecting C compile features - done

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- Check for working CXX compiler: ///SDK/gcc/bin/ppc-amigaos-g++ - skipped

-- Detecting CXX compile features

-- Detecting CXX compile features - done

Not sure if this is a problem later on, since it gets detected nonetheless, but i'm hesistant to say there isn' t a problem.

Also and opt: device is being asked for, cancelling this lets me move on

--

game box/art scans
scummvm infrequent builds

elfpipe

Re: CMake 3.29 Native (OS4)

Posted on: 10/5 16:41 #97

Just can't stay away

@Raziel

Quote:

It seems to add superflous slashes to pathes

I have seen this with certain builds, and I am not sure, why it happens. It needs to be fixed of course.

Quote:

Also and opt: device is being asked for,

I don't think there is an invocation of /opt/ in the binary, so this is probably from some script in the Modules/ directory. I have touched absolutely none of these, someone else has a project going doing generic updates there.

EDIT: I probably accidentally included a reference to /opt/ in the build command for cmake itself. This would explain, that it comes up with a more or less simple build.

kas1e

Re: CMake 3.29 Native (OS4)

Posted on: 10/5 17:55 #98

Home away from home

@elfpipe
This huge memory leak Raziel meet with looks very similar with one we have with clib4 build of gdb: loading of some more or less big binaries cause full memory eating and "memory exhaused" words. Can be well related to calloc/realloc ?

Join us to improve dopus5!
AmigaOS4 on youtube

Raziel

Re: CMake 3.29 Native (OS4)

Posted on: 10/5 21:29 #99

Home away from home

@kas1e
@elfpipe

mmh, maybe the memory leak doesn't stem from cmake then, it could very well be coming from clib4(.library) as well(?)

--

game box/art scans
scummvm infrequent builds

kas1e

Re: CMake 3.29 Native (OS4)

Posted on: 10/6 6:09 #100

Home away from home

@Raziel
Pretty possible. At least i aware of one issue causing small leaks in every clib4 apps:
https://github.com/AmigaLabs/clib4/issues/210

As well as both cmake and gdb use pipes, and with both of them we have on exit not cleared pipe-handlers left in dos processes. This one also cause small memory leak.

And, there some another strange problem with memory happens which by amount of leaked memory looks like same you had with cmake tests, and in gdb it easy reproduced like this : https://github.com/AmigaLabs/binutils-gdb/issues/23

Join us to improve dopus5!
AmigaOS4 on youtube

Register To Post	« 1 2 3 4 (5) 6 »
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 2 ( 0 members and 2 Anonymous Users )