tcltk problems

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

tcltk problems

Rolf Turner

It recently came to my attention that my R installation no longer has
tcltk capability.

I can't figure out why or what to do about it.

I built R from source.  I configured using the "--with-tcltk" flag.  The
build and install *seemed* to go OK, but after realising I didn't have
tcltk capability I looked into config.log.

There I found:

> configure:39486: checking for tclConfig.sh
> configure:39519: result: no
> configure:39528: checking for tclConfig.sh in library (sub)directories
> configure:39549: result: no
> configure:39561: checking for tkConfig.sh
> configure:39594: result: no
> configure:39603: checking for tkConfig.sh in library (sub)directories
> configure:39624: result: no
> configure:39721: checking for tcl.h
> conftest.c:249:17: fatal error: tcl.h: No such file or directory
> compilation terminated.

I have tcl and tk (and the -dev versions) installed on my machine, and
they are apparently up-to-date).

Moreover if I do "locate tclConfig.sh" I get:

> /usr/lib/tcl8.6/tclConfig.sh
> /usr/lib/x86_64-linux-gnu/tcl8.6/tclConfig.sh

And likewise "locate tcl.h" produces:

> /usr/include/tcl8.6/tcl.h
> /usr/include/tcl8.6/tcl-private/generic/tcl.h

So why can't "configure" find these files, and how can I tell it where
to find them?

I'm running Ubuntu 16.04 and my last install of R was of version 3.4.2.

My installation procedure always worked in the past ....

Thanks for any tips.

cheers,

Rolf Turner

--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Erin Hodgess-2
When I have compiled from sourced on Ubuntu, I did NOT include the
"with-tcltk" and it worked fine.  Did you try that, please?

Thanks,
Erin


On Fri, Nov 17, 2017 at 6:34 PM, Rolf Turner <[hidden email]>
wrote:

>
> It recently came to my attention that my R installation no longer has
> tcltk capability.
>
> I can't figure out why or what to do about it.
>
> I built R from source.  I configured using the "--with-tcltk" flag.  The
> build and install *seemed* to go OK, but after realising I didn't have
> tcltk capability I looked into config.log.
>
> There I found:
>
> configure:39486: checking for tclConfig.sh
>> configure:39519: result: no
>> configure:39528: checking for tclConfig.sh in library (sub)directories
>> configure:39549: result: no
>> configure:39561: checking for tkConfig.sh
>> configure:39594: result: no
>> configure:39603: checking for tkConfig.sh in library (sub)directories
>> configure:39624: result: no
>> configure:39721: checking for tcl.h
>> conftest.c:249:17: fatal error: tcl.h: No such file or directory
>> compilation terminated.
>>
>
> I have tcl and tk (and the -dev versions) installed on my machine, and
> they are apparently up-to-date).
>
> Moreover if I do "locate tclConfig.sh" I get:
>
> /usr/lib/tcl8.6/tclConfig.sh
>> /usr/lib/x86_64-linux-gnu/tcl8.6/tclConfig.sh
>>
>
> And likewise "locate tcl.h" produces:
>
> /usr/include/tcl8.6/tcl.h
>> /usr/include/tcl8.6/tcl-private/generic/tcl.h
>>
>
> So why can't "configure" find these files, and how can I tell it where to
> find them?
>
> I'm running Ubuntu 16.04 and my last install of R was of version 3.4.2.
>
> My installation procedure always worked in the past ....
>
> Thanks for any tips.
>
> cheers,
>
> Rolf Turner
>
> --
> Technical Editor ANZJS
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posti
> ng-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>



--
Erin Hodgess
Associate Professor
Department of Mathematical and Statistics
University of Houston - Downtown
mailto: [hidden email]

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Rolf Turner
On 18/11/17 17:00, Erin Hodgess wrote:
> When I have compiled from sourced on Ubuntu, I did NOT include the
> "with-tcltk" and it worked fine.  Did you try that, please?

In the past I have configured without using the "--with-tcltk" flag,
and R of course built just fine.  But it *did not* have tcltk
capability.  When I wanted that capability I had to start using the
aforesaid flag.

It makes absolutely no sense that one would get tcltk capability when
configuring without the flag but *not* get it when configuring *with*
the flag.  If that is indeed the case then this definitely constitutes a
bug in the "configure" system.

