[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Re: SVN Compile Error Under Cygwin: Omnithread St

From: Eric Blossom
Subject: Re: [Discuss-gnuradio] Re: SVN Compile Error Under Cygwin: Omnithread Stuff
Date: Mon, 13 Aug 2007 00:46:56 -0700
User-agent: Mutt/1.5.9i

On Wed, Aug 08, 2007 at 05:10:12PM -0400, Don Ward wrote:
> ----- Original Message ----- 
> From: "Reid N Kleckner" <address@hidden>
> To: "Don Ward" <address@hidden>
> Cc: <address@hidden>
> Sent: Wednesday, August 08, 2007 4:33 PM
> Subject: SVN Compile Error Under Cygwin: Omnithread Stuff
> >So, that advice fixed that problem.  Now I have a problem similar to the 
> >one
> >documented here: http://www.gnuradio.org/trac/ticket/138  I applied the 
> >patch
> >listed there, but my error has not gone away:
> >
> >/usr/src/gnuradio/gnuradio-core/src/lib/swig/gnuradio_swig_py_runtime.cc:(.text+
> >0x325be): undefined reference to `omni_thread::init_t::init_t()'
> >/usr/src/gnuradio/gnuradio-core/src/lib/swig/gnuradio_swig_py_runtime.cc:(.text+
> >0x325dc): undefined reference to `omni_thread::init_t::~init_t()'
> >
> >Is there a similar fix to make it link/include/magic omnithread before 
> >building
> >the rest of the code?
> As far as I know, no agreement has been reached on the right way to handle 
> this, but the attached patches work for me.  Use them instead of the ones 
> from ticket 138.
> -- Don W.

Here's a bit of background on this issue:

Though Don's patches do work around the problem that we see on Cygwin,
they violate the "write it once" principle.  That is, they force us to
encode in multiple places the external dependencies of particular
libraries.  This is just plain ugly and encourages bit rot.
The libtool .la files already contain this information.  It may be
that libool needs some work for Cygin, though I'm not sure about this.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]