Modify ↓
Opened 12 years ago
Closed 12 years ago
#96 closed defect (fixed)
runjson fails with g_thread_init error
Reported by: | Matthias Vogelgesang | Owned by: | Matthias Vogelgesang |
---|---|---|---|
Priority: | major | Milestone: | ufo-core-0.2 |
Component: | ufo-core | Version: | |
Keywords: | Cc: |
Description
Calling runjson
fails:
blume@hasgkssw2ctrec1:tmp$ runjson reco-1.js Ufo-Message: Ufo version 0.2.0 ocl-Message: Number of OpenCL platforms: 1 ocl-Message: --- NVIDIA CUDA --- ocl-Message: Vendor : NVIDIA Corporation ocl-Message: Version : OpenCL 1.1 CUDA 4.2.1 ocl-Message: Device count : 2 ocl-Message: Build options : -cl-mad-enable -cl-nv-verbose -DVENDOR=NVIDIA Ufo-Message: UfoGraph: Created new resource manager 0x238e030 Ufo-Message: UfoPluginManager: Created reader-0x257c040 Ufo-Message: UfoPluginManager: Created writer-0x257e050 Ufo-Message: UfoPluginManager: Created backproject-0x257c110 Ufo-Message: UfoPluginManager: Created fft-0x2581820 Ufo-Message: UfoPluginManager: Created ifft-0x257c1e0 Ufo-Message: UfoPluginManager: Created filter-0x2585030 GLib-ERROR **: The thread system is not yet initialized. aborting... Aborted
This is probably caused by GLib 2.22 used in ScientificLinux 6.3 that is installed at HZG.
Attachments (0)
Note: See
TracTickets for help on using
tickets.
Somehow, a fresh checkout fixed this.