[Clam-devel] call for mac powerpc people

[Pau Arumi]

ok, we need to see the linkage command line.
scons is always verbose for clam libs compilation, but it's not the case 
for apps. you need to give a verbose option.
$ scons verbose=1

then double check the -Lpath options and that clam libs are on that 
path, and not on /usr/local/lib for instance.

what else. if you can link but complains on not finding libs when 
running, export DYLD_LIBRARY_PATH=/clamprefix/lib
another push and we are there :-)


Xavier Amatriain wrote:
> I am almost there... now I only  have linking problems in the Network 
> Editor, how can I tell what is exactly linking? I have newest source 
> from svn.
>
> /usr/bin/ld: Undefined symbols:
> CLAM::PortMonitorConfig::DefaultInit()
> CLAM::InPortBase::GetVisuallyConnectedOutPort()
> CLAM::InPortBase::SetVisuallyConnectedOutPort(CLAM::OutPortBase*)
> CLAM::OutPortBase::EndVisuallyConnectedInPorts()
> CLAM::OutPortBase::BeginVisuallyConnectedInPorts()
> CLAM::Network::RenameProcessing(std::basic_string<char, 
> std::char_traits<char>, std::allocator<char> > const&, 
> std::basic_string<char, std::char_traits<char>, std::allocator<char> > 
> const&)
> CLAM::OutControl::AddLink(CLAM::InControl&)
> CLAM::PortMonitor<CLAM::Audio, CLAM::AudioInPort>::Do()
> CLAM::PortMonitor<CLAM::Audio, CLAM::AudioInPort>::PortMonitor()
> CLAM::PANetworkPlayer::PANetworkPlayer()
> CLAM::JACKNetworkPlayer::JACKNetworkPlayer(std::basic_string<char, 
> std::char_traits<char>, std::allocator<char> > const&)
> CLAM::Network::SetPlayer(CLAM::NetworkPlayer*)
> CLAM::JACKNetworkPlayer::IsConnectedToServer() const
> CLAM::Network::GetUnusedName(std::basic_string<char, 
> std::char_traits<char>, std::allocator<char> > const&) const
> CLAM::Network::HasSyncSource() const
> CLAM::Network::GetConfigurationErrors() const
> CLAM::Network::HasMisconfiguredProcessings() const
> CLAM::Network::IsEmpty() const
> CLAM::Network::IsStopped() const
> CLAM::OutControlSender::SendControl(float)
>
> Pau Arumi wrote:
>> Xavier Amatriain wrote:
>>> Wondering, did you run into similar issues or was it smoother in your
>>> case?
>>>   
>> smoother i should say. but only when i decided to use macports and 
>> not fink nor native installs.
>> but the process was quite long because we had to adapt the clam build 
>> system, learn how to install libs in a bundle, etc.
>> ah, the qt4 compilation also lasted several hours in my intel macbook
>>
>> pau
>>
>> ps: i've been updating the wiki on how to solve the kind of problems 
>> you reported.
>