The libHBAAPI and libhbalinux .pc files are under /usr/lib64 so I used
environment variable PKG_CONFIG_PATH to this directory and it helped to
locate these files.
The problem is with the lldpad.
I succeed to perform : apt-get install lldpad
I use rpm since it is in the INSTALL instructions
The problem is that there is no .pc for it so I can't configure the env.
variable PKG_CONFIG_PATH
I also don't know what should be in LLDPAD_LIBS or LLDPAD_CFLAGS instead
...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for HBAAPI... yes
checking for LLDPAD... no
configure: error: Package requirements (lldpad >= 0.9.43) were not met:
No package 'lldpad' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LLDPAD_CFLAGS
and LLDPAD_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


On Mon, Jul 15, 2013 at 8:16 PM, Love, Robert W <[email protected]>wrote:

> > -----Original Message-----
> > From: [email protected] [mailto:fcoe-devel-
> > [email protected]] On Behalf Of Neil Horman
> > Sent: Monday, July 15, 2013 10:02 AM
> > To: Doron Kenneth
> > Cc: [email protected]
> > Subject: Re: [Open-FCoE] Installing fcoe-utils
> >
> > On Mon, Jul 15, 2013 at 02:14:51PM +0300, Doron Kenneth wrote:
> > > I receive an error: unable to locate package lldpad-devel
> > >
> > Then contact your distribution maintainers to see where the lldpad-devel
> > package is, or what its name is (lldpad-devel is the fedora name).
> >
> > Speaking of which, Why are you using rpm on Ubuntu?  shouldn't you be
> > using deb (or whatever Canonical tool replaces deb)?  Or have they
> > converted to rpm or something?
>
> I would guess that he's using rpm because it's part of the INSTALL
> instructions,
> which were written against Fedora.
>
> 1) Bootstrap, configure, make and make install
>    # ./bootstrap.sh
>    # rpm --eval "%configure" | sh
>    # make
>    # make install
>
> This was just a nice way to get the default options for './configure'.
>
> When I went to build fcoe-utils.git on Ubuntu I installed rpm (was
> surprised it
> was a package) and then continued with the instructions. Everything went
> well until I ran into the lib64 vs lib issue. I looked at the output of
>
> rpm --eval "%configure" | sh
>
> on Ubuntu and the output seemed reasonable. I simply didn't have the time
> to look into it at the time so I just symlinked around the problem.
>
> There is probably a 'deb' way to get those default configure options, but
> I'd
> have to spend some time looking into it.
>
> //Rob
>
_______________________________________________
fcoe-devel mailing list
[email protected]
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel

Reply via email to