Re: [Ltib] Problem in Enabling the Quagga Routing Daemon Built Using LTIB

[Hamilton Vera]

Hi Balu, I am quite curious ... I used to work with Quagga long time
ago to publish BGP routing tables.
Those tables used to grab a huge amount of memory, how are you handling this?

Thanks in advance!



On Wed, Sep 23, 2009 at 10:20 AM, Stuart Hughes <address@hidden> wrote:
> Hi Balu,
>
> I'm pretty sure you can ignore the warning related to libtool.  It's just
> telling you that the shared libraries in your build tree need to be
> re-linked for installation.  Provided the package is normal this will happen
> during the 'make install' section.
>
> What you need to do is removed the extra libtool stuff you added (I think)
> and then debug on the target to try to figure out why the daemons don't
> start.  Is there an option to not daemonise?  it there is use this, maybe
> you'll see some error messages that can give a clue to the runtime problem.
>
> Regards, Stuart
>
> Balu V wrote:
>>
>> Dear All,
>>         I have been working on porting Quagga Dynamic Routing into a power
>> pc board using the LTIB and i have followed the necessary steps for building
>> the package using LTIB as per the "How can I add a completely new package to
>> the root filesystem" documentation given in the Ltibfaq
>> "http://www.bitshrine.org/autodocs/LtibFaq.html#ref_89";. I have been able to
>> configure,make and make install the software package suite sucessfully.  But
>> the routing daemons could not be run in the background mode and enabled at
>> the board level. The same package was found to be working when installed in
>> the PC.
>>
>> Hence after some comparisons between the configure, make and make install
>> at the PC level building and LTIB level building it was found that the make
>> install at the Board had a line
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> "libtool: install: warning: remember to run `libtool --finish
>> /usr/local/lib' " at two places
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> the above line were present in two places even during the issue of the
>> deployment command "./ltib -m scdeploy -p quagga.spec"
>>
>> At the PC level make install at the place of the above line, the following
>> lines were present,
>>
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
>> ----------------------------------------------------------------------
>> Libraries have been installed in:   /usr/local/lib
>>
>> If you ever happen to want to link against installed libraries
>> in a given directory, LIBDIR, you must either use libtool, and
>> specify the full pathname of the library, or use the `-LLIBDIR'
>> flag during linking and do at least one of the following:
>>   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
>>     during execution
>>   - add LIBDIR to the `LD_RUN_PATH' environment variable
>>     during linking
>>   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
>>   - have your system administrator add LIBDIR to `/etc/ld.so.conf'
>>
>> See any operating system documentation about shared libraries for
>> more information, such as the ld(1) and ld.so(8) manual pages.
>> ----------------------------------------------------------------------
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>  Hence after the "./ltib -m scinstall -p quagga.spec" command the libtool
>> command "libtool --finish
>>
>> /usr/local/lib" was issued followed by the deployment command "./ltib -m
>> scdeploy -p quagga.spec"
>> The command "libtool --finish /usr/local/lib"  displayed the following
>> lines.,
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
>> ----------------------------------------------------------------------
>> Libraries have been installed in:   /usr/local/lib
>>
>> If you ever happen to want to link against installed libraries
>> in a given directory, LIBDIR, you must either use libtool, and
>> specify the full pathname of the library, or use the `-LLIBDIR'
>> flag during linking and do at least one of the following:
>>   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
>>     during execution
>>   - add LIBDIR to the `LD_RUN_PATH' environment variable
>>     during linking
>>   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
>>   - have your system administrator add LIBDIR to `/etc/ld.so.conf'
>>
>> See any operating system documentation about shared libraries for
>> more information, such as the ld(1) and ld.so(8) manual pages.
>> ----------------------------------------------------------------------
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> After following the above procedure thinking that the path to the library
>> was missing it was again found that the daemons were not running and
>> enabled,
>> the issue of command "zebra --help" results in "-sh:zebra: not found"
>> where zebra is the routing manager daemon in the quagga.But the issue of the
>> same command in PC lists the help information for the zebra.
>>
>> Kindly provide the solution for the above problem or please let me know
>> about the necessary action that needs to be taken for the warning "libtool:
>> install: warning: remember to run `libtool --finish /usr/local/lib' "  while
>> using the LTIB for building the packages other than available as a part of
>> LTIB.
>>
>> Thanks and Regards
>> Balu
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> LTIB home page: http://ltib.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
>



-- 
Hamilton Vera
int Administrator (char Network[],char ComputationalSystems[])
http://hvera.wordpress.com