As part of my exercise to get Bacula 1.38 running with full GUI toys, I have 
installed SLES 10 on a computer, downloaded and installed the latest MysQL, 
downloaded Bacula 1.38.11 with the bacula-gui-bimagemgr, then downloaded and 
extracted the following:

atk 1.9.1
cairo 1.2.0
glib 2.12.2
gtk+ 2.10.4
jpeg 6b
libpng 1.2.8 (configure version)
pango 1.14.4
pkg-config 0.20
tiff 3.7.4
wxGTK 2.7.0-1
wxWidgets 2.7.0-1

I ran configure for all of the above and make|make install for those to which 
it applies, except for gtk+ and the wx items. My instructions say to do glib, 
gtk+ and wxGTK last, in that order. Also they say to configure gtk with this 
command line argument:

-prefix=/opt/gtk

As you know, configure, make and make install scroll a lot of text through the 
screen. I saw no errors until I tried it with gtk. At the end of make install, 
it informed me:

checking for BASE_DEPENDENCIES... configure: error: Package requirements 
(glib-2.0 >= 2.12.0  atk >= 1.9.0  pango >= 1.12.0  cairo >= 1.2.0) were not 
met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed 
software in a non-standard prefix.
Alternatively you may set the BASE_DEPENDENDENCIES_CFLAGS and 
BASE_DEPENDENCIES_LIBS environment variables to avoid the need to call 
pkg-config. See the pkg-config man page for more details.

I looked at the man page and, while I understood some of what it said, it 
didn't help me solve my problem. So I ran ./configure > [package name].log to 
capture the stdout. I did not then try to capture stderr, and this printed to 
the console:

./configure > cairo.log
cat: /etc/ld.so.conf.d/*.conf: No such file or directory
cat: /etc/ld.so.conf.d/*.conf: No such file or directory
cat: /etc/ld.so.conf.d/*.conf: No such file or directory
configure: WARNING: PDF backend will not be tested since poppler is not 
available
configure: WARNING: SVG backend will not be tested since a librsvg is not 
available

(Obviously, this is for cairo; others had similar errors with respect to "No 
such file . . .")

So I began looking at the config.log files in each of the package directories. 
Most of them had an error of this sort (this one is from pkg-config):

configure: failed program was:
| #ifndef __cplusplus
|    choke me
| #endif
.
.
.
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_ "pkg-config"
| #define VERSION "0.20"
| /* end confdefs.h  */
| #include <ac_nonexistent.h>


Or (This one is from atk):

configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "atk"
| #define PACKAGE_TARNAME "atk"
| #define PACKAGE_VERSION "1.9.1"
| #define PACKAGE_STRING "atk 1.9.1"
| #define PACKAGE_BUGREPORT 
"http://bugzilla.gnome.org/enter_bug.cgi?product=atk";
| #define PACKAGE_ "atk"
| #define VERSION "1.9.1"
| #define GETTEXT_PACKAGE "atk10"
| /* end confdefs.h  */
| #include <ac_nonexistent.h>

So I deleted the package directories and extracted them again so I could run 
configure, make and make install from a clean slate, capturing both sdtout and 
stderr. Here are some examples of stderr output:

glib make:

gconvert.c:91: warning: â€*visibilityâ€* attribute ignored on non-class types
ghash.c: In function â€*IA__g_hash_table_refâ€*:
ghash.c:170: warning: pointer targets in passing argument 1 of 
â€*IA__g_atomic_int_addâ€* differ in signedness

tiff :

dummy.c:9: warning: â€*libport_dummy_functionâ€* defined but not used
tif_dir.c: In function â€*_TIFFVSetFieldâ€*:
.
.
.
ras2tiff.c:101: warning: dereferencing type-punned pointer will break 
strict-aliasing rules

pango install:

libtool: link: warning: 
`/usr/lib/gcc/i586-suse-linux/4.1.0/../../..//libfontconfig.la' seems to be 
moved

The glib, pkg-config and tiff look like file corruption, so I downloaded and 
extracted them again, but got the same results. Are the others telling me that 
they are looking for libraries that are either not installed or that SLES has 
them in unconventional places where the scripts will not find them? If this is 
the case, is there a straightforward change that will let them be found? If 
not, could I expect all these items to install on RH without these errors?

-- 

Tks n rgds,
Richard White CNE6
Network Engineer
Mason County, Washington
360-427-5501
[EMAIL PROTECTED]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to