You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(13) |
Mar
(1) |
Apr
(17) |
May
(26) |
Jun
(35) |
Jul
(28) |
Aug
(17) |
Sep
(11) |
Oct
(42) |
Nov
(16) |
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(11) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(4) |
Jun
(19) |
Jul
(12) |
Aug
(12) |
Sep
(33) |
Oct
(3) |
Nov
(16) |
Dec
(34) |
| 2005 |
Jan
(59) |
Feb
(25) |
Mar
(9) |
Apr
(11) |
May
(8) |
Jun
(30) |
Jul
(18) |
Aug
(8) |
Sep
(12) |
Oct
(13) |
Nov
(29) |
Dec
(14) |
| 2006 |
Jan
(11) |
Feb
(2) |
Mar
(15) |
Apr
(11) |
May
(23) |
Jun
(14) |
Jul
(4) |
Aug
(19) |
Sep
(3) |
Oct
(34) |
Nov
(7) |
Dec
(7) |
| 2007 |
Jan
(2) |
Feb
(11) |
Mar
(15) |
Apr
|
May
(21) |
Jun
(17) |
Jul
(8) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2008 |
Jan
|
Feb
(9) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(6) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(12) |
| 2010 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
|
7
|
8
|
9
|
10
|
11
(6) |
12
|
13
|
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
|
28
|
29
|
30
|
31
|
|
|
|
|
From: Moriyoshi K. <mo...@sf...> - 2008-12-11 16:53:15
|
Could you send me the config.log in ecell/ directory? You can reach me on #ecell at irc.freenode.net. Thanks. -- moriyoshi On Fri, Dec 12, 2008 at 1:45 AM, Eric Fernandez <efe...@ph...> wrote: > Hi, > > Well, thanks for the tip. Just tried it. > > However, I get the same problem than reported early: > > checking for Boost.Python runtime library avaiability... no > configure: error: could not find Boost.Python library > configure: error: ./configure failed for ecell > error: Bad exit status from > /home/eric/svn/ecell/BUILDROOT/rpm-tmp.hsyK0S (%build) > > Note this is a rpm build, not a direct ./configure && make, but that > should be the same. > Boost Python has been entirely redesigned, could it be the problem ? > > Eric > >> -----Original Message----- >> From: mor...@gm... [mailto:mor...@gm...] On >> Behalf Of Moriyoshi Koizumi >> Sent: 11 December 2008 16:38 >> To: Eric Fernandez >> Cc: ece...@li... >> Subject: Re: [Ecell-devel] Boost Python issue & future of >> e-cell?[Scanned] >> >> Checking out can be done through http as well. >> >> svn checkout >> http://ecell.svn.sourceforge.net/svnroot/ecell/ecell3/branches >> /ecell-3.1 >> ecell-3.1 >> >> You can update to the latest revision by doing svn update in the tree >> (ecell-3.1 for the example above) >> >> Hope this works. >> >> -- moriyoshi >> > |
|
From: Eric F. <efe...@ph...> - 2008-12-11 16:42:49
|
Hi, Well, thanks for the tip. Just tried it. However, I get the same problem than reported early: checking for Boost.Python runtime library avaiability... no configure: error: could not find Boost.Python library configure: error: ./configure failed for ecell error: Bad exit status from /home/eric/svn/ecell/BUILDROOT/rpm-tmp.hsyK0S (%build) Note this is a rpm build, not a direct ./configure && make, but that should be the same. Boost Python has been entirely redesigned, could it be the problem ? Eric > -----Original Message----- > From: mor...@gm... [mailto:mor...@gm...] On > Behalf Of Moriyoshi Koizumi > Sent: 11 December 2008 16:38 > To: Eric Fernandez > Cc: ece...@li... > Subject: Re: [Ecell-devel] Boost Python issue & future of > e-cell?[Scanned] > > Checking out can be done through http as well. > > svn checkout > http://ecell.svn.sourceforge.net/svnroot/ecell/ecell3/branches > /ecell-3.1 > ecell-3.1 > > You can update to the latest revision by doing svn update in the tree > (ecell-3.1 for the example above) > > Hope this works. > > -- moriyoshi > |
|
From: Moriyoshi K. <mo...@sf...> - 2008-12-11 16:38:34
|
Checking out can be done through http as well. svn checkout http://ecell.svn.sourceforge.net/svnroot/ecell/ecell3/branches/ecell-3.1 ecell-3.1 You can update to the latest revision by doing svn update in the tree (ecell-3.1 for the example above) Hope this works. -- moriyoshi On Fri, Dec 12, 2008 at 1:29 AM, Eric Fernandez <efe...@ph...> wrote: > Hi, > > Thanks for your answer. > I am not entriely familiar with svn, especially to checkout a specific > branch. Is it the same syntax than cvs ? > > To be on the safe side, can you confirm this is correct: > svn export > https://svn.sourceforge.net/svnroot/ecell/ecell3/branches/ecell-3.1 > ecell-3.1 > > Kind regards, > Eric > >> -----Original Message----- >> From: mor...@gm... [mailto:mor...@gm...] On >> Behalf Of Moriyoshi Koizumi >> Sent: 11 December 2008 16:00 >> To: Eric Fernandez >> Cc: ece...@li... >> Subject: Re: [Ecell-devel] Boost Python issue & future of >> e-cell?[Scanned] >> >> Hi Eric, >> >> I guess you tried trunk. Unfortunately it's broken at the >> moment, and the working branch is ecell-3.1. >> >> Yes, it's still activlely maintained. (mostly by me) >> >> Regards, >> Moriyoshi >> >> -- moriyoshi > |
|
From: Eric F. <efe...@ph...> - 2008-12-11 16:27:05
|
Hi, Thanks for your answer. I am not entriely familiar with svn, especially to checkout a specific branch. Is it the same syntax than cvs ? To be on the safe side, can you confirm this is correct: svn export https://svn.sourceforge.net/svnroot/ecell/ecell3/branches/ecell-3.1 ecell-3.1 Kind regards, Eric > -----Original Message----- > From: mor...@gm... [mailto:mor...@gm...] On > Behalf Of Moriyoshi Koizumi > Sent: 11 December 2008 16:00 > To: Eric Fernandez > Cc: ece...@li... > Subject: Re: [Ecell-devel] Boost Python issue & future of > e-cell?[Scanned] > > Hi Eric, > > I guess you tried trunk. Unfortunately it's broken at the > moment, and the working branch is ecell-3.1. > > Yes, it's still activlely maintained. (mostly by me) > > Regards, > Moriyoshi > > -- moriyoshi |
|
From: Moriyoshi K. <mo...@sf...> - 2008-12-11 16:04:32
|
Hi Eric, I guess you tried trunk. Unfortunately it's broken at the moment, and the working branch is ecell-3.1. Yes, it's still activlely maintained. (mostly by me) Regards, Moriyoshi -- moriyoshi On Thu, Dec 11, 2008 at 6:22 PM, Eric Fernandez <efe...@ph...> wrote: > Hi, > > I have been maintaining the rpm package for Mandriva Linux for several > years now, and have now been put under pressure to make it work for the > development version (cooker) :) The issues I have are probably valid for > Fedora and other distros. > > I get this building error during the configure: > > checking for Boost.Python runtime library avaiability... no > configure: error: could not find Boost.Python library > configure: error: ./configure failed for ecell > > Allegedly this is because E-cell is not compatible with the new major > version of Boost. Can someone have a look at it? > > At the same time, is e-cell still maintained? What is the current status > ? > > Thanks a lot > Eric > > ------------------------------------------------------------------------------ > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. > The future of the web can't happen without you. Join us at MIX09 to help > pave the way to the Next Web now. Learn more and register at > http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ > _______________________________________________ > Ecell-devel mailing list > Ece...@li... > https://lists.sourceforge.net/lists/listinfo/ecell-devel > |
|
From: Eric F. <efe...@ph...> - 2008-12-11 09:19:44
|
Hi, I have been maintaining the rpm package for Mandriva Linux for several years now, and have now been put under pressure to make it work for the development version (cooker) :) The issues I have are probably valid for Fedora and other distros. I get this building error during the configure: checking for Boost.Python runtime library avaiability... no configure: error: could not find Boost.Python library configure: error: ./configure failed for ecell Allegedly this is because E-cell is not compatible with the new major version of Boost. Can someone have a look at it? At the same time, is e-cell still maintained? What is the current status ? Thanks a lot Eric |