On Tue, May 20, 2003, Bill Campbell wrote:
> I was building lftp on SuSE 8.2 Linux today, and it was dumping core when
> loading. I made one very minor change in the specfile in hopes that the
> problem lay in library conflicts between the openpkg compiled libraries,
> and system ones, and it seems to have worked.
> [...]
> --- lftp.spec.orig 2003-02-28 10:58:30.000000000 -0800
> +++ lftp.spec 2003-05-20 16:27:36.000000000 -0700
> @@ -33,7 +33,7 @@
> Group: FTP
> License: GPL
> Version: 2.6.5
> -Release: 20030228
> +Release: 20030520
>
> # list of sources
> Source0:
> http://ftp.yars.free.net/pub/software/unix/net/ftp/client/lftp/lftp-%{version}.tar.bz2
> @@ -57,7 +57,7 @@
> CXX="%{l_cxx}" \
> CFLAGS="%{l_cflags -O}" \
> CXXFLAGS="%{l_cxxflags -O}" \
> - ./configure \
> + %{configure} \
> --prefix=%{l_prefix} \
> --sysconfdir=%{l_prefix}/etc/lftp
> %{l_make} %{l_mflags -O}
> [...]
Hmmm... sorry, but %{configure} is a non-OpenPKG RPM macro, so I cannot
just introduce this here. And its definition gives me no clue why this
solves your problem. Can you determine why its definition...
%configure \
CFLAGS="${CFLAGS:-%optflags}" ; export CFLAGS ; \
CXXFLAGS="${CXXFLAGS:-%optflags}" ; export CXXFLAGS ; \
FFLAGS="${FFLAGS:-%optflags}" ; export FFLAGS ; \
%{?__libtoolize:[ -f configure.in ] && %{__libtoolize} --copy --force} ; \
./configure %{_target_platform} \\\
--prefix=%{_prefix} \\\
--exec-prefix=%{_exec_prefix} \\\
--bindir=%{_bindir} \\\
--sbindir=%{_sbindir} \\\
--sysconfdir=%{_sysconfdir} \\\
--datadir=%{_datadir} \\\
--includedir=%{_includedir} \\\
--libdir=%{_libdir} \\\
--libexecdir=%{_libexecdir} \\\
--localstatedir=%{_localstatedir} \\\
--sharedstatedir=%{_sharedstatedir} \\\
--mandir=%{_mandir} \\\
--infodir=%{_infodir}
...makes any difference here? AFAIK only the libtoolize and some
different build flags could make a difference. All the other stuff is
just for paths?
> BTW: The glibc-devel-2.3.2-6 on SuSE 8.1 has a nasty quirk involving
> errno. Instead of being a single external int, it appears they've gone to
> a thread safe implementation which results in undefined references for
> errno unless one includes the <errno.h> header. This breaks quite a few
> builds.
Then we have to fix those vendor sources, of course. Can you give us
details about which packages already fail? We've currently no SuSE box
available, so we cannot check it ourself easily on SuSE. But I guess
RedHat 9 and Debian 3.0 should have similar problems, right?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
