On 19 April 2007 at 20:12, Martin Michlmayr wrote:
| Dirk,
|
| * Dirk Eddelbuettel [EMAIL PROTECTED] [2007-04-19 20:44]:
| No beans. I was just discussing with Kurt Hornik, one of the R Core
| developers, and CRAN maintainers, why building of my RQuantLib /
| r-cran-quantlib takes so long.
Hi Martin,
On 19 April 2007 at 16:51, Martin Michlmayr wrote:
| * Dirk Eddelbuettel [EMAIL PROTECTED] [2006-08-15 17:29]:
| Package: g++-4.1
| Version: 4.1.1-5
|
| I understand that it is fixed in unstable, but as the toolchain is
| frozen (or being frozen) I just want to make sure
Dirk,
* Dirk Eddelbuettel [EMAIL PROTECTED] [2007-04-19 20:44]:
No beans. I was just discussing with Kurt Hornik, one of the R Core
developers, and CRAN maintainers, why building of my RQuantLib /
r-cran-quantlib takes so long. The issue is not solved as far as I can
tell. The linking of
On Saturday 19 August 2006 07:03, Matthias Klose wrote:
Dirk Eddelbuettel writes:
On 18 August 2006 at 00:58, Martin Michlmayr wrote:
| * John Schmidt [EMAIL PROTECTED] [2006-08-17 13:46]:
| Is there a way for me to instrument my code/system, etc to indicate
| where the big time sink
On Tuesday 05 September 2006 11:34, Dirk Eddelbuettel wrote:
On 5 September 2006 at 18:41, Luigi Ballabio wrote:
| On Sep 3, 2006, at 5:57 PM, Dirk Eddelbuettel wrote:
| | s/small/self-contained/ then. Do you have some example where the
| | linking process of some c++ files takes ages,
* Dirk Eddelbuettel [EMAIL PROTECTED] [2006-09-26 13:07]:
Nice work, and I can surely try this. Now, I don't see a recent non-2.17
version of binutils anywhere in .deb form for i386. Before I go off an
rebuild, could you place your version somewhere where I can fetch it from?
On 26 September 2006 at 11:34, John Schmidt wrote:
| To follow-up on my experiences with g++-4.1 code and extremely slow link
| times, I did a chroot and pulled in old versions of g++-4.1 and binutils from
| snapshot.debian.net to build my big c++ application.
|
| Here is a table with the
On 26 September 2006 at 20:10, Martin Michlmayr wrote:
| * Dirk Eddelbuettel [EMAIL PROTECTED] [2006-09-26 13:07]:
| Nice work, and I can surely try this. Now, I don't see a recent non-2.17
| version of binutils anywhere in .deb form for i386. Before I go off an
| rebuild, could you place your
John Schmidt writes:
I then downloaded the gcc-4.1-source and checked if the PR debug/25468 fix
was
included in the source, and it wasn't.
it is. see the upstream changelog in the package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Tuesday 12 September 2006 04:34, Luigi Ballabio wrote:
On Tue, 2006-09-05 at 12:34 -0500, Dirk Eddelbuettel wrote:
Link times. [ The 'link error in Etch' was something we first saw on
hppa, and later noticed as a general problem -- but which is fixed in
recent g++ versions. ]
Are
On Tue, 2006-09-05 at 12:34 -0500, Dirk Eddelbuettel wrote:
Link times. [ The 'link error in Etch' was something we first saw on hppa,
and later noticed as a general problem -- but which is fixed in recent g++
versions. ]
Are you aware of anything we could turn in as a self-contained
On Tuesday 12 September 2006 04:34, Luigi Ballabio wrote:
On Tue, 2006-09-05 at 12:34 -0500, Dirk Eddelbuettel wrote:
Link times. [ The 'link error in Etch' was something we first saw on
hppa, and later noticed as a general problem -- but which is fixed in
recent g++ versions. ]
Are
On Sep 3, 2006, at 5:57 PM, Dirk Eddelbuettel wrote:
| s/small/self-contained/ then. Do you have some example where the
| linking process of some c++ files takes ages, without linking them
| against some external library? That would make things much easier
| imho.
I agree. But as I am unsure
On 5 September 2006 at 18:41, Luigi Ballabio wrote:
|
| On Sep 3, 2006, at 5:57 PM, Dirk Eddelbuettel wrote:
| | s/small/self-contained/ then. Do you have some example where the
| | linking process of some c++ files takes ages, without linking them
| | against some external library? That
On 22 August 2006 at 07:29, Dirk Eddelbuettel wrote:
|
| On 19 August 2006 at 15:03, Matthias Klose wrote:
| | Dirk Eddelbuettel writes:
| |
| | On 18 August 2006 at 00:58, Martin Michlmayr wrote:
| | | * John Schmidt [EMAIL PROTECTED] [2006-08-17 13:46]:
| | | Is there a way for me to
* Dirk Eddelbuettel [EMAIL PROTECTED] [2006-09-03 06:47]:
I never heard any follow-up. Is there any? While it is nice that 4.1.1-11 is
now in testing it is not so nice that 4.1.1-11 exhibits the slow builds John
and I have been experiencing -- on different code bases, no less.
I briefly
* Dirk Eddelbuettel [EMAIL PROTECTED] [2006-09-03 09:16]:
| up with some kind of (small) testcase.
As John and I stated, 'small' is hard to define in the context of large-ish
C++ applications / libraries. The C++ source of RQuantLib are small (around
60kb) and I could probably trim that
On 3 September 2006 at 14:40, Martin Michlmayr wrote:
| * Dirk Eddelbuettel [EMAIL PROTECTED] [2006-09-03 06:47]:
| I never heard any follow-up. Is there any? While it is nice that 4.1.1-11
is
| now in testing it is not so nice that 4.1.1-11 exhibits the slow builds John
| and I have been
On 3 September 2006 at 16:27, Martin Michlmayr wrote:
| * Dirk Eddelbuettel [EMAIL PROTECTED] [2006-09-03 09:16]:
| | up with some kind of (small) testcase.
|
| As John and I stated, 'small' is hard to define in the context of large-ish
| C++ applications / libraries. The C++ source of
One interesting little illustration is provided by the CRAN timing
summaries. The master site of CRAN (the CTAN / CPAN equivalent for R) is
hosted on Debian testing. Compile/build/test times are shown at
http://cran.r-project.org/src/contrib/checkTimings.html
and RQuantLib is the 2nd most
On 19 August 2006 at 15:03, Matthias Klose wrote:
| Dirk Eddelbuettel writes:
|
| On 18 August 2006 at 00:58, Martin Michlmayr wrote:
| | * John Schmidt [EMAIL PROTECTED] [2006-08-17 13:46]:
| | Is there a way for me to instrument my code/system, etc to indicate
| | where the big time
On 18 August 2006 at 00:58, Martin Michlmayr wrote:
| * John Schmidt [EMAIL PROTECTED] [2006-08-17 13:46]:
| Is there a way for me to instrument my code/system, etc to indicate
| where the big time sink is?
|
| I'm not sure but I'll try to investigate.
I didn't make that as clear as I wanted
Dirk Eddelbuettel writes:
On 18 August 2006 at 00:58, Martin Michlmayr wrote:
| * John Schmidt [EMAIL PROTECTED] [2006-08-17 13:46]:
| Is there a way for me to instrument my code/system, etc to indicate
| where the big time sink is?
|
| I'm not sure but I'll try to investigate.
I
* John Schmidt [EMAIL PROTECTED] [2006-08-16 18:32]:
I have a big c++ application that creates quite a few shared libraries and it
takes on the order of 10 minutes for the creation of one of my libraries (not
all of them) with g++-4.1, whereas with g++-4.0, the same library only takes
at
* John Schmidt [EMAIL PROTECTED] [2006-08-17 13:46]:
Is there a way for me to instrument my code/system, etc to indicate
where the big time sink is?
I'm not sure but I'll try to investigate.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Tuesday 15 August 2006 16:29, Dirk Eddelbuettel wrote:
Package: g++-4.1
Version: 4.1.1-5
Severity: important
The g++ version that recently entered testing exhibits the same problem I
had been reported to the hppa maintainers -- and which Randolph report
upstream at
26 matches
Mail list logo
