Keeping track of changes
Locked
 
|
Hi all,
mostly as an aid to Nando (which before a release goes through the ChangeLog, poor soul, and writes a list of the changes since the previous release) I've added a file called Changes.txt to the root QuantLib folder. After committing a change, you're invited to append to such file a short description of your contribution. Thanks, Luigi |
|
|
I spoke too soon. I just looked back at the console history and the
original time QuantLib and the test-suite compiled it was with -O2. When gcc crashed with QuantLib-python it was compiling with -O3. I'm re-compiling QuantLib now with -O1 (hopefully I won't have to go all the way to -O0). Mark. On Jun 15, 2004, at 10:37 AM, Luigi Ballabio wrote: > > Hi all, > mostly as an aid to Nando (which before a release goes through the > ChangeLog, poor soul, and writes a list of the changes since the > previous release) I've added a file called Changes.txt to the root > QuantLib folder. After committing a change, you're invited to append > to such file a short description of your contribution. > > Thanks, > Luigi > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code > NWMGYKND > _______________________________________________ > Quantlib-dev mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
|
Sorry, replied to wrong message.
On Jun 15, 2004, at 10:32 PM, Mark Treiber wrote: > I spoke too soon. I just looked back at the console history and the > original time QuantLib and the test-suite compiled it was with -O2. > When gcc crashed with QuantLib-python it was compiling with -O3. I'm > re-compiling QuantLib now with -O1 (hopefully I won't have to go all > the way to -O0). > > Mark. > > On Jun 15, 2004, at 10:37 AM, Luigi Ballabio wrote: > >> >> Hi all, >> mostly as an aid to Nando (which before a release goes through the >> ChangeLog, poor soul, and writes a list of the changes since the >> previous release) I've added a file called Changes.txt to the root >> QuantLib folder. After committing a change, you're invited to append >> to such file a short description of your contribution. >> >> Thanks, >> Luigi >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference >> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer >> Conference, June 28 - July 1 at the Moscone Center in San Francisco, >> CA >> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code >> NWMGYKND >> _______________________________________________ >> Quantlib-dev mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/quantlib-dev >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code > NWMGYKND > _______________________________________________ > Quantlib-dev mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
|
In reply to this post by mrtreibe
On 2004.06.16 04:32, Mark Treiber wrote:
> I spoke too soon. I just looked back at the console history and the > original time QuantLib and the test-suite compiled it was with -O2. > When gcc crashed with QuantLib-python it was compiling with -O3. I'm > re-compiling QuantLib now with -O1 (hopefully I won't have to go all > the way to -O0). Mark, you might want to go all the way up to gcc 3.3.4 instead. I just recompiled the sources with -O3, and I didn't get the error. Later, Luigi |
|
|
Unfortunately I'm limited to the gcc versions that apple releases (since they
are modified) and the latest is an Apple modified version of gcc 3.3-prerelease. Until apple updates their gcc (which may happen this summer with 10.4 coming out) I found that compiling and the test-suite for QuantLib have no problems with -O1 and that compiling and the test-suite for QuantLib-Python have no problems with -O2. Mark. Quoting Luigi Ballabio <[hidden email]>: > you might want to go all the way up to gcc 3.3.4 instead. > I just recompiled the sources with -O3, and I didn't get the error. ---------------------------------------- This mail sent through www.mywaterloo.ca |
|
|
In reply to this post by Luigi Ballabio-2
On Wed, Jun 16, 2004 at 12:14:02PM +0200, Luigi Ballabio wrote:
> On 2004.06.16 04:32, Mark Treiber wrote: > >I spoke too soon. I just looked back at the console history and the > >original time QuantLib and the test-suite compiled it was with -O2. > >When gcc crashed with QuantLib-python it was compiling with -O3. I'm > >re-compiling QuantLib now with -O1 (hopefully I won't have to go all > >the way to -O0). > > Mark, > you might want to go all the way up to gcc 3.3.4 instead. > I just recompiled the sources with -O3, and I didn't get the error. Seconded, for what it's worth. It builds fine here on i386 with the default -02, once I figured out which of the Debian boost development packages I needed (libboost-dev, libboost-regex-dev, libboost-test-dev). I now have to fix something in the package structure that seems to stem from the split of the main libraries. So on track, but a little late... Dirk, who is busy with Quantian -- FEATURE: VW Beetle license plate in California |
|
|
On Wed, Jun 16, 2004 at 07:49:51AM -0500, Dirk Eddelbuettel wrote:
> On Wed, Jun 16, 2004 at 12:14:02PM +0200, Luigi Ballabio wrote: > > On 2004.06.16 04:32, Mark Treiber wrote: > > >I spoke too soon. I just looked back at the console history and the > > >original time QuantLib and the test-suite compiled it was with -O2. > > >When gcc crashed with QuantLib-python it was compiling with -O3. I'm > > >re-compiling QuantLib now with -O1 (hopefully I won't have to go all > > >the way to -O0). > > > > Mark, > > you might want to go all the way up to gcc 3.3.4 instead. > > I just recompiled the sources with -O3, and I didn't get the error. > > Seconded, for what it's worth. It builds fine here on i386 with the default > -02, once I figured out which of the Debian boost development packages I > needed (libboost-dev, libboost-regex-dev, libboost-test-dev). I now have to > fix something in the package structure that seems to stem from the split of > the main libraries. So on track, but a little late... Something changed in the Makefiles. Up until 0.3.6, I would have edd@basebud:/var/local/cache/pbuilder/result> dpkg -c libquantlib0_0.3.6-1_i386.deb | grep usr/lib drwxr-xr-x root/root 0 2004-04-15 17:44:31 ./usr/lib/ -rw-r--r-- root/root 3660992 2004-04-15 17:44:31 ./usr/lib/libQuantLib.so.0.0.0 lrwxrwxrwx root/root 0 2004-04-15 17:44:23 ./usr/lib/libQuantLib.so.0 -> libQuantLib.so.0.0.0 in the runtime package, and edd@basebud:/var/local/cache/pbuilder/result> dpkg -c libquantlib0-dev_0.3.6-1_i386.deb | grep usr/lib drwxr-xr-x root/root 0 2004-04-15 17:44:33 ./usr/lib/ -rw-r--r-- root/root 15932122 2004-04-15 17:44:33 ./usr/lib/libQuantLib.a lrwxrwxrwx root/root 0 2004-04-15 17:44:29 ./usr/lib/libQuantLib.so -> libQuantLib.so.0.0.0 in the development package. The meta-rules where tagges on that, i.e. /usr/lib/*.so and /usr/lib/*.a get moved into the -dev package. Now I get basebud:/home/quantlib-0.3.6.rc.20040611/debian/libquantlib0-dev/usr/lib# ls -l total 21912 -rwxr-xr-x 1 root root 4742328 Jun 16 12:50 libQuantLib-0.3.7.so -rw-r--r-- 1 root root 17215158 Jun 16 12:50 libQuantLib.a lrwxrwxrwx 1 root root 20 Jun 16 12:50 libQuantLib.so -> libQuantLib-0.3.7.so -rwxr-xr-x 1 root root 177061 Jun 16 12:50 libQuantLibFunctions-0.3.7.so -rw-r--r-- 1 root root 250240 Jun 16 12:50 libQuantLibFunctions.a lrwxrwxrwx 1 root root 29 Jun 16 12:50 libQuantLibFunctions.so -> libQuantLibFunctions-0.3.7.so basebud:/home/quantlib-0.3.6.rc.20040611/debian/libquantlib0-dev/usr/lib# Is that caused by a new libtool version? I guess I am simply behind in terms of what is currently en vogue ... From the looks of it, I need to make sure that the two .so libs (to which ldd on the example binary points) stay in the library package, and I should then be fine. Comments? Dirk -- FEATURE: VW Beetle license plate in California |
|
|
On 2004.06.16 15:00, Dirk Eddelbuettel wrote:
> Something changed in the Makefiles. > > Is that caused by a new libtool version? I guess I am simply behind > in terms of what is currently en vogue ... Old libtool, new flags. It might (emphasis on might) make it feasible to keep different versions installed. > From the looks of it, I need to make sure that the two .so libs (to > which ldd on the example binary points) stay in the library package, > and I should then be fine. Comments? I think so. lib*-0.3.7 should correspond to the old lib*.0.0.0. Later, Luigi P.S. You won't have to depend on boost-regex in the final version (the dependency probably came from a forgotten #include that I just nuked) |
|
|
On Wed, Jun 16, 2004 at 03:32:31PM +0200, Luigi Ballabio wrote:
> On 2004.06.16 15:00, Dirk Eddelbuettel wrote: > >Something changed in the Makefiles. > > > >Is that caused by a new libtool version? I guess I am simply behind > >in terms of what is currently en vogue ... > > Old libtool, new flags. It might (emphasis on might) make it feasible > to keep different versions installed. Right, that's how it looks by encoding the major/minor in the filename. > >From the looks of it, I need to make sure that the two .so libs (to > >which ldd on the example binary points) stay in the library package, > >and I should then be fine. Comments? > > I think so. lib*-0.3.7 should correspond to the old lib*.0.0.0. Yes, I'll try that later then. > > Later, > Luigi > > P.S. You won't have to depend on boost-regex in the final version (the > dependency probably came from a forgotten #include that I just nuked) Ack. I may as well keep it in. Would be nice to have configure checks for the different boost pieces, though. Ciao, Dirk -- FEATURE: VW Beetle license plate in California |
«
Return to quantlib-dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |