Shibboleth Developers

[Ricardo Dias Marques <>]

Hi Scott,

Today (2009-09-21) Scott Cantor 
<>
 wrote (replying to
Frank Tröger) :

>> BuildRequires:  libapr-util1-devel
> This is already handled by the apache2-devel dependency and is installed in
> the VM for the failed build.
>
>> %build
>> export CPPFLAGS="${CPPFLAGS} -I/usr/include/apr-1"
>
> If that's required, something is broken in the /usr/bin/apr-1-config script.
> I need somebody with SLES 10 who can run the script and see what it's
> reporting.

I have a (VMware Server 1.0.x) Virtual Machine running SLES 10 SP2 (32-bits).

I had installed the "apache2" package but not the "apache2-devel" one,
so I couldn't run the /usr/bin/apr-1-config script to test this.

So, I installed the "apache2-devel" and that installed
"libapr-util1-devel" (libapr-util1-devel-1.2.2-13.2.i586.rpm) and
"libapr1-devel" (libapr1-devel-1.2.2-13.2.i586.rpm).

Now, when I run /usr/bin/apr-1-config I get usage information.

So Scott, in order to help you, I need you to tell me: what "switch"
should I pass to the /usr/bin/apr-1-config script?

Here's the output of /usr/bin/apr-1-config (usage information) in my system:
____________________
 # /usr/bin/apr-1-config
Usage: apr-1-config [OPTION]

Known values for OPTION are:
 --prefix[=DIR]    change prefix to DIR
 --bindir          print location where binaries are installed
 --includedir      print location where headers are installed
 --cc              print C compiler name
 --cpp             print C preprocessor name and any required options
 --cflags          print C compiler flags
 --cppflags        print C preprocessor flags
 --includes        print include information
 --ldflags         print linker flags
 --libs            print additional libraries to link against
 --srcdir          print APR source directory
 --installbuilddir print APR build helper directory
 --link-ld         print link switch(es) for linking to APR
 --link-libtool    print the libtool inputs for linking to APR
 --shlib-path-var  print the name of the shared library path env var
 --apr-la-file     print the path to the .la file, if available
 --apr-so-ext      print the extensions of shared objects on this platform
 --apr-lib-target  print the libtool target information
 --apr-libtool     print the path to APR's libtool
 --version         print the APR's version as a dotted triple
 --help            print this help

When linking with libtool, an application should do something like:
 APR_LIBS="`apr-1-config --link-libtool --libs`"
or when linking directly:
 APR_LIBS="`apr-1-config --link-ld --libs`"

An application should use the results of --cflags, --cppflags, --includes,
and --ldflags in their build process.
____________________


Best wishes,
Ricardo Dias Marques
lists AT ricmarques DOT net