I cannot believe that it would work to leave out the flag, but I'll try
it just for the sake of "completeness".

cheers,

Rolf

--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Rolf Turner
In reply to this post by Erin Hodgess-2

On 18/11/17 17:00, Erin Hodgess wrote:

> When I have compiled from sourced on Ubuntu, I did NOT include the
> "with-tcltk" and it worked fine.  Did you try that, please?

As I said, this idea makes absolutely no sense, but OK, I tried it.
And of course it didn't work.

Using the newly built R I ran capabilities() and got:

>        jpeg         png        tiff       tcltk         X11        aqua
>        TRUE        TRUE        TRUE       FALSE        TRUE       FALSE
>    http/ftp     sockets      libxml        fifo      cledit       iconv
>        TRUE        TRUE        TRUE        TRUE        TRUE        TRUE
>         NLS     profmem       cairo         ICU long.double     libcurl
>        TRUE       FALSE        TRUE        TRUE        TRUE        TRUE

cheers,

Rolf

--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

plangfelder
In reply to this post by Rolf Turner
Rolf,

looking at the configure script I believe you need to specify

--with-tcl-config=/usr/lib/tcl8.6/tclConfig.sh

and similarly

--with-tk-config=<location of tkConfig.sh>

HTH,

Peter


On Fri, Nov 17, 2017 at 8:43 PM, Rolf Turner <[hidden email]> wrote:

> On 18/11/17 17:00, Erin Hodgess wrote:
>>
>> When I have compiled from sourced on Ubuntu, I did NOT include the
>> "with-tcltk" and it worked fine.  Did you try that, please?
>
>
> In the past I have configured without using the "--with-tcltk" flag,
> and R of course built just fine.  But it *did not* have tcltk capability.
> When I wanted that capability I had to start using the
> aforesaid flag.
>
> It makes absolutely no sense that one would get tcltk capability when
> configuring without the flag but *not* get it when configuring *with* the
> flag.  If that is indeed the case then this definitely constitutes a bug in
> the "configure" system.
>
> I cannot believe that it would work to leave out the flag, but I'll try it
> just for the sake of "completeness".
>
> cheers,
>
> Rolf
>
> --
> Technical Editor ANZJS
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Peter Dalgaard-2
That should probably work, but I wonder whether the root cause might be non-installation of Ubuntu "-devel" (or is it "-dev"?) Tcl and Tk packages. It doesn't look quite right to have to tell R's configure about a path that depends on the current Tcl/Tk version. I would have expected that tclConfig.sh would be found in /usr/lib or /usr/local/lib.

-pd

> On 18 Nov 2017, at 06:18 , Peter Langfelder <[hidden email]> wrote:
>
> Rolf,
>
> looking at the configure script I believe you need to specify
>
> --with-tcl-config=/usr/lib/tcl8.6/tclConfig.sh
>
> and similarly
>
> --with-tk-config=<location of tkConfig.sh>
>
> HTH,
>
> Peter
>
>
> On Fri, Nov 17, 2017 at 8:43 PM, Rolf Turner <[hidden email]> wrote:
>> On 18/11/17 17:00, Erin Hodgess wrote:
>>>
>>> When I have compiled from sourced on Ubuntu, I did NOT include the
>>> "with-tcltk" and it worked fine.  Did you try that, please?
>>
>>
>> In the past I have configured without using the "--with-tcltk" flag,
>> and R of course built just fine.  But it *did not* have tcltk capability.
>> When I wanted that capability I had to start using the
>> aforesaid flag.
>>
>> It makes absolutely no sense that one would get tcltk capability when
>> configuring without the flag but *not* get it when configuring *with* the
>> flag.  If that is indeed the case then this definitely constitutes a bug in
>> the "configure" system.
>>
>> I cannot believe that it would work to leave out the flag, but I'll try it
>> just for the sake of "completeness".
>>
>> cheers,
>>
>> Rolf
>>
>> --
>> Technical Editor ANZJS
>> Department of Statistics
>> University of Auckland
>> Phone: +64-9-373-7599 ext. 88276
>>
>> ______________________________________________
>> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
>> https://stat.ethz.ch/mailman/listinfo/r-help
>> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
>> and provide commented, minimal, self-contained, reproducible code.
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

