cmake under OpenBSD: rpath support misconfigured

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

cmake under OpenBSD: rpath support misconfigured

Frank Mertens
I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to link my software correctly.
The issue had been described some time ago: http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
I figured out that cmake-2.6.3/Modules/Platform/NetBSD.cmake contains some meaningful (and functional!)
configuration while OpenBSD.cmake is empty.
The solution was simple: cp NetBSD.cmake OpenBSD.cmake.
I think those two files can be kept safely identical.

Thx in advance,
Frank.

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Brad King
Frank Mertens wrote:
> I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to link my software correctly.
> The issue had been described some time ago: http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
> I figured out that cmake-2.6.3/Modules/Platform/NetBSD.cmake contains some meaningful (and functional!)
> configuration while OpenBSD.cmake is empty.
> The solution was simple: cp NetBSD.cmake OpenBSD.cmake.
> I think those two files can be kept safely identical.

Currently OpenBSD.cmake has this line:

  SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERSIONING 1)

The property is documented as:

 FIND_LIBRARY_USE_OPENBSD_VERSIONING
  Whether FIND_LIBRARY should find OpenBSD-style shared libraries.

  This property is a boolean specifying whether the FIND_LIBRARY command
  should find shared libraries with OpenBSD-style versioned extension:
  ".so.<major>.<minor>".  The property is set to true on OpenBSD and
  false on other platforms.

Does this apply to NetBSD also?

FYI, a given platform is officially supported only if someone
contributes a nightly build/test submission to our quality
dashboard:

  http://www.cdash.org/CDash/index.php?project=CMake

If you have spare computing resources at night that can be
spent testing CMake on OpenBSD, we will be happy to get you
set up and to support the platform.

-Brad

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Brad King
Brad King wrote:
> Frank Mertens wrote:
>> The solution was simple: cp NetBSD.cmake OpenBSD.cmake.
>> I think those two files can be kept safely identical.
>
> Currently OpenBSD.cmake has this line:
>
>   SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERSIONING 1)

I've applied the commit below.

-Brad


Use NetBSD to initialize OpenBSD configuration
/cvsroot/CMake/CMake/Modules/Platform/OpenBSD.cmake,v  <--  Modules/Platform/OpenBSD.cmake
new revision: 1.8; previous revision: 1.7

diff --git a/Modules/Platform/OpenBSD.cmake b/Modules/Platform/OpenBSD.cmake
index 422227b..e7df46d 100644
--- a/Modules/Platform/OpenBSD.cmake
+++ b/Modules/Platform/OpenBSD.cmake
@@ -1,3 +1,2 @@
-SET(CMAKE_DL_LIBS "")
+INCLUDE(Platform/NetBSD)
 SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERSIONING 1)
-INCLUDE(Platform/UnixPaths)
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Frank Mertens
In reply to this post by Brad King
Brad King wrote:

> Frank Mertens wrote:
>> I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to link my software correctly.
>> The issue had been described some time ago: http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
>> I figured out that cmake-2.6.3/Modules/Platform/NetBSD.cmake contains some meaningful (and functional!)
>> configuration while OpenBSD.cmake is empty.
>> The solution was simple: cp NetBSD.cmake OpenBSD.cmake.
>> I think those two files can be kept safely identical.
>
> Currently OpenBSD.cmake has this line:
>
>   SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERSIONING 1)
>
> The property is documented as:
>
>  FIND_LIBRARY_USE_OPENBSD_VERSIONING
>   Whether FIND_LIBRARY should find OpenBSD-style shared libraries.
>
>   This property is a boolean specifying whether the FIND_LIBRARY command
>   should find shared libraries with OpenBSD-style versioned extension:
>   ".so.<major>.<minor>".  The property is set to true on OpenBSD and
>   false on other platforms.
>
> Does this apply to NetBSD also?
>
> FYI, a given platform is officially supported only if someone
> contributes a nightly build/test submission to our quality
> dashboard:
>
>   http://www.cdash.org/CDash/index.php?project=CMake
>
> If you have spare computing resources at night that can be
> spent testing CMake on OpenBSD, we will be happy to get you
> set up and to support the platform.

