Re: Channel Archiver/ Extension Build Question

[John Dobbins <jad@lepp.cornell.edu>]

Ralph, Kay,

Thank you. Once I ran make in the directory extensions/configure 
everything proceeded normally.

John Dobbins

Ralph Lange wrote:
> Hi John,
>
> To me it does actually look like there's one "make" missing in the 
> extensions/configure subdirectory.
>
> Remember that running "make" inside the configure directory creates 
> Makefile snippets that get included during all make runs under this TOP. 
> These Makefile snippets contain (among other things) search path 
> definitions for includes and libraries.
> The pearl script that creates the library path definitions will only add 
> directories that actually contain libraries - this is to avoid adding 
> countless empty directories to the search paths.
>
> If you created librecIoc.a in base after you ran make in 
> extensions/configure, your Makefile snippets might not contain the 
> correct library location within base. As a result, make will try to find 
> librecIoc.a only /locally/, i.e. under this TOP directory. It's not 
> there, and cannot be created locally, so make complains correctly about
> *** No rule to make target `../../../../lib/linux-x86//librecIoc.a
>
> *General rule of thumb:* If a make run yields errors that look like it's 
> trying to find a library locally which should be found elsewhere ...
>
>     * Make sure the path to the external module (in which the library is
>       located) is set correctly in TOP/configure/RELEASE.
>     * Make sure the library does exist in that module at the generic
>       location (e.g. MODULE/lib/ARCHITECTURE)
>     * Do a "make clean", then "make" (or shorter: "make clean all")
>       inside TOP/configure.
>
> If it still doesn't work, well ... shit happens.
>
> Good luck!
> Ralph
>
>
> Kay-Uwe Kasemir wrote:
>
> > Hi:
> >
> > Well, I cannot duplicate your exact setup right now,
> > [...]