| Summary: | Compile error: multiple definition of `jpeg_suppress_tables' | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Alf Mel <alf> |
| Component: | Portability-Compilation | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.9.5 | |
| Sentry Crash Report: | |||
|
Description
Alf Mel
2007-06-24 03:02:23 UTC
The crucial lines are those just at the first ocurance of the error, ../../digikam/libs/dimg/.libs/libdimg.a(jcapimin.o): In function `jpeg_suppress_tables': jcapimin.c:(.text+0x0): multiple definition of `jpeg_suppress_tables' ../../digikam/libs/jpegutils/.libs/libjpegutils.a(jcapimin.o):jcapimin.c:(.text+0x0): first defined here But I don't understand why ... Maybe you could try with a fresh svn check-out? (http://www.digikam.org/?q=download/svn under "Install digiKam in your Home Directory") Sorry, no real help - good luck, Arnd This is really strange. Here both libs don't contain jcapimin.o You see any output for: ar -t digikam/libs/jpegutils/.libs/libjpegutils.a | grep jcapi ar -t digikam/libs/dimg/.libs/libdimg.a | grep jcapi libjpegutils contains here only two modules: ar -t digikam/libs/jpegutils/.libs/libjpegutils.a jpegutils.o transupp.o Can it be that you try to build a static version of digikam (I never had success building a KDE application static) using ./configure --enable-static ? Alf, We need more informations about how you have compiled and linked digiKam. Please report us these informations, else this story cannot be continued... Gilles Caulier I am building digiKam on a system built from scratch following LFS rules. My configure string is as follows: ./configure --prefix=/opt/kde --disable-debug --disable-dependency-tracking My C(XX)FLAGS were as follows: -Os -march=athlon-xp -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -Wl,-O1,--as-needed All my software has been configured with those flags. I know some packages have troubles with the stack protector and fortify source so I took those off, and simply left -Os -march=athlon-xp -pipe but the same problem occurred. I have not tried the CVS build yet. Hopefully I can try this later today. As per ... comment, I ran the build again, adding --disable-static to make sure static libraries were not built. Configure still gave the same results: checking whether to build static libraries... no Now, correct me if I'm wrong (usually the case), but aren't .la files used for static linking? Why are they being built if static libraries are not being built? I have created a tarball of the source+build directory up until the time it displays the error. The tarball contains two extra files, log-configure and log-make which show the full logs from the configure and make commands. You can download the tarball at: http://slim.mypals.org/slim/digikam-build-error.tar.bz2 Here is a bit more on my environment: umask 022 set +h export _POSIX2_VERSION=199209 export CONFIG_SITE="/var/local/slim/build/digikam/config.site" export LC_ALL=POSIX export LDFLAGS="-s" export CFLAGS="-Os -march=athlon-xp -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -Wl,-O1,--as-needed" export CXXFLAGS="-Os -march=athlon-xp -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -Wl,-O1,--as-needed" export MAKEFLAGS="-j2" export prefix="/opt/kde" My config.site: test $prefix = NONE && prefix=/opt/kde test -z "$CFLAGS" && CFLAGS="-O2 -pipe" test -z "$CXXFLAGS" && CXXFLAGS="-O2 -pipe" My commands after untarring: ./configure --disable-debug --disable-dependency-tracking make -j1 I hope that helps. Is this bugreport still valid? Otherwise we should close it? Not reproductible here with PC It's a specific Macos stuff... So i cannot hack this problem Gilles (In reply to comment #7) > Is this bugreport still valid? Otherwise we should close it? I just built 0.9.4 and the problem did not exist. It has been over a year since this problem was reported and I haven't had it since. It could have been unique to my system. (As a note, this occurred in a Linux system, not on MacOS.) |