Hi there, <swear> Has anybody noticed that Majordomo was written by a bunch of brain-dead morons? When anybody mentioned the word "unstable" in a mail it gets sorted out and ends up as a Majordomo error because they match against the regular expression "/\buns\w*b/i" which is obviously meant for "unsubscribe" but matches other stuff, too. I have deleted the most idiotic patterns from the check and hope it works better now, but if anybody has a good alternative for Majordomo I would like to hear about it. Sorry for being inpolite but it just overcomes you when you have a look at those scripts. It is unbelievable! </swear> Now to Julian's question: I hope to package and upload it today or tomorrow. Some people are also eager for Cint and I have sorted out most problems with Masaharu now which so far prevented a reasonable packaging. I don't know yet how that is going to work out, though. As for the library versioning, no that is ok. The numbers attached to the filenames are a priori unrelated to the library version number. If you find this irritating, please have a look at the info page provided by libtool. Sorry, I do not know why you get "checking for CLN - version >= 1.1.0... no". I have just installed cln_1.1.0-2_i386.deb and cln-dev_1.1.0-2_i386.deb and run configure and it works fine. Could you please investigate by having a look at config.log and find out why the test program "failed to compile or link"? (By manually creating that test program and try to get it running.) Regards -richy. PS: I assume that you are running i386 since the build daemon usually takes some days or weeks? -- Richard Kreckel <Richard.Kreckel@Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/> ---------- Forwarded message ---------- Date: Mon, 19 Mar 2001 12:43:58 +0100 From: owner-ginac-devel@thep.physik.uni-mainz.de To: ginac-devel-approval@thep.physik.uni-mainz.de Subject: BOUNCE ginac-devel@ThEP.Physik.Uni-Mainz.DE: Admin request of type /\buns\w*b/i at line 2 Admin request of type /\buns\w*b/i at line 6
From kreckel@thep.physik.uni-mainz.de Mon Mar 19 12:43:56 2001 Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by zino.physik.uni-mainz.de (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA22673 for <ginac-devel@zino.physik.uni-mainz.de>; Mon, 19 Mar 2001 12:43:56 +0100 Received: from antoinette.snu.ac.kr (mail@antoinette.snu.ac.kr [147.46.115.122]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f2JBhpV08288 for <ginac-devel@zino.physik.uni-mainz.de>; Mon, 19 Mar 2001 12:43:52 +0100 (MET) Received: from stoev by antoinette.snu.ac.kr with local (Exim 3.22 #1 (Debian)) id 14ey4Z-00084x-00 for <ginac-devel@zino.physik.uni-mainz.de>; Mon, 19 Mar 2001 20:43:39 +0900 Date: Mon, 19 Mar 2001 20:43:33 +0900 From: Julian Stoev <stoev@users.sourceforge.net> To: ginac-devel@thep.physik.uni-mainz.de Subject: Re: CLN 1.1 Message-ID: <20010319204333.A18940@antoinette.snu.ac.kr> References: <Pine.LNX.4.10.10103191123400.16602-100000@galileo.fis.unipr.it> <Pine.LNX.4.21.0103191146350.26620-100000@higgs.physik.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <Pine.LNX.4.21.0103191146350.26620-100000@higgs.physik.uni-mainz.de>; from kreckel@zino.physik.uni-mainz.de on Mon, Mar 19, 2001 at 12:02:04PM +0100 Sender: Julian Stoev <stoev@antoinette.snu.ac.kr>
Is there a hope for ginac Debian unstable packages appearing somewhere on the ftp? And BTW, I don't know why, but the names of the cln libs in Debian unstable are: -rw-r--r-- 1 root root 3098108 Mar 16 04:44 libcln.a -rw-r--r-- 1 root root 636 Mar 16 04:44 libcln.la lrwxrwxrwx 1 root root 15 Mar 19 20:24 libcln.so -> libcln.so.1.0.0 lrwxrwxrwx 1 root root 15 Mar 19 20:24 libcln.so.1 -> libcln.so.1.0.0 -rw-r--r-- 1 root root 940300 Mar 16 04:44 libcln.so.1.0.0 Shouldn't these be 1.1.0 libraries? when I start the configure of ginac, I get checking for CLN - version >= 1.1.0... no *** Could not run CLN test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means CLN was incorrectly installed *** or that you have moved CLN since it was installed. In the latter case, you *** may want to edit the cln-config script: /usr/bin/cln-config. I am with Debian unstable updated daily. On Mon, Mar 19, 2001 at 12:02:04PM +0100, Richard B. Kreckel wrote: |Bingo! We keep seeing a lot of those problems. Please upgrade your |compiler to GCC 2.95.2 or GCC 2.95.3. If your are running RedHat, please |see <http://www.ginac.de/lists/ginac-devel/msg00083.html>.
On Mon, 19 Mar 2001, Richard B. Kreckel wrote:
<swear> Has anybody noticed that Majordomo was written by a bunch of brain-dead morons? When anybody mentioned the word "unstable" in a mail it gets sorted out and ends up as a Majordomo error because they match against the regular expression "/\buns\w*b/i" which is obviously meant for "unsubscribe" but matches other stuff, too. I have deleted the most idiotic patterns from the check and hope it works better now, but if anybody has a good alternative for Majordomo I would like to hear about it. Sorry for being inpolite but it just overcomes you when you have a look at those scripts. It is unbelievable! </swear>
Try Mailman for a good alternative, http://www.list.org/ Pearu
On Mon, Mar 19, 2001 at 01:21:23PM +0100, Richard B. Kreckel wrote: |As for the library versioning, no that is ok. The numbers attached to the |filenames are a priori unrelated to the library version number. If you |find this irritating, please have a look at the info page provided by |libtool. OK. Thanks. |Sorry, I do not know why you get "checking for CLN - version >= |1.1.0... no". I have just installed cln_1.1.0-2_i386.deb and |cln-dev_1.1.0-2_i386.deb and run configure and it works fine. Could you |please investigate by having a look at config.log and find out why the |test program "failed to compile or link"? (By manually creating that |test program and try to get it running.) I've just rebuild the Debian package from source. To do this I had to install libgmp3-dev. After the rebuild and the install it works fine. Probably there is some obscure dependence on libgmp3-dev in cln-dev, when it was compiled with gmp installed. Probably you have to change your deb depends for cln-dev somehow to include the libgmp3-dev. --JS
Hi Julian, On Tue, 20 Mar 2001, Julian Stoev wrote:
I've just rebuild the Debian package from source. To do this I had to install libgmp3-dev. After the rebuild and the install it works fine. Probably there is some obscure dependence on libgmp3-dev in cln-dev, when it was compiled with gmp installed. Probably you have to change your deb depends for cln-dev somehow to include the libgmp3-dev.
Not really. CLN links against libgmp3. But the headers are not needed any more for running the library, even not for linking against libcln. (We have rejected a dozen or so patches that "fixed" CLN for use with gmp3 for exactly this reason: we don't want to rely on the gmp header filese being there. All we need to know is sizeof(mp_limb_t), then we can map this to our data structures.) So, we have the following dependencies: cln depends on libgmp3 (but not libgmp3-dev) cln-dev depends on cln and thus on libgmp3 the whole package build-depends on libgmp3-dev Probably something got screwed elsewhere. I will build the cln package again, this time not here but on one of the Debian project machines. Please holler if cln-1.1.0_3 reintroduces the problem on your machine! Regards -richy. PS: Hubert, we could need a machine running woody. Can I just use higgs? -- Richard Kreckel <Richard.Kreckel@Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/>
participants (3)
-
Julian Stoev
-
Pearu Peterson
-
Richard B. Kreckel