aMule Forum
English => aMule Help => Topic started by: Crakem on March 12, 2008, 01:52:48 AM
-
I got aMule-debug-CVS-*.rpm when compiling amuled (build rpm on madriva) with --disable-debug in configure, please could somebody say me what is that (unwanted) rpm? If I install it I got amuled with debug on? If I installed that rpm and later I want to uninstall it (aMule-debug-CVS-*.rpm) I got another time aMuled without debug?
Thanks all!
NOTE: If debug-CVS is a pluggable rpm for enable debug as people want, it's fun! (I never got that package in old 2006 CVS)
-
Sure I got too aMule-CVS-*.rpm but I dont know why I got two rpms:
aMule-CVS-*.rpm
aMule-CVS-debug-*.rpm <------ ???
with rpmbuild from mandriva
I using aMule.spec like this:
%define cvsdate 20080220
%define optflags %{nil}
Summary: aMule - another eMule p2p client
Name: aMule
Version: CVS
Release: %{cvsdate}
License: GPL
Group: Applications/Internet
Packager: The aMule Team (http://forum.amule.org/)
Vendor: The aMule Project
URL: http://www.amule.org/
Source: %{name}-%{version}-%{release}.tar.bz2
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
%description
aMule is a peer to peer file sharing client, based on the well known eMule.
Starting with 2.0.0 aMule works on Linux, Mac, *BSD and Windows, which makes it
the first multi-platform edonkey network client.
%pre
echo "****************************************************************************"
echo "Warning: This is a cvs release!"
echo "This release is made for testing purpose and it may cause several problems,"
echo "burn your house, kill your dog, etc, but it *should* be safe to use anyway."
echo "If you would like to test some of the great new features go on and install."
echo "Otherwise you may press ctrl-c within the next 10 seconds to abort the"
echo "installation."
echo -n "Waiting for user... "
for i in $(seq 10 -1 1); do
echo -n "$i, "
sleep 1
done
echo " 0, ok, here we go then... Muhahaha :), installing."
%prep
%setup -q -n amule-cvs
%build
%configure \
--enable-optimize \
--disable-debug \
--disable-monolithic \
--enable-amule-daemon \
--enable-amulecmd \
--enable-webserver \
--disable-ccache \
--enable-nls \
--with-toolkit=base \
--with-language=es
%{__make} %{?_smp_mflags}
%install
[ ! "$RPM_BUILD_ROOT" = "/" ] && %{__rm} -rf "$RPM_BUILD_ROOT"
make DESTDIR=$RPM_BUILD_ROOT install
%find_lang amule
%clean
[ ! "$RPM_BUILD_ROOT" = "/" ] && %{__rm} -rf "$RPM_BUILD_ROOT"
%files -f amule.lang
%defattr(-,root,root,-)
%{_bindir}/amuled
%{_bindir}/autostart-xas
%{_bindir}/ed2k
%{_bindir}/amulecmd
%{_bindir}/amuleweb
%{_libdir}/xchat/plugins/xas.pl
%{_mandir}/man1/*
%{_mandir}/*/man1/*
%docdir %{_datadir}/doc/%{name}-%{version}
%{_datadir}/doc/*
%{_datadir}/amule
%changelog
* Sun Dec 25 2005 Gerd78 <aMule forum>
- Really disable optimizations by defining optflags to nil.
-
I see nothing wrong about the spec. How do you start the build process?
-
I see nothing wrong about the spec. How do you start the build process?
rpmbuild -bb SPECS/aMule-CVS-20080220.specand I got:
ls -hal
170K 2008-02-20 18:38 aMule-debug-CVS-20080220.i586.rpm
2,1M 2008-02-20 18:38 aMule-CVS-20080220.i586.rpmI tested aMule-CVS-20080218 and it got too debug package ???
Thanks very much for (all) your replies wuischke
-
Mh...what files are inside the debug package? It's very small, there's for sure no debug enabled binary.
-
Mh...what files are inside the debug package? It's very small, there's for sure no debug enabled binary.
In debug file under dir: /usr/lib/debug/usr/bin/
-rwxr-xr-x 1 enrique enrique 47K 2008-03-28 16:04 amulecmd.debug
406K 2008-03-28 16:04 amuled.debug
108K 2008-03-28 16:04 amuleweb.debug
14K 2008-03-28 16:04 ed2k.debug
::)
-
Curiouser and curiouser...
Could you do a file /usr/lib/debug/usr/bin/ed2k.debug?
-
Curiouser and curiouser...
Could you do a file /usr/lib/debug/usr/bin/ed2k.debug?
Sure my friend!
amulecmd.debug: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
amuled.debug: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
amuleweb.debug: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
ed2k.debug: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
-
OK, now I'm puzzled. I'm on 64bit, but my amuleweb binary is 736kb and amule (not the daemon) is 6.6MB, both not stripped. Ah, screw it. Just run them in gdb and see if they are the real deal. ;)
-
Just ignore the -debug package.
If you're curious what this is: At the end of the build process, the binaries are stripped. The stripped binaries are placed to /usr/bin, and a separate -debug package with unstripped versions is created. The unstripped binaries are placed to /usr/lib/debug/usr/bin. If you install the -debug package and run amuled with gdb, it will use the unstripped ones.
If you don't know what the difference between a stripped and an unstripped binary is, just ignore it.
-
Thanks all for information. I didn't understand what kind of package I'll produce and I warned myself from installing ::)