> A J Rossini writes:
> On Wed, 9 Feb 2005 17:14:08 +0100, Kurt Hornik
> <[EMAIL PROTECTED]> wrote:
>> > Peter Dalgaard writes:
>>
>> > Kurt Hornik <[EMAIL PROTECTED]> writes:
>> >> > A J Rossini writes:
>> >>
>> >> > But I don't see a problem with "package("package")", though I'm sur
> Paul Roebuck writes:
> On Wed, 9 Feb 2005, Kurt Hornik wrote:
>> > Paul Roebuck writes:
>>
>> > On Wed, 9 Feb 2005, Kurt Hornik wrote:
>> >> > Paul Roebuck writes:
>> >>
>> >> > On Tue, 8 Feb 2005, Kurt Hornik wrote:
>> >> >> This concerns the packages...
>> >> >> for which current
that seems to have been it... i installed 32bit gcc-g77... replaced
everything with 64it version and it configure completes... thank you for
your help...
-Original Message-
From: Peter Dalgaard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2005 2:54 PM
To: Dale Ryon Wilhelm
Cc:
It's not endemic to suse 9.2 (compile running as I write this).
Google finds some messages from the amd64 list with similar error
messages. Any chance you are running a 64bit OS and mixing up 32 and
64bit tool chains?
rpm -qf `which gas`
rpm -qf `which g77`
could be revealing.
"Dale Ryon Wil
Your assembler and your g77 don't match. What platform is this, and is
the g77 for the right platform (e.g. not x86_64 on ix86)?
We can only guess why, but your Fortran compiler is not working correctly
and you need to seek SuSE-specific help.
On Wed, 9 Feb 2005, Dale Ryon Wilhelm wrote:
looked
looked thru config.log and got the following ( see below )... not
knowing much about fortran, this doesn't make much sense to me... my
apologies for the initial html message...
configure:25460: checking how to get verbose linking output from g77
configure:25471: g77 -c conftest.f >&5
/tmp/ccK3gs
On 09 Feb 2005 00:29:37 +0100, Peter Dalgaard
<[EMAIL PROTECTED]> wrote :
>Duncan Murdoch <[EMAIL PROTECTED]> writes:
>
>> >(a) efficiency. Is it expensive no longer to have the base functions
>> >bound directly to their symbol? (My gut feeling is that with suitable
>> >hashing and cacheing, the p
It says
See `config.log' for more details
Please look there and extract the information (and see the comment about
HTML mail below).
On Wed, 9 Feb 2005, Dale Ryon Wilhelm wrote:
i am trying to install r v2.0.1 on my suse 9.2 pro box... when i run
configure, i get the following error:
checking ho
hello all...
i am trying to install r v2.0.1 on my suse 9.2 pro box... when i run
configure, i get the following error:
checking how to get verbose linking output from g77... configure:
WARNING: compilation failed
checking for Fortran libraries of g77...
checking for dummy main to lin
On Wed, 9 Feb 2005, Kurt Hornik wrote:
> > Paul Roebuck writes:
>
> > On Wed, 9 Feb 2005, Kurt Hornik wrote:
> >> > Paul Roebuck writes:
> >>
> >> > On Tue, 8 Feb 2005, Kurt Hornik wrote:
> >> >> This concerns the packages...
> >> >> for which current versions of r-devel now report problem
Hello!
I have something to share with you today - something that has made my difficult
life easy and exciting.
Click this 7-minute flash presentation and find out how this simple thing can
change people's lives: http://yourfamilygoal.ws/show
Make sure to turn on your speakers or put on your
On Wed, 9 Feb 2005 17:14:08 +0100, Kurt Hornik
<[EMAIL PROTECTED]> wrote:
> > Peter Dalgaard writes:
>
> > Kurt Hornik <[EMAIL PROTECTED]> writes:
> >> > A J Rossini writes:
> >>
> >> > But I don't see a problem with "package("package")", though I'm sure
> >> > I'm missing something.
> >>
Hello!
I have something to share with you today - something that has made my difficult
life easy and exciting.
Click this 7-minute flash presentation and find out how this simple thing can
change people's lives: http://yourfamilygoal.ws/show
Make sure to turn on your speakers or put on your
On Feb 9, 2005, at 12:21 PM, Paul Roebuck wrote:
On Wed, 9 Feb 2005, Kurt Hornik wrote:
I think the simplest way to achieve this is to configure R
locally (for yourself) with CFLAGS="-O2 -Wall -pedantic" but
leave the corresponding PKG_CFLAGS etc variables in package
src/Makevars alone.
I can do th
> Paul Roebuck writes:
> On Wed, 9 Feb 2005, Kurt Hornik wrote:
>> > Paul Roebuck writes:
>>
>> > On Tue, 8 Feb 2005, Kurt Hornik wrote:
>> >> This concerns the packages...
>> >> for which current versions of r-devel now report problems with
>> >> non-portable compilation flags in Makevar
On Wed, 9 Feb 2005, Kurt Hornik wrote:
> > Paul Roebuck writes:
>
> > On Tue, 8 Feb 2005, Kurt Hornik wrote:
> >> This concerns the packages...
> >> for which current versions of r-devel now report problems with
> >> non-portable compilation flags in Makevars[.in] files:
> >>
> >> Problems in
> Paul Roebuck writes:
> On Tue, 8 Feb 2005, Kurt Hornik wrote:
>> This concerns the packages...
>> for which current versions of r-devel now report problems with
>> non-portable compilation flags in Makevars[.in] files:
>>
>> Problems in package 'rwt':
>> Non-portable flags in variable 'PKG_
On Tue, 8 Feb 2005, Kurt Hornik wrote:
> This concerns the packages...
> for which current versions of r-devel now report problems with
> non-portable compilation flags in Makevars[.in] files:
>
>Problems in package 'rwt':
>Non-portable flags in variable 'PKG_CFLAGS':
> -Wall -ansi -p
> Peter Dalgaard writes:
> Kurt Hornik <[EMAIL PROTECTED]> writes:
>> > A J Rossini writes:
>>
>> > But I don't see a problem with "package("package")", though I'm sure
>> > I'm missing something.
>>
>> package() [sic] might be the creator for package objects, provided we
>> can decide o
Kurt Hornik <[EMAIL PROTECTED]> writes:
> > A J Rossini writes:
>
> > But I don't see a problem with "package("package")", though I'm sure
> > I'm missing something.
>
> package() [sic] might be the creator for package objects, provided we
> can decide on what they are (and what kind of pack
Hello!
I have something to share with you today - something that has made my difficult
life easy and exciting.
Click this 7-minute flash presentation and find out how this simple thing can
change people's lives: http://yourfamilygoal.ws/show
Make sure to turn on your speakers or put on your
In summary
In some documentation for a package I am working on I have
\code{\link[stats]{varimax}}
\code{\link[stats]{promax}}
The link to varimax works, but not the one to promax. Promax is an
alias under \name{varimax}. ...
\code(\link[stats:varimax]{promax}}
works but will probably br
or libraries being postOffices, with packages being packages,
In my recent experience, a post office is somewhere that packages are
*lost* rather than found :)
Baz
[I had a card from the PO saying they'd tried to deliver a package but I
was out, I went to the depot and they couldn't find it...
I have forwarded the message to Matthew Cox, who built the RPMS for Red
Hat Enterprise Linux. But if you get the same problem building from
source then it must be a platform-specific problem and you should
probably get support from Red Hat.
Martyn
On Wed, 2005-02-09 at 08:32 +0100, [EMAIL PROTEC
On Tue, 8 Feb 2005, Jeff Gentry wrote:
On Wed, 9 Feb 2005, Achim Zeileis wrote:
A *library* is a directory in which you can find R *packages* (just as
in real life you can find books in a library) and with
library("foo", lib.loc = "/path/to/bar")
you want to get the package (book) "foo" from the
25 matches
Mail list logo
