Re: [Cpu-users] Compile Errors

[<sup...@su...>]

My apologies on the email formatting.  I've turned of HTML formatting so
this should look nicer.

Anyhow, I've successfully compiled and installed CPU, but now get the
following when I simply enter in the command 'cpu' (no arguments):

dually:~# cpu
CPU_loadLibrary: dlopen(libcpu_ldap.so, RTLD_NOW) failed.
CPU_loadLibrary: libcpu_ldap.so: cannot open shared object file: No such
file or directory
There was an error loading the ldap library. Exiting.
dually:~#

Any ideas?

Ben

> Hi Ben,
> I forgot to add parser.h as an EXTRA_SOURCE for make dist. This has been
> fixed, you can now grab a new tarball from sourceforge. In addition, the
> body of your emails are arriving as an attachment, which is rather
> annoying :-)
>
> -Blake
>
> Whatchu talkin' 'bout, Willis?
>> I keep getting the following errors when trying to compile the latest
>> 1.3.99a version of CPU.  My system is a Debian Woody 3.0 and I'm doing
>> a default configure and make (no flags or options).
>>
>> parser.c:35: util/parser.h: No such file or directory
>> make[3]: *** [parser.lo] Error 1
>> make[3]: Leaving directory `/stuff/cpu-1.3.99a/src/util'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/stuff/cpu-1.3.99a/src/util'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/stuff/cpu-1.3.99a/src'
>> make: *** [all-recursive] Error 1
>>
>>
>> Ben
>
>
> --
> Blake Matheny           "... one of the main causes of the fall of the
> bma...@pu...      Roman Empire was that, lacking zero, they had
> http://www.dbaseiv.net   no way to indicate successful termination of
> http://ovmj.org/GNUnet/  their C programs." --Robert Firth