I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.

Being new to ctest, I skimmed through "CMake Testing With CTest"
and triggered "make test". It already passes 99% of all tests
with cmake 2.6.3.

--
Frank

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Frank Mertens
Frank Mertens wrote:

> Brad King wrote:
>> Frank Mertens wrote:
>>> I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to link my software correctly.
>>> The issue had been described some time ago: http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
>>> I figured out that cmake-2.6.3/Modules/Platform/NetBSD.cmake contains some meaningful (and functional!)
>>> configuration while OpenBSD.cmake is empty.
>>> The solution was simple: cp NetBSD.cmake OpenBSD.cmake.
>>> I think those two files can be kept safely identical.
>> Currently OpenBSD.cmake has this line:
>>
>>   SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERSIONING 1)

Yes OpenBSD uses shorter library names:

$ls -c1 /usr/lib
...
libkrb5.so.16.0
libkrb5_p.a
libkrb5_pic.a
libkvm.a
libkvm.so.9.0
libkvm_p.a
libkvm_pic.a
libl.a
libl_p.a
libm.a
libm.so.5.0
libm_p.a
libm_pic.a
libmenu.a
libmenu.so.3.0
libmenu_p.a
libmenu_pic.a
libmilter.a
libmilter.so.2.1
libmilter_p.a
libmilter_pic.a
libncurses.a
libncurses.so.10.0
...
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Bill Hoffman
In reply to this post by Frank Mertens
Frank Mertens wrote:

>
> I'm running OpenBSD on a freshly refurbishes office server.
> It does currently nothing else than running tests for my
> inhouse needs. Give me the pointers and I set it up as testing
> client for cmake, too.
>
> Being new to ctest, I skimmed through "CMake Testing With CTest"
> and triggered "make test". It already passes 99% of all tests
> with cmake 2.6.3.
>
Great,

Can you run the attached ctest script?

To run:

ctest -S generic_cmake.cmake

It should create a directory : $ENV{HOME}/Dashboards/My Tests/.  And
checkout CMake from CVS, and the build it and submit a nightly
dashboard.  Try running it by hand at first.  If that works, then just
create a cronjob that runs sometime after 9:00 EST each day.

-Bill

cmake_minimum_required(VERSION 2.4)
###################################################################
# The values in this section must always be provided
###################################################################
if(NOT compiler)
  set(compiler gcc)
endif(NOT compiler)
if(NOT c_compiler)
  set(c_compiler gcc)
endif(NOT c_compiler)
if(NOT full_compiler)
  set(full_compiler g++)
endif(NOT full_compiler)


find_program(HOSTNAME NAMES hostname)
find_program(UNAME NAMES uname)

# Get the build name and hostname
exec_program(${HOSTNAME} ARGS OUTPUT_VARIABLE hostname)
string(REGEX REPLACE "[/\\\\+<> #]" "-" hostname "${hostname}")

message("HOSTNAME: ${hostname}")
# default to parallel 1
if(NOT DEFINED parallel)
  set(parallel 1)
endif(NOT DEFINED parallel)

# find CVS
find_program(CVS cvs PATHS $ENV{HOME}/bin /vol/local/bin)
if(NOT CVS)
  message(FATAL_ERROR "CVS not found")
endif(NOT CVS)

set(CTEST_UPDATE_COMMAND       ${CVS})
set(CTEST_UPDATE_OPTIONS       "-d -P -A")
macro(getuname name flag)
  exec_program("${UNAME}" ARGS "${flag}" OUTPUT_VARIABLE "${name}")
  string(REGEX REPLACE "[/\\\\+<> #]" "-" "${name}" "${${name}}")
  string(REGEX REPLACE "^(......|.....|....|...|..|.).*" "\\1" "${name}" "${${name}}")
endmacro(getuname)

