Hi all,

I was looking at building the samples directory but encountered ad error during 
the configure.
Before attempting to build within the samples directory, the OpenSAF code 
itself was built using configure and make.
I take it, the samples don't get built by default?

The suggestion is to adjust the PKG_CONFIG_PATH variable. Ok, so what should it 
be set to?


# ./configure
...
checking for SAF_AIS_AMF... no
configure: error: Package requirements (opensaf-amf) were not met:

No package 'opensaf-amf' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
...


Here's the full output:

[root@build-1 ~]# pwd
/root/osaf-build/opensaf-5.19.10/samples
[root@build-1 ~]# ls
aclocal.m4      bootstrap.sh  config.h.in  configure.ac  edsv     install-sh    
   Makefile.in  README
amf             ChangeLog     config.log   COPYING.LIB   glsv     m4            
   missing      smfsv
AUTHORS         compile       config.sub   cpsv          immsv    Makefile.am   
   mqsv         THANKS
autom4te.cache  config.guess  configure    depcomp       INSTALL  
Makefile.common  NEWS
[root@build-1 ~]#
[root@build-1 ~]# ./bootstrap.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
autoreconf: Leaving directory `.'
[root@build-1 ~]#
[root@build-1 ~]# ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for memset... yes
checking for strerror... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for pid_t... yes
checking for size_t... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for SAF_AIS_AMF... no
configure: error: Package requirements (opensaf-amf) were not met:

No package 'opensaf-amf' 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 SAF_AIS_AMF_CFLAGS
and SAF_AIS_AMF_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
[root@build-1 ~]#


Regards,
David

Notice: This e-mail together with any attachments may contain information of 
Ribbon Communications Inc. and its Affiliates that is confidential and/or 
proprietary for the sole use of the intended recipient. Any review, disclosure, 
reliance or distribution by others or forwarding without express permission is 
strictly prohibited. If you are not the intended recipient, please notify the 
sender immediately and then delete all copies, including any attachments.
_______________________________________________
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Reply via email to