ocio_core_tests linking issue on Ubuntu 10.10


Andrew Hunter <and...@...>
 

Hey everyone,

I've encountered a linker issue on Ubuntu 10.10 with ocio-0.7.0. I was
wondering if anyone could shed some light on whats going on?


Linking CXX executable ocio_core_tests
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crt1.o: In
function `_start':
(.text+0x20): undefined reference to `main'
collect2: ld returned 1 exit status
make[2]: *** [src/core_tests/ocio_core_tests] Error 1
make[1]: *** [src/core_tests/CMakeFiles/ocio_core_tests.dir/all] Error 2
make: *** [all] Error 2

Has anyone else been able to successfully build 0.7 on Ubuntu?

Cheers,

Andrew


Jeremy Selan <jeremy...@...>
 

I haven't seen that issue before, but it looks like it's related to
the testing framework (which relies on boost). I'll try to get an
Ubuntu machine up in the next few days for testing.

But... in the meantime, you can disable compilation of the testing app
by editing CMakeList.txt (in the root dir), and commenting out the
following line: (Add a "#" to make the line a comment).

#add_subdirectory (src/core_tests)

I can add this as a command-line configuration option if the hack has
to live beyond the week.

Please let me know if compilation succeeds with this line commented out?

Thanks!

-- Jeremy

On Tue, Nov 2, 2010 at 9:37 AM, Andrew Hunter <and...@aehunter.net> wrote:
Hey everyone,

I've encountered a linker issue on Ubuntu 10.10 with ocio-0.7.0. I was
wondering if anyone could shed some light on whats going on?


Linking CXX executable ocio_core_tests
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crt1.o: In
function `_start':
(.text+0x20): undefined reference to `main'
collect2: ld returned 1 exit status
make[2]: *** [src/core_tests/ocio_core_tests] Error 1
make[1]: *** [src/core_tests/CMakeFiles/ocio_core_tests.dir/all] Error 2
make: *** [all] Error 2

Has anyone else been able to successfully build 0.7 on Ubuntu?

Cheers,

Andrew


Est <rame...@...>
 

I had the same problem. It happens when you link to the
dynamic version of boost's test libraries.
You need to build / install boost test as static libraries
and point CMake to them.

Est.

On Nov 2, 11:23 pm, Jeremy Selan <jeremy...@gmail.com> wrote:
I haven't seen that issue before, but it looks like it's related to
the testing framework (which relies on boost).  I'll try to get an
Ubuntu machine up in the next few days for testing.

But... in the meantime, you can disable compilation of the testing app
by editing CMakeList.txt (in the root dir), and commenting out the
following line:  (Add a "#" to make the line a comment).

#add_subdirectory (src/core_tests)

I can add this as a command-line configuration option if the hack has
to live beyond the week.

Please let me know if compilation succeeds with this line commented out?

Thanks!

-- Jeremy

On Tue, Nov 2, 2010 at 9:37 AM, Andrew Hunter <and...@aehunter.net> wrote:
Hey everyone,
I've encountered a linker issue on Ubuntu 10.10 with ocio-0.7.0. I was
wondering if anyone could shed some light on whats going on?
Linking CXX executable ocio_core_tests
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crt1.o: In
function `_start':
(.text+0x20): undefined reference to `main'
collect2: ld returned 1 exit status
make[2]: *** [src/core_tests/ocio_core_tests] Error 1
make[1]: *** [src/core_tests/CMakeFiles/ocio_core_tests.dir/all] Error 2
make: *** [all] Error 2
Has anyone else been able to successfully build 0.7 on Ubuntu?
Cheers,
Andrew


Andrew Hunter <and...@...>
 

Hey Jeremy,

On Tue, Nov 2, 2010 at 6:23 PM, Jeremy Selan <jeremy...@gmail.com> wrote:
I haven't seen that issue before, but it looks like it's related to
the testing framework (which relies on boost).  I'll try to get an
Ubuntu machine up in the next few days for testing.

But... in the meantime, you can disable compilation of the testing app
by editing CMakeList.txt (in the root dir), and commenting out the
following line:  (Add a "#" to make the line a comment).

#add_subdirectory (src/core_tests)
The build completes successfully commenting out that line.


I can add this as a command-line configuration option if the hack has
to live beyond the week.
If things are as Est mentioned, then I think this is a good idea. It
would be preferable to use the distribution's supplied boost rather
than having to build it locally.

Cheers!

Andrew