getuname(osname -s)
getuname(osver  -v)
getuname(osrel  -r)
getuname(cpu    -m)
if("${osname}" MATCHES Darwin)
  find_program(SW_VER sw_vers)
  execute_process(COMMAND "${SW_VER}" -productVersion OUTPUT_VARIABLE osver)
  string(REPLACE "\n" "" osver "${osver}")
  set(osname "MacOSX")
  set(osrel "")
  if("${cpu}" MATCHES "Power")
    set(cpu "ppc")
  endif("${cpu}" MATCHES "Power")
endif("${osname}" MATCHES Darwin)

if(NOT compiler)
  message(FATAL_ERROR "compiler must be set")
endif(NOT compiler)

 
set(BUILDNAME "${osname}${osver}${osrel}${cpu}-${compiler}")
message("BUILDNAME: ${BUILDNAME}")

# this is the cvs module name that should be checked out
set (CTEST_MODULE_NAME CMake)
set (CTEST_DIR_NAME "${CTEST_MODULE_NAME}CVS")

# Settings:
message("NOSPACES = ${NOSPACES}")
if(NOSPACES)
  set(CTEST_DASHBOARD_ROOT    "$ENV{HOME}/Dashboards/MyTests-${BUILDNAME}")
else(NOSPACES)
  set(CTEST_DASHBOARD_ROOT    "$ENV{HOME}/Dashboards/My Tests-${BUILDNAME}")
endif(NOSPACES)
set(CTEST_SITE              "${hostname}")
set(CTEST_BUILD_NAME        "${BUILDNAME}")
set(CTEST_TEST_TIMEOUT           "1500")

# CVS command and the checkout command
if(NOT EXISTS "${CTEST_DASHBOARD_ROOT}/${CTEST_DIR_NAME}")
  set(CTEST_CHECKOUT_COMMAND     "\"${CTEST_UPDATE_COMMAND}\" -q -z3 -d:pserver:[hidden email]:/cvsroot/CMake co -d \"${CTEST_DIR_NAME}\" -D yesterday ${CTEST_MODULE_NAME}")
endif(NOT EXISTS "${CTEST_DASHBOARD_ROOT}/${CTEST_DIR_NAME}")

# Set the generator and build configuration
if(NOT DEFINED CTEST_CMAKE_GENERATOR)
  set(CTEST_CMAKE_GENERATOR      "Unix Makefiles")
endif(NOT DEFINED CTEST_CMAKE_GENERATOR)
set(CTEST_PROJECT_NAME         "CMake")
set(CTEST_BUILD_CONFIGURATION  "Release")

# Extra special variables
set(ENV{DISPLAY}             "")
if(CTEST_CMAKE_GENERATOR MATCHES Makefiles)
  set(ENV{CC}                  "${c_compiler}")
  set(ENV{FC}                  "${f_compiler}")
  set(ENV{CXX}                 "${full_compiler}")
endif(CTEST_CMAKE_GENERATOR MATCHES Makefiles)

#----------------------------------------------------------------------------------
# Should not need to edit under this line
#----------------------------------------------------------------------------------

# if you do not want to use the default location for a
# dashboard then set this variable to the directory
# the dashboard should be in
make_directory("${CTEST_DASHBOARD_ROOT}")
# these are the the name of the source and binary directory on disk.
# They will be appended to DASHBOARD_ROOT
set(CTEST_SOURCE_DIRECTORY  "${CTEST_DASHBOARD_ROOT}/${CTEST_DIR_NAME}")
set(CTEST_BINARY_DIRECTORY  "${CTEST_SOURCE_DIRECTORY}-${CTEST_BUILD_NAME}")
if(NOT SKIP_CTEST_CONFIGURE_COMMAND)
  set(CTEST_CONFIGURE_COMMAND "\"${CTEST_SOURCE_DIRECTORY}/bootstrap\"")
endif(NOT SKIP_CTEST_CONFIGURE_COMMAND)
set(CTEST_NOTES_FILES  "${CTEST_NOTES_FILES}"
  "${CMAKE_CURRENT_LIST_FILE}"
  )

