On Thu, Nov 29, 2012 at 6:49 PM, Jakson Alves de Aquino
wrote:
> On Thu, Nov 29, 2012 at 5:55 PM, Simon Urbanek
> wrote:
>> I wrote this post yesterday but for some reason it did not leave the
>> outbox, so apologies to everyone since a mailer glitch apparently
>> failed to prevent the waste of t
On Thu, Nov 29, 2012 at 5:55 PM, Simon Urbanek
wrote:
> I wrote this post yesterday but for some reason it did not leave the
> outbox, so apologies to everyone since a mailer glitch apparently
> failed to prevent the waste of time of quite a few people. To follow
> up on the post - the autoconf ma
I wrote this post yesterday but for some reason it did not leave the outbox, so
apologies to everyone since a mailer glitch apparently failed to prevent the
waste of time of quite a few people. To follow up on the post - the autoconf
macros to look for are AC_PATH_X and AC_PATH_XTRA.
Cheers,
Si
On Nov 28, 2012, at 7:38 PM, Jakson Alves de Aquino wrote:
> Hi,
>
> I submitted a package to CRAN:
> http://cran.r-project.org/web/packages/vimcom/index.html
>
> It builds on Linux without warnings, but there is the following error
> on Mac OS X:
>
>ld: library not found for -lX11
>col
On 29-11-2012, at 18:49, Prof Brian Ripley wrote:
> On 29/11/2012 17:37, Federico Calboli wrote:
>> On 29 Nov 2012, at 17:29, Jochen wrote:
>>
>>> Just a guess, but maybe XCode and its command line tools need to be
>>> installed?
>>
>> I don't know for third parties, but I do have the latest
On 29 Nov 2012, at 17:49, Prof Brian Ripley wrote:
> On 29/11/2012 17:37, Federico Calboli wrote:
>> On 29 Nov 2012, at 17:29, Jochen wrote:
>>
>>> Just a guess, but maybe XCode and its command line tools need to be
>>> installed?
>>
>> I don't know for third parties, but I do have the latest
On 29/11/2012 17:37, Federico Calboli wrote:
On 29 Nov 2012, at 17:29, Jochen wrote:
Just a guess, but maybe XCode and its command line tools need to be installed?
I don't know for third parties, but I do have the latest XCode + command line
tools installed (and I would need them for MacPor
On 29 Nov 2012, at 17:29, Jochen wrote:
> Just a guess, but maybe XCode and its command line tools need to be installed?
I don't know for third parties, but I do have the latest XCode + command line
tools installed (and I would need them for MacPorts in the first place). As by
my previous ema
Just a guess, but maybe XCode and its command line tools need to be installed?
Am 29.11.2012 um 18:09 schrieb Jakson Alves de Aquino :
> On Thu, Nov 29, 2012 at 1:49 PM, Berend Hasselman wrote:
>> On 29-11-2012, at 17:16, Jakson Alves de Aquino wrote:
>>> I adapted the code from cairoDevice pac
On Thu, Nov 29, 2012 at 1:49 PM, Berend Hasselman wrote:
> On 29-11-2012, at 17:16, Jakson Alves de Aquino wrote:
>> I adapted the code from cairoDevice package. It was just a matter
>> of replacing gtk with x11 and I hope that now it will build on any
>> unix that have X installed.
>>
>>https
On 29 Nov 2012, at 16:49, Berend Hasselman wrote:
>
> Contents .../00install.out
>
> * installing *source* package 'vimcom' ...
> checking for pkg-config... no
> ERROR: Cannot find pkg-config.
> ERROR: configuration failed for package 'vimcom'
> * removing
> '/Users/berendhasselman/Documents/P
On 29-11-2012, at 17:16, Jakson Alves de Aquino wrote:
> On Thu, Nov 29, 2012 at 10:26 AM, Prof Brian Ripley
> wrote:
>>> On Thu, Nov 29, 2012 at 10:05 AM, Prof Brian Ripley
>>> wrote:
But those paths should not be used unconditionally (as you have).
They are not right for most
On Thu, Nov 29, 2012 at 10:26 AM, Prof Brian Ripley
wrote:
>> On Thu, Nov 29, 2012 at 10:05 AM, Prof Brian Ripley
>> wrote:
>>>
>>> But those paths should not be used unconditionally (as you have).
>>> They are not right for most x86_64 Linux, Solaris, ... and they
>>> might not even be right on
On 29/11/2012 13:23, Jakson Alves de Aquino wrote:
On Thu, Nov 29, 2012 at 10:05 AM, Prof Brian Ripley
wrote:
But those paths should not be used unconditionally (as you have). They are
not right for most x86_64 Linux, Solaris, ... and they might not even be
right on Mac OS X (depending on the
On Thu, Nov 29, 2012 at 10:05 AM, Prof Brian Ripley
wrote:
> But those paths should not be used unconditionally (as you have). They are
> not right for most x86_64 Linux, Solaris, ... and they might not even be
> right on Mac OS X (depending on the X installation).
Sorry, but I don't known how t
But those paths should not be used unconditionally (as you have). They
are not right for most x86_64 Linux, Solaris, ... and they might not
even be right on Mac OS X (depending on the X installation).
And PKG_CPPFLAGS was correct: that means flags for cpp, the C
pre-processor, not for C++ (wh
On Thu, Nov 29, 2012 at 8:43 AM, jochen laubrock
wrote:
> Works for me after additionally setting PKG_CPPFLAGS to point to the headers
> in Makevars
>
> PKG_LIBS=-L/usr/X11/lib -lX11
> PKG_CPPFLAGS=-I/usr/X11/include
>
>
> On Nov 29, 2012, at 12:18 , Jakson Alves de Aquino wrote:
>
>> On Wed, No
Works for me after additionally setting PKG_CPPFLAGS to point to the headers in
Makevars
PKG_LIBS=-L/usr/X11/lib -lX11
PKG_CPPFLAGS=-I/usr/X11/include
On Nov 29, 2012, at 12:18 , Jakson Alves de Aquino wrote:
> On Wed, Nov 28, 2012 at 9:38 PM, Jakson Alves de Aquino
> wrote:
>> I submitted
On Wed, Nov 28, 2012 at 9:38 PM, Jakson Alves de Aquino
wrote:
> I submitted a package to CRAN:
> http://cran.r-project.org/web/packages/vimcom/index.html
>
> It builds on Linux without warnings, but there is the following error
> on Mac OS X:
>
> ld: library not found for -lX11
> collect2
Hi,
I submitted a package to CRAN:
http://cran.r-project.org/web/packages/vimcom/index.html
It builds on Linux without warnings, but there is the following error
on Mac OS X:
ld: library not found for -lX11
collect2: ld returned 1 exit status
make: *** [vimcom.so] Error 1
ERROR:
20 matches
Mail list logo