--
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: [hidden email]  Priv: [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Albrecht Kauffmann-2
In reply to this post by Erin Hodgess-2
Did you istall the tcl- and tk-devel packages?

Best, Albrecht

--
  Albrecht Kauffmann
  [hidden email]

Am Sa, 18. Nov 2017, um 05:00, schrieb Erin Hodgess:

> When I have compiled from sourced on Ubuntu, I did NOT include the
> "with-tcltk" and it worked fine.  Did you try that, please?
>
> Thanks,
> Erin
>
>
> On Fri, Nov 17, 2017 at 6:34 PM, Rolf Turner <[hidden email]>
> wrote:
>
> >
> > It recently came to my attention that my R installation no longer has
> > tcltk capability.
> >
> > I can't figure out why or what to do about it.
> >
> > I built R from source.  I configured using the "--with-tcltk" flag.  The
> > build and install *seemed* to go OK, but after realising I didn't have
> > tcltk capability I looked into config.log.
> >
> > There I found:
> >
> > configure:39486: checking for tclConfig.sh
> >> configure:39519: result: no
> >> configure:39528: checking for tclConfig.sh in library (sub)directories
> >> configure:39549: result: no
> >> configure:39561: checking for tkConfig.sh
> >> configure:39594: result: no
> >> configure:39603: checking for tkConfig.sh in library (sub)directories
> >> configure:39624: result: no
> >> configure:39721: checking for tcl.h
> >> conftest.c:249:17: fatal error: tcl.h: No such file or directory
> >> compilation terminated.
> >>
> >
> > I have tcl and tk (and the -dev versions) installed on my machine, and
> > they are apparently up-to-date).
> >
> > Moreover if I do "locate tclConfig.sh" I get:
> >
> > /usr/lib/tcl8.6/tclConfig.sh
> >> /usr/lib/x86_64-linux-gnu/tcl8.6/tclConfig.sh
> >>
> >
> > And likewise "locate tcl.h" produces:
> >
> > /usr/include/tcl8.6/tcl.h
> >> /usr/include/tcl8.6/tcl-private/generic/tcl.h
> >>
> >
> > So why can't "configure" find these files, and how can I tell it where to
> > find them?
> >
> > I'm running Ubuntu 16.04 and my last install of R was of version 3.4.2.
> >
> > My installation procedure always worked in the past ....
> >
> > Thanks for any tips.
> >
> > cheers,
> >
> > Rolf Turner
> >
> > --
> > Technical Editor ANZJS
> > Department of Statistics
> > University of Auckland
> > Phone: +64-9-373-7599 ext. 88276
> >
> > ______________________________________________
> > [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> > https://stat.ethz.ch/mailman/listinfo/r-help
> > PLEASE do read the posting guide http://www.R-project.org/posti
> > ng-guide.html
> > and provide commented, minimal, self-contained, reproducible code.
> >
>
>
>
> --
> Erin Hodgess
> Associate Professor
> Department of Mathematical and Statistics
> University of Houston - Downtown
> mailto: [hidden email]
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Dirk Eddelbuettel

Rolf,

A few quick points as I just noticed this thread (as I don't regularly dip
into r-help any more):

 1)  You really do not need to builds R locally on Ubuntu. I update the
     Debian package hours after Peter cuts a release. Michael rolls Ubuntu
     releases off these typically the same or next day, which arrive at CRAN
     in less than 72 hours after a release.

     See https://cloud.r-project.org/bin/linux/ubuntu/README.html

     I run these binaries myself on several personal machines and dozens more
     at work.  They. Just. Work.  Why not take advantage of a freebie?

 2)  If you still want to build locally, simply copy what we do. Our sources
     are public.  The debian/control for r-base (for Debian, albeit, don't
     have Michael's here but tcl/tk has not changed in year) has

        Build-Depends: gcc (>= 4:4.1.0), [...], tcl8.6-dev, tk8.6-dev, [...]

     so make sure you install those two package, and the debian/rules does

        ./configure --prefix=/usr \
                    [....]
                    --with-tcltk \
                    [....]

        [...]

        $(MAKE)    [...]

     ie nothing special for configure or make.

     My most recent build then logged

        checking for tclConfig.sh... no
        checking for tclConfig.sh in library (sub)directories... /usr/lib/tcl8.6/tclConfig.sh
        checking for tkConfig.sh... no
        checking for tkConfig.sh in library (sub)directories... /usr/lib/tk8.6/tkConfig.sh
        checking tcl.h usability... yes
        checking tcl.h presence... yes
        checking for tcl.h... yes
        checking tk.h usability... yes
        checking tk.h presence... yes
        checking for tk.h... yes
        checking whether compiling/linking Tcl/Tk code works... yes

     which echos what Peter already said. Its final state report for
     configure was

        R is now configured for x86_64-pc-linux-gnu
       
          Source directory:          .
          Installation directory:    /usr
       
          C compiler:                gcc -std=gnu99  -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
          Fortran 77 compiler:       gfortran  -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong
       
          Default C++ compiler:      g++   -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
          C++98 compiler:            g++ -std=gnu++98 -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
          C++11 compiler:            g++ -std=gnu++11 -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
          C++14 compiler:            g++  -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
          C++17 compiler:            g++ -std=gnu++17 -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
          Fortran 90/95 compiler:    gfortran -g -O2 -fdebug-prefix-map=/build/r-base-3.4.2=. -fstack-protector-strong
          Obj-C compiler:      
       
          Interfaces supported:      X11, tcltk
          External libraries:        readline, BLAS(generic), LAPACK(generic), curl
          Additional capabilities:   PNG, JPEG, TIFF, NLS, cairo, ICU
          Options enabled:           shared R library, R profiling, memory profiling
       
          Capabilities skipped:      
          Options not enabled:       shared BLAS
       
          Recommended packages:      no

     which looks pretty good to me. No capabilities. All batteries
     included. (And rec'd packages is no as we package them individually).

 3)  r-help is the wrong list for these questions. Come to r-sig-debian
     which covers R on .deb based systems.  We don't bite, and it is low volume

Cheers, Dirk

--
http://dirk.eddelbuettel.com | @eddelbuettel | [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: tcltk problems

Rolf Turner
In reply to this post by Albrecht Kauffmann-2

On 19/11/17 05:36, Albrecht Kauffmann wrote:

> Did you istall the tcl- and tk-devel packages?

(a) That should be "dev" not "devel".

(b) The answer to your question is, yes, as I made clear in my original
post.

cheers,

Rolf Turner

--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: tcltk problems

Peter Dalgaard-2
Hum, missed that bit. Looking at the configure script, the only way I can see it failing to look in /usr/lib/tcl8.6 is if ${LIBnn} is not "lib". Any chance it might be set to lib64?

-pd


> On 18 Nov 2017, at 22:32 , Rolf Turner <[hidden email]> wrote:
>
>
> On 19/11/17 05:36, Albrecht Kauffmann wrote:
>
>> Did you istall the tcl- and tk-devel packages?
>
> (a) That should be "dev" not "devel".
>
> (b) The answer to your question is, yes, as I made clear in my original post.
>
> cheers,
>
> Rolf Turner
>
> --
> Technical Editor ANZJS
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

--
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: [hidden email]  Priv: [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Rolf Turner
In reply to this post by plangfelder
On 18/11/17 18:18, Peter Langfelder wrote:

> Rolf,
>
> looking at the configure script I believe you need to specify
>
> --with-tcl-config=/usr/lib/tcl8.6/tclConfig.sh
>
> and similarly
>
> --with-tk-config=<location of tkConfig.sh>
>
> HTH.

Yes it helped.  Thank you. I don't really understand why, but.

I had previously (following an off-list suggestion from Berwin Turlach)
put in symbolic links in /usr/lib:

      tclConfig.sh -> tcl8.6/tclConfig.sh*
and
      tkConfig.sh -> tk8.6/tclConfig.sh

so if the configure was by default looking for these files in /usr/lib
it should have found them.  But it seemed not to.

In respect of Dirk's suggestion that I try using pre-built ubuntu R, I
decided to try that and did

sudo apt update
sudo apt-get install r-base

and that kind of worked --- but naturally it screwed something up.  I
can no longer load a "personal" library of utilities --- when I try this
(either having the load command in my .Rprofile or by invoking
R --vanilla) R crashes and tries to dump core.

Now, after having successfully installed R from source (following Peter
Langfelder's tip) I still cannot load my utilities library.  Something
got changed by the "install r-base" procedure, and there would appear to
be no way of tracking down just what got changed.

It's things like that which make me want to "do it myself" as much as
possible.

W.r.t. Peter Dalgaard's suggestion/question about ${LIBnn}$:  I looked
through R-3.4.2/configure and can see nowhere that LIBnn gets set.
(Lots of references to LIBnn, but nowhere that its value gets set equal
to something.)

BTW I (of course) am using the configure file that comes with R-3.4.2; I
haven't changed anything.  So if anyone looks at the R-3.4.2 configure
file they should see exactly what I see.

Then I scanned through BldDir/config.log and found:

LIBnn='lib64'

(on line 19901 !!!)

So it would appear that Peter D.'s conjecture is correct.

OTOH this is waaayyy after the "checking for tclConfig.sh" business,
which happens at about line 15101 of config.log.  So how does it have an
impact on that?

And how did LIBnn get to be set to 'lib64'?  I certainly didn't do it,
and there's nothing about 'lib64' in the environment variables that I
have set.

I remain mystified.

cheers,

Rolf

P.S.  On a whim, I scanned through config.log some more and found many,
many errors logged and many, many "compilation terminated" notes.  In
particular there seem to be problems with a file "confdef.h", which
repeatedly seems to give rise to "fatal errors".  (Where is confdef.h?
It seems to be nowhere.)

But this was from a "*successful*" configure (using Peter L.'s
suggestion.) So it would appear that these errors were harmless.  Mostly
harmless???

R.

--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Peter Dalgaard-2
This is normal, but you're not reading it right. Typically, a program conftest.c is generated on the fly and contains something like a #include of something you may or may not have. The first part of the program is labeled /* conftest.h */ which indicates that it is taken from that file of standard definitions.

The contents of confdefs.h is actually mostly irrelevant (though I suppose there are cases when it isn't), the interesting bit is usually the line(s) that comes from elsewhere, e.g.

....
| #define HAVE_UNISTD_H 1
| #define HAVE_UTIME_H 1
| #define HAVE_ARPA_INET_H 1
| /* end confdefs.h.  */
| #include <dl.h>
configure:23459: result: no
configure:23459: checking for dl.h
configure:23459: result: no

This whole thint is about whether or not your system contains dl.h. When the compile fails, configure concludes that it doesn't.

You only get to see the programs when they fail, but the same mechanism is behind all the other tests, like

configure:23459: checking langinfo.h presence
configure:23459: gcc -arch x86_64 -E -I/usr/local/include conftest.c
configure:23459: $? = 0
configure:23459: result: yes
configure:23459: checking for langinfo.h
configure:23459: result: yes

In some other cases, there is a rudimentary main() function, usually to check existence of specific library routines, and in a few cases there is a check whether the compiled program  actually runs.


-pd

> On 19 Nov 2017, at 02:02 , Rolf Turner <[hidden email]> wrote:
>
> P.S.  On a whim, I scanned through config.log some more and found many, many errors logged and many, many "compilation terminated" notes.  In particular there seem to be problems with a file "confdef.h", which repeatedly seems to give rise to "fatal errors".  (Where is confdef.h?
> It seems to be nowhere.)

--
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: [hidden email]  Priv: [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Peter Dalgaard-2
In reply to this post by Rolf Turner
Dirk may want to dig in here:

Seems like you have a system with a /usr/lib64 dir for 64 bit libraries, but Tcl files in /usr/lib. If that is not an anomaly, it looks like we have a configure bug (conceiveably, a system might be using /usr/lib for architecture-independent files, and lib64/lib32 for binaries). It doesn't look too hard to modify configure to also check /usr/lib, but we probably shouldn't do it if one user has shot himself in the foot somehow.

-pd

> On 19 Nov 2017, at 02:02 , Rolf Turner <[hidden email]> wrote:
>
> Then I scanned through BldDir/config.log and found:
>
> LIBnn='lib64'
>
> (on line 19901 !!!)
>
> So it would appear that Peter D.'s conjecture is correct.
>
> OTOH this is waaayyy after the "checking for tclConfig.sh" business, which happens at about line 15101 of config.log.  So how does it have an impact on that?
>
> And how did LIBnn get to be set to 'lib64'?  I certainly didn't do it, and there's nothing about 'lib64' in the environment variables that I have set.

--
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: [hidden email]  Priv: [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Dirk Eddelbuettel

On 19 November 2017 at 12:17, peter dalgaard wrote:
| Dirk may want to dig in here:

I respectfully decline.

R builds fine on every Ubuntu system, and always has.  No bug in R, or
Ubuntu, or Debian (which would be cup of tea). There is the distro package
(which may be older if an older distro like 16.04 is used) and there always
is a current package at CRAN based on Michael's build of my packages. Always.

Of course a lot of people also locally build R, or maybe R-devel. There is no
general issue here as best as I can tell.

| [...] if one user has shot himself in the foot somehow.

My brief reading suggests that this is the case.

Nothing good comes off moving files around in /usr as was done.  It creates
local non-standard circumstances. You cannot expect standardized build to
anticipate each and every possible non-standard modification.

This discussion is still on the wrong list too.

Dirk

--
http://dirk.eddelbuettel.com | @eddelbuettel | [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Rolf Turner
On 20/11/17 03:15, Dirk Eddelbuettel wrote:

>
> On 19 November 2017 at 12:17, peter dalgaard wrote:
> | Dirk may want to dig in here:
>
> I respectfully decline.
>
> R builds fine on every Ubuntu system, and always has.  No bug in R, or
> Ubuntu, or Debian (which would be cup of tea). There is the distro package
> (which may be older if an older distro like 16.04 is used) and there always
> is a current package at CRAN based on Michael's build of my packages. Always.
>
> Of course a lot of people also locally build R, or maybe R-devel. There is no
> general issue here as best as I can tell.
>
> | [...] if one user has shot himself in the foot somehow.
>
> My brief reading suggests that this is the case.

Point of order Mr. Chairman.  It is completely unfair to say that I shot
myself in the foot.

I did:

sudo apt-get install tcl
sudo apt-get install tcl8.6.dev

and similarly for tk stuff.

I downloaded the source for R-3.4.2 and ran ../R-3.4.2/configure (from a
"parallel" directory "BldDir".

It stuffed up, apparently being unable to find tclConfig.sh and tkConfig.sh.

*After* the stuff-up I put in symbolic links in /usr/lib to these file
in the subdirectories (in which apt-get install apparently placed them.)
This was done according to a suggestion from Berwin Turlach, who found
that there were similar symbolic links in his file system.  This did not
help however.

Peter Langfelder's suggestion, saying very explicitly what flags I
should provide to "configure" in respect of the *Config.sh files, *DID*
work.

I did *not* move any files around.  I did *not* make any alterations to
the configure script.  I did not modify anything, in a "non-standard"
way --- or even in a standard way!  I just used the software provided,
in the prescribed manner, and it did not work.

> Nothing good comes off moving files around in /usr as was done.  It creates
> local non-standard circumstances. You cannot expect standardized build to
> anticipate each and every possible non-standard modification.
>
> This discussion is still on the wrong list too.

Well, OK.  What list *should* it be on?  I was asking for help with an R
problem.  It seems to me that R-help is appropriate.

cheers,

Rolf Turner

--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: tcltk problems

Dirk Eddelbuettel

On 20 November 2017 at 08:38, Rolf Turner wrote:
| Point of order Mr. Chairman.  It is completely unfair to say that I shot
| myself in the foot.

You moved files [or, in this case, created symlinks] below /usr.

Most of us repeatedly said you should not have to.

| Well, OK.  What list *should* it be on?  I was asking for help with an R
| problem.  It seems to me that R-help is appropriate.

r-sig-debian, as my first email here said, and in concordance with all R
mailing list help and information.  

I am removing myself from CCs. The tone of these emails is such that I prefer
to focus on other things. You can do on your systems whatever you want -- but
if it breaks you get to keep the pieces.

Dirk

--
http://dirk.eddelbuettel.com | @eddelbuettel | [hidden email]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: tcltk problems

Berwin A Turlach-3
In reply to this post by Peter Dalgaard-2
G'day Peter,

On Sat, 18 Nov 2017 23:20:25 +0100
peter dalgaard <[hidden email]> wrote:

> Hum, missed that bit. Looking at the configure script, the only way I
> can see it failing to look in /usr/lib/tcl8.6 is if ${LIBnn} is not
> "lib". Any chance it might be set to lib64?

Well, yes, in an earlier e-mail Rolf said:

    Then I scanned through BldDir/config.log and found:
    LIBnn='lib64'
    (on line 19901 !!!)

But that seems to be the output of the configuration as determined
by ./configure.

The question is why ${LIBnn} is set to this value.  If not through some
environment variable or config.site, the only way I can see that the relevant
code snippet[1] (lines 3788-3806 of R 3.4.2's configure, quoted below) sets
${LIBnn} to 'lib64' is if /usr/lib64 exist.

This should not be the case on a 64bit Ubuntu machine.  My machine
has /usr/lib, /usr/lib32 and /usr/libx32.  As far as I know, Ubuntu
(and also Debian? But I have not used Debian for a long time) has always
placed its 64bit libraries into /lib and the 32bit libraries
into e.g. /lib32.  And nowadays, one has also /usr/lib/i386-linux-gnu for
32bit libraries and /usr/lib/x86_64-linux-gnu for 64bit libraries.

As far as I can tell, RedHat used /lib for the 32bit libraries
and /lib64 for the 64bit libraries.  And I believe that most (all?) of
R core that were using linux were using RedHat.  But I could be wrong.
Definitely remember that I always found the multiple-architecture part
in "R Installation and Administration" confusing to read as my linux
system had no /lib64 directories. :)

Finally, if ${LIBnn} is set to 'lib' then the relevant code snippet[2]
(lines 39527-39543 of R 3.4.2's configure, quoted below), would find
tclConfig.sh; regardless on whether it is in /usr/lib
or /usr/lib/tcl8.6.  Of course, if ${LIBnn} is set to 'lib64',
then ./configure will not find tclConfig.sh on an Ubuntu machine.

So Rolf should probably check whether there is a /usr/lib64 directory
on his machine.  If so, why is it there?  Perhaps some other software
installed from source created it? The contents of the directory might give
some clues.  If a /usr/lib64 exist on Rolf's machine, he should probably use
config.site to set ${LIBnn} to 'lib' (line 146 in R 3.4.2's
config.site) so that ./configure can automagically find tclConfig.sh
again......

Cheers,

        Berwin

PS: Who is now wondering whether his 32bit compile of R is actually
using the 64bit version of TCL/TK on his system....  One day I might
find out... :)

[1]
## We need to establish suitable defaults for a 64-bit OS
libnn=lib
case "${host_os}" in
  linux*)
    ## Not all distros use this: some choose to march out of step
    ## Allow for ppc64le (Debian calls ppc64el), powerpc64le ...
    case "${host_cpu}" in
      x86_64|mips64|ppc64*|powerpc64*|sparc64|s390x)
        if test -d /usr/lib64; then
          libnn=lib64
        fi
      ;;
    esac
    ;;
  solaris*)
    ## libnn=lib/sparcv9 ## on 64-bit only, but that's compiler-specific
    ;;
esac
: ${LIBnn=$libnn}

[2]
if test -z "${TCL_CONFIG}"; then
  { $as_echo "$as_me:${as_lineno-$LINENO}: checking for tclConfig.sh in library (sub)directories" >&5
$as_echo_n "checking for tclConfig.sh in library (sub)directories... " >&6; }
if ${r_cv_path_TCL_CONFIG+:} false; then :
  $as_echo_n "(cached) " >&6
else
  for ldir in /usr/local/${LIBnn} /usr/${LIBnn} /${LIBnn} /opt/lib /sw/lib /opt/csw/lib /usr/sfw/lib /opt/freeware/lib; do
  for dir in \
      ${ldir} \
      `ls -d ${ldir}/tcl[8-9].[0-9]* 2>/dev/null | sort -r`; do
    if test -f ${dir}/tclConfig.sh; then
      r_cv_path_TCL_CONFIG="${dir}/tclConfig.sh"
      break 2
    fi
  done
done
fi

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.