# check for parallel
if(parallel GREATER 1)
  if(NOT CTEST_BUILD_COMMAND)
    set(CTEST_BUILD_COMMAND "make -j${parallel} -i")
  endif(NOT CTEST_BUILD_COMMAND)

  if(NOT SKIP_CTEST_CONFIGURE_COMMAND)
    set(CTEST_CONFIGURE_COMMAND
      "\"${CTEST_SOURCE_DIRECTORY}/bootstrap\" --parallel=${parallel}")
  endif(NOT SKIP_CTEST_CONFIGURE_COMMAND)

  message("Use parallel build")
  message("CTEST_BUILD_COMMAND: ${CTEST_BUILD_COMMAND}")
  message("CTEST_CONFIGURE_COMMAND: ${CTEST_CONFIGURE_COMMAND}")
endif(parallel GREATER 1)

##########################################################################
# wipe the binary dir
message("Remove binary directory...")
ctest_empty_binary_directory("${CTEST_BINARY_DIRECTORY}")

message("CTest Directory: ${CTEST_DASHBOARD_ROOT}")
message("Initial checkout: ${CTEST_CVS_CHECKOUT}")
message("Initial cmake: ${CTEST_CMAKE_COMMAND}")
message("CTest command: ${CTEST_COMMAND}")

# this is the initial cache to use for the binary tree, be careful to escape
# any quotes inside of this string if you use it
file(WRITE "${CTEST_BINARY_DIRECTORY}/CMakeCache.txt" "
SITE:STRING=${hostname}
BUILDNAME:STRING=${BUILDNAME}
DART_ROOT:PATH=
CVSCOMMAND:FILEPATH=${CTEST_UPDATE_COMMAND}
DROP_METHOD:STRING=http
CTEST_TEST_CTEST:BOOL=1
CVS_UPDATE_OPTIONS:STRING=${CTEST_UPDATE_OPTIONS}
DART_TESTING_TIMEOUT:STRING=${CTEST_TEST_TIMEOUT}
")

message("Start dashboard...")
ctest_start(Nightly)
message("  Update")
ctest_update(SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE res)
message("  Configure")
ctest_configure(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)
message("read custom files after configure")
ctest_read_custom_files("${CTEST_BINARY_DIRECTORY}")
message("  Build")
ctest_build(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)
message("  Test")
ctest_test(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)
message("  Submit")
ctest_submit(RETURN_VALUE res)
message("  All done")



_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Frank Mertens
Bill Hoffman wrote:

> Frank Mertens wrote:
>
>>
>> I'm running OpenBSD on a freshly refurbishes office server.
>> It does currently nothing else than running tests for my
>> inhouse needs. Give me the pointers and I set it up as testing
>> client for cmake, too.
>>
>> Being new to ctest, I skimmed through "CMake Testing With CTest"
>> and triggered "make test". It already passes 99% of all tests
>> with cmake 2.6.3.
>>
>
> Great,
>
> Can you run the attached ctest script?
>
> To run:
>
> ctest -S generic_cmake.cmake
>
> It should create a directory : $ENV{HOME}/Dashboards/My Tests/.  And
> checkout CMake from CVS, and the build it and submit a nightly
> dashboard.  Try running it by hand at first.  If that works, then just
> create a cronjob that runs sometime after 9:00 EST each day.
>

Oh,... well I just run 'make Experimential' on the CVS source an hour ago.
It passed all tests! But I fear the dart stuff failed to send a report,
got some strange errors about '/proc/cpuinfo' missing. Right OpenBSD
has sysctl and no '/proc'. I probably have to stick my fingers into the
source code. A first small peak into it shows that there is Apple/FreeBSD
style sysctl support in kwsys/SystemInformation. Maybe just modifying
some macros and those part works, too?

$ uname -ap
OpenBSD blackbox.cyblogic.com 4.5 GENERIC#1749 i386 Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class)
$ sysctl -a|grep cpu
kern.ccpu=1948
hw.ncpu=1
hw.cpuspeed=499
machdep.cpuvendor=AuthenticAMD
machdep.cpuid=1442
machdep.cpufeature=8956221
$

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Frank Mertens
In reply to this post by Bill Hoffman
Bill Hoffman wrote:

> Frank Mertens wrote:
>
>>
>> I'm running OpenBSD on a freshly refurbishes office server.
>> It does currently nothing else than running tests for my
>> inhouse needs. Give me the pointers and I set it up as testing
>> client for cmake, too.
>>
>> Being new to ctest, I skimmed through "CMake Testing With CTest"
>> and triggered "make test". It already passes 99% of all tests
>> with cmake 2.6.3.
>>
>
> Great,
>
> Can you run the attached ctest script?
>
> To run:
>
> ctest -S generic_cmake.cmake
>

Ok, I try this one next.
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Frank Mertens
In reply to this post by Bill Hoffman
Bill Hoffman wrote:

> Frank Mertens wrote:
>
>>
>> I'm running OpenBSD on a freshly refurbishes office server.
>> It does currently nothing else than running tests for my
>> inhouse needs. Give me the pointers and I set it up as testing
>> client for cmake, too.
>>
>> Being new to ctest, I skimmed through "CMake Testing With CTest"
>> and triggered "make test". It already passes 99% of all tests
>> with cmake 2.6.3.
>>
>
> Great,
>
> Can you run the attached ctest script?
>
> To run:
>
> ctest -S generic_cmake.cmake
>

It fails within seconds...

$ ctest -version
ctest version 2.6-patch 3
$ ctest -S generic_cmake.cmake
HOSTNAME: blackbox.cyblogic.com
BUILDNAME: OpenBSGENERI4.5i386-gcc
NOSPACES =
Remove binary directory...
CTest Directory: /home/guest/Dashboards/My Tests-OpenBSGENERI4.5i386-gcc
Initial checkout:
Initial cmake:
CTest command:
Start dashboard...
  Update
Abort trap (core dumped)
$ echo $?
134
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Frank Mertens
Frank Mertens wrote:

> Bill Hoffman wrote:
>> Frank Mertens wrote:
>>
>>> I'm running OpenBSD on a freshly refurbishes office server.
>>> It does currently nothing else than running tests for my
>>> inhouse needs. Give me the pointers and I set it up as testing
>>> client for cmake, too.
>>>
>>> Being new to ctest, I skimmed through "CMake Testing With CTest"
>>> and triggered "make test". It already passes 99% of all tests
>>> with cmake 2.6.3.
>>>
>> Great,
>>
>> Can you run the attached ctest script?
>>
>> To run:
>>
>> ctest -S generic_cmake.cmake
>>
>
> It fails within seconds...
>
> $ ctest -version
> ctest version 2.6-patch 3
> $ ctest -S generic_cmake.cmake
> HOSTNAME: blackbox.cyblogic.com
> BUILDNAME: OpenBSGENERI4.5i386-gcc
> NOSPACES =
> Remove binary directory...
> CTest Directory: /home/guest/Dashboards/My Tests-OpenBSGENERI4.5i386-gcc
> Initial checkout:
> Initial cmake:
> CTest command:
> Start dashboard...
>   Update
> Abort trap (core dumped)
> $ echo $?
> 134

Launched it again in gdb, maybe helps...

(gdb) r -S generic_cmake.cmake
Starting program: /home/frank/cmake-2.6.3/bin/ctest -S generic_cmake.cmake
HOSTNAME: blackbox.cyblogic.com
BUILDNAME: OpenBSGENERI4.5i386-gcc
NOSPACES =
Remove binary directory...
CTest Directory: /home/guest/Dashboards/My Tests-OpenBSGENERI4.5i386-gcc
Initial checkout:
Initial cmake:
CTest command:
Start dashboard...
  Update

Program received signal SIGABRT, Aborted.
0x00c23f81 in kill () from /usr/lib/libc.so.50.1
(gdb) where
#0  0x00c23f81 in kill () from /usr/lib/libc.so.50.1
#1  0x00c55114 in __stack_smash_handler (func=0x3c0124a0 "virtual int cmCTestUpdateHandler::ProcessHandler()",
    damaged=701771816) at /usr/src/lib/libc/sys/stack_protector.c:89
#2  0x1c088cdc in cmCTestUpdateHandler::ProcessHandler ()
#3  0x1c08ee0d in cmCTestHandlerCommand::InitialPass ()
#4  0x1c05c9e1 in cmCommand::InvokeInitialPass ()
#5  0x1c0e1c74 in cmMakefile::ExecuteCommand ()
#6  0x1c0e3009 in cmMakefile::ReadListFile ()
#7  0x1c0580f6 in cmCTestScriptHandler::ReadInScript ()
#8  0x1c059075 in cmCTestScriptHandler::RunConfigurationScript ()
#9  0x1c056744 in cmCTestScriptHandler::ProcessHandler ()
#10 0x1c019da6 in cmCTest::Run ()
#11 0x1c00761c in main ()
(gdb)

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Bill Hoffman
In reply to this post by Frank Mertens
Frank Mertens wrote:

> Bill Hoffman wrote:
>> Frank Mertens wrote:
>>
>>> I'm running OpenBSD on a freshly refurbishes office server.
>>> It does currently nothing else than running tests for my
>>> inhouse needs. Give me the pointers and I set it up as testing
>>> client for cmake, too.
>>>
>>> Being new to ctest, I skimmed through "CMake Testing With CTest"
>>> and triggered "make test". It already passes 99% of all tests
>>> with cmake 2.6.3.
>>>
>> Great,
>>
>> Can you run the attached ctest script?
>>
>> To run:
>>
>> ctest -S generic_cmake.cmake
>>
>
> It fails within seconds...
>
> $ ctest -version
> ctest version 2.6-patch 3
> $ ctest -S generic_cmake.cmake
> HOSTNAME: blackbox.cyblogic.com
> BUILDNAME: OpenBSGENERI4.5i386-gcc
> NOSPACES =
> Remove binary directory...
> CTest Directory: /home/guest/Dashboards/My Tests-OpenBSGENERI4.5i386-gcc
> Initial checkout:
> Initial cmake:
> CTest command:
> Start dashboard...
>   Update
> Abort trap (core dumped)
> $ echo $?
> 134

Can you run ctest under gdb and find out where this crash is?  You could
also try ctest 2.6.4 maybe it is something that is fixed.


Thanks.

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: cmake under OpenBSD: rpath support misconfigured

Bill Hoffman
In reply to this post by Frank Mertens
Frank Mertens wrote:

> Oh,... well I just run 'make Experimential' on the CVS source an hour ago.
> It passed all tests! But I fear the dart stuff failed to send a report,
> got some strange errors about '/proc/cpuinfo' missing. Right OpenBSD
> has sysctl and no '/proc'. I probably have to stick my fingers into the
> source code. A first small peak into it shows that there is Apple/FreeBSD
> style sysctl support in kwsys/SystemInformation. Maybe just modifying
> some macros and those part works, too?
>
> $ uname -ap
> OpenBSD blackbox.cyblogic.com 4.5 GENERIC#1749 i386 Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class)
> $ sysctl -a|grep cpu
> kern.ccpu=1948
> hw.ncpu=1
> hw.cpuspeed=499
> machdep.cpuvendor=AuthenticAMD
> machdep.cpuid=1442
> machdep.cpufeature=8956221
> $
>
> _______________________

It should still submit, but I don't see anything on the dashboard.  I
wonder if there is a network error.

Can you do

cd build-tree
ctest -D Experimental -VV --debug >& out

Then send me the out file off the list.  I think we are getting into
stuff that is not generally an issue for the whole list... :)  I will
post results once we figure out what is wrong.

Thanks.


-Bill
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake