thr3ads.net - R devel - [Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes) [Dec 2003]

If this information is useful, please help other people find it:
Share via:

Simon Urbanek

2003-Dec-22 19:52 UTC

[Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes)

Some issues with the recent R-devel (rsync today) on Darwin:

1) Recent R-devel is a bit misleading concerning the R-framework  
installation:
A new option --enable-R-framework was introduced, but  
install-Rframework ignores its absence (or --disable-R-framework for  
that matter) and tries to install the framework anyway in / which fails  
just after the R itself was copied into /Versions/.... I know, the user  
is to blame, but still, a simple check and stop (perhaps with a hint to  
use --enable-R-framework) would be nice.

2) Wrong -install_name:
configure.ac@1094:  LIBR_LDFLAGS="-dynamiclib -install_name  
${R_FRAMEWORK_DIR}/R.framework/Versions/${PACKAGE_VERSION}/Resources/ 
bin/libR.dylib -compatibility_version ${PACKAGE_VERSION}   
-current_version ${PACKAGE_VERSION}"

R_FRAMEWORK_DIR specifies the full path including the framework name,  
at least according to the previous definition:

configure.ac@154:
      if test "${want_R_framework}" = yes; then
	R_FRAMEWORK_DIR="/Library/Frameworks/R.framework"
       else
	R_FRAMEWORK_DIR="${want_R_framework}/R.framework"
	want_R_framework=yes
       fi

therefore R.framework should be removed from the path at line 1094

3) Chicken-and-egg problem:
There is a chicken-and-egg  problem if --enable-R-framework is used:
gcc -bundle -flat_namespace -undefined suppress -L/usr/local/lib -o  
R_X11.so  dataentry.lo devX11.lo rotated.lo rbitmap.lo  -lSM -lICE  
-L/usr/X11R6/lib -lX11   -framework R -lz -lreadline -lcc_dynamic  
-lncurses -lm
ld: can't locate framework for: -framework R
make[4]: *** [R_X11.so] Error 1

--enable-framework adds: LIBR="-framework R" [configure.ac@173] which
is then used:
src/modules/X11/Makefile.in@36: R_X11_la_LIBADD = $(ALL_X_LIBS)  
$(BITMAP_LIBS) $(LIBR)

  If you installed R.framework previously, you're fine (well, fine in a  
sense that R is not compiled against its own version of the shared  
library as one would expect, but the currently installed R framework  
instead). If you have a clean system, it won't even build.

It is a touchy subject: during the compilation of R we cannot use the  
framework as-is, since there is none. On the other hand once installed,  
we want all packages to use -framework R.

A partial solution is to "fake" a non-installed framework:

Add following to the Makefile.in conditional for Darwin (probably  
somewhere around src/main/Makefile.in@160):
mkdir $(top_builddir)/bin/R.framework
ln -s ../libR.dylib $(top_builddir)/bin/R.framework/R

and add "-F$(top_builddir)/bin" to the LIBS
The addition of -F.. to LIBS should be temporary during the build of R  
only - I'm not sure if there is such a mechanism in the current R  
building process though ... if there isn't we could just add something  
like $(LIBS_BUILD) or similar to all modules that are built before  
install ...

A side note: unfortunately gcc doesn't honor DYLD_FRAMEWORK_PATH, so we  
cannot use that elegant solution :(

4) warnings - aqua module under construction?
I guess the aqua code is currently under construction, because it's  
probably compiled-in twice (in the libR and in aqua.so):
[...]
ld: warning multiple definitions of symbol _InitAquaIO
aquaconsole.lo definition of _InitAquaIO in section (__TEXT,__text)
/Work/R-builds/osx/r-devel/bin/R.framework/R(aqua.lo) definition of  
_InitAquaIO
[...many warnings of the same kind follow...]

I didn't invesitgate this further - if this is not intentional then I  
could have a look ... I suspect that this has something to do with  
Stefano's attempt to separate Carbon code (aqua+quartz) from the core R  
so it can be used from an external terminal w/o root privileges.

5) --enable vs. --with:
I have a rather general question about configure options: why use the  
name --"with"-aqua but --"enable"-R-framework ? I'm just
curious: after
--with-zlib --with-aqua I somehow expected --with-R-framework, but  
configure neither warns about an unrecognized option, nor does it take  
it as --enable-R-framework. Remember that R.framework isn't just a  
different way to install R/dylib, but in future it will also unlock the  
Obj-C code contained in the R.framework (hopefully) [i.e. to justify  
--with in case it is meant for additional stuff whereas --enable just  
pulls a lever somewhere ...].

Merry Xmas!
Simon

platform powerpc-apple-darwin7.2.0
arch     powerpc
os       darwin7.2.0
system   powerpc, darwin7.2.0
status   Under development (unstable)
major    1
minor    9.0
year     2003
month    12
day      22
language R

---
Simon Urbanek
Department of computer oriented statistics and data analysis
University of Augsburg
Universit?tsstr. 14
86135 Augsburg
Germany

Tel: +49-821-598-2236
Fax: +49-821-598-2200

Simon.Urbanek@Math.Uni-Augsburg.de
http://simon.urbanek.info

stefano iacus

2003-Dec-22 20:48 UTC

head link

[Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes)

On Luned?, dic 22, 2003, at 19:53 Europe/Rome, Simon Urbanek wrote:
> Some issues with the recent R-devel (rsync today) on Darwin:
>
> 1) Recent R-devel is a bit misleading concerning the R-framework  
> installation:
> A new option --enable-R-framework was introduced, but  
> install-Rframework ignores its absence (or --disable-R-framework for  
> that matter) and tries to install the framework anyway in / which  
> fails just after the R itself was copied into /Versions/.... I know,  
> the user is to blame, but still, a simple check and stop (perhaps with  
> a hint to use --enable-R-framework) would be nice.
will do>
> 2) Wrong -install_name:
> configure.ac@1094:  LIBR_LDFLAGS="-dynamiclib -install_name  
> ${R_FRAMEWORK_DIR}/R.framework/Versions/${PACKAGE_VERSION}/Resources/ 
> bin/libR.dylib -compatibility_version ${PACKAGE_VERSION}   
> -current_version ${PACKAGE_VERSION}"
>
> R_FRAMEWORK_DIR specifies the full path including the framework name,  
> at least according to the previous definition:
>
> configure.ac@154:
>      if test "${want_R_framework}" = yes; then
> 	R_FRAMEWORK_DIR="/Library/Frameworks/R.framework"
>       else
> 	R_FRAMEWORK_DIR="${want_R_framework}/R.framework"
> 	want_R_framework=yes
>       fi
>
> therefore R.framework should be removed from the path at line 1094
I've already fixed this>
> 3) Chicken-and-egg problem:
> There is a chicken-and-egg  problem if --enable-R-framework is used:
> gcc -bundle -flat_namespace -undefined suppress -L/usr/local/lib -o  
> R_X11.so  dataentry.lo devX11.lo rotated.lo rbitmap.lo  -lSM -lICE  
> -L/usr/X11R6/lib -lX11   -framework R -lz -lreadline -lcc_dynamic  
> -lncurses -lm
> ld: can't locate framework for: -framework R
> make[4]: *** [R_X11.so] Error 1
>
> --enable-framework adds: LIBR="-framework R" [configure.ac@173]
which
> is then used:
> src/modules/X11/Makefile.in@36: R_X11_la_LIBADD = $(ALL_X_LIBS)  
> $(BITMAP_LIBS) $(LIBR)
>
>  If you installed R.framework previously, you're fine (well, fine in a
> sense that R is not compiled against its own version of the shared  
> library as one would expect, but the currently installed R framework  
> instead). If you have a clean system, it won't even build.I know that, this flag will only be inserted upon installation, I'm  
working on this.

>
> It is a touchy subject: during the compilation of R we cannot use the  
> framework as-is, since there is none. On the other hand once  
> installed, we want all packages to use -framework R.
>
> A partial solution is to "fake" a non-installed framework:
>
> Add following to the Makefile.in conditional for Darwin (probably  
> somewhere around src/main/Makefile.in@160):
> mkdir $(top_builddir)/bin/R.framework
> ln -s ../libR.dylib $(top_builddir)/bin/R.framework/R
>
> and add "-F$(top_builddir)/bin" to the LIBS
> The addition of -F.. to LIBS should be temporary during the build of R  
> only - I'm not sure if there is such a mechanism in the current R  
> building process though ... if there isn't we could just add something
> like $(LIBS_BUILD) or similar to all modules that are built before  
> install ...
>no, I think -framework R is only intended to be present in the R script  
which is installed inside the framework. I.e. only for an installed  
version of R. I don't like this fake solution because R uses  
$(builddir)/bin/R to build packages etc.

Kurt kindly apply these changes for me and I wasn't able to build  
R-devel these days because my machine was down and I needed a urgent  
backup.
> A side note: unfortunately gcc doesn't honor DYLD_FRAMEWORK_PATH, so  
> we cannot use that elegant solution :(
>
> 4) warnings - aqua module under construction?
> I guess the aqua code is currently under construction, because it's  
> probably compiled-in twice (in the libR and in aqua.so):
> [...]
> ld: warning multiple definitions of symbol _InitAquaIO
> aquaconsole.lo definition of _InitAquaIO in section (__TEXT,__text)
> /Work/R-builds/osx/r-devel/bin/R.framework/R(aqua.lo) definition of  
> _InitAquaIO
> [...many warnings of the same kind follow...]
>I don?t have this. I did not apply changes yet.
> I didn't invesitgate this further - if this is not intentional then I  
> could have a look ... I suspect that this has something to do with  
> Stefano's attempt to separate Carbon code (aqua+quartz) from the core  
> R so it can be used from an external terminal w/o root privileges.
>
> 5) --enable vs. --with:
> I have a rather general question about configure options: why use the  
> name --"with"-aqua but --"enable"-R-framework ? I'm
just curious:
> after --with-zlib --with-aqua I somehow expected --with-R-framework,  
> but configure neither warns about an unrecognized option, nor does it  
> take it as --enable-R-framework. Remember that R.framework isn't just  
> a different way to install R/dylib, but in future it will also unlock  
> the Obj-C code contained in the R.framework (hopefully) [i.e. to  
> justify --with in case it is meant for additional stuff whereas  
> --enable just pulls a lever somewhere ...].
>
> Merry Xmas!
> Simon
>
> platform powerpc-apple-darwin7.2.0
> arch     powerpc
> os       darwin7.2.0
> system   powerpc, darwin7.2.0
> status   Under development (unstable)
> major    1
> minor    9.0
> year     2003
> month    12
> day      22
> language R
>
> ---
> Simon Urbanek
> Department of computer oriented statistics and data analysis
> University of Augsburg
> Universit?tsstr. 14
> 86135 Augsburg
> Germany
>
> Tel: +49-821-598-2236
> Fax: +49-821-598-2200
>
> Simon.Urbanek@Math.Uni-Augsburg.de
> http://simon.urbanek.info
>
> ______________________________________________
> R-devel@stat.math.ethz.ch mailing list
> https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
>

stefano iacus

2003-Dec-22 22:03 UTC

head link

[Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes)

On Luned?, dic 22, 2003, at 19:53 Europe/Rome, Simon Urbanek wrote:
> Some issues with the recent R-devel (rsync today) on Darwin:
>
> 1) Recent R-devel is a bit misleading concerning the R-framework  
> installation:
> A new option --enable-R-framework was introduced, but  
> install-Rframework ignores its absence (or --disable-R-framework for  
> that matter) and tries to install the framework anyway in / which  
> fails just after the R itself was copied into /Versions/.... I know,  
> the user is to blame, but still, a simple check and stop (perhaps with  
> a hint to use --enable-R-framework) would be nice.
>
> 2) Wrong -install_name:
> configure.ac@1094:  LIBR_LDFLAGS="-dynamiclib -install_name  
> ${R_FRAMEWORK_DIR}/R.framework/Versions/${PACKAGE_VERSION}/Resources/ 
> bin/libR.dylib -compatibility_version ${PACKAGE_VERSION}   
> -current_version ${PACKAGE_VERSION}"
>
> R_FRAMEWORK_DIR specifies the full path including the framework name,  
> at least according to the previous definition:
>
> configure.ac@154:
>      if test "${want_R_framework}" = yes; then
> 	R_FRAMEWORK_DIR="/Library/Frameworks/R.framework"
>       else
> 	R_FRAMEWORK_DIR="${want_R_framework}/R.framework"
> 	want_R_framework=yes
>       fi
>
> therefore R.framework should be removed from the path at line 1094
>
> 3) Chicken-and-egg problem:
> There is a chicken-and-egg  problem if --enable-R-framework is used:
> gcc -bundle -flat_namespace -undefined suppress -L/usr/local/lib -o  
> R_X11.so  dataentry.lo devX11.lo rotated.lo rbitmap.lo  -lSM -lICE  
> -L/usr/X11R6/lib -lX11   -framework R -lz -lreadline -lcc_dynamic  
> -lncurses -lm
> ld: can't locate framework for: -framework R
> make[4]: *** [R_X11.so] Error 1
>
> --enable-framework adds: LIBR="-framework R" [configure.ac@173]
which
> is then used:
> src/modules/X11/Makefile.in@36: R_X11_la_LIBADD = $(ALL_X_LIBS)  
> $(BITMAP_LIBS) $(LIBR)
>
>  If you installed R.framework previously, you're fine (well, fine in a
> sense that R is not compiled against its own version of the shared  
> library as one would expect, but the currently installed R framework  
> instead). If you have a clean system, it won't even build.
>
> It is a touchy subject: during the compilation of R we cannot use the  
> framework as-is, since there is none. On the other hand once  
> installed, we want all packages to use -framework R.
>
> A partial solution is to "fake" a non-installed framework:
>
> Add following to the Makefile.in conditional for Darwin (probably  
> somewhere around src/main/Makefile.in@160):
> mkdir $(top_builddir)/bin/R.framework
> ln -s ../libR.dylib $(top_builddir)/bin/R.framework/R
>
> and add "-F$(top_builddir)/bin" to the LIBS
> The addition of -F.. to LIBS should be temporary during the build of R  
> only - I'm not sure if there is such a mechanism in the current R  
> building process though ... if there isn't we could just add something
> like $(LIBS_BUILD) or similar to all modules that are built before  
> install ...
>
> A side note: unfortunately gcc doesn't honor DYLD_FRAMEWORK_PATH, so  
> we cannot use that elegant solution :(
>
> 4) warnings - aqua module under construction?
> I guess the aqua code is currently under construction, because it's  
> probably compiled-in twice (in the libR and in aqua.so):
> [...]
> ld: warning multiple definitions of symbol _InitAquaIO
> aquaconsole.lo definition of _InitAquaIO in section (__TEXT,__text)
> /Work/R-builds/osx/r-devel/bin/R.framework/R(aqua.lo) definition of  
> _InitAquaIO
> [...many warnings of the same kind follow...]
>
well, I forgot to mention that when building framework, R is not  
(accidentally) built a dylib, so I think this is causing what you see.  
In the strategy we have in mind, building R as a framework implies R to  
be a shlib.

stefano
> I didn't invesitgate this further - if this is not intentional then I  
> could have a look ... I suspect that this has something to do with  
> Stefano's attempt to separate Carbon code (aqua+quartz) from the core  
> R so it can be used from an external terminal w/o root privileges.
>
> 5) --enable vs. --with:
> I have a rather general question about configure options: why use the  
> name --"with"-aqua but --"enable"-R-framework ? I'm
just curious:
> after --with-zlib --with-aqua I somehow expected --with-R-framework,  
> but configure neither warns about an unrecognized option, nor does it  
> take it as --enable-R-framework. Remember that R.framework isn't just  
> a different way to install R/dylib, but in future it will also unlock  
> the Obj-C code contained in the R.framework (hopefully) [i.e. to  
> justify --with in case it is meant for additional stuff whereas  
> --enable just pulls a lever somewhere ...].
>
> Merry Xmas!
> Simon
>
> platform powerpc-apple-darwin7.2.0
> arch     powerpc
> os       darwin7.2.0
> system   powerpc, darwin7.2.0
> status   Under development (unstable)
> major    1
> minor    9.0
> year     2003
> month    12
> day      22
> language R
>
> ---
> Simon Urbanek
> Department of computer oriented statistics and data analysis
> University of Augsburg
> Universit?tsstr. 14
> 86135 Augsburg
> Germany
>
> Tel: +49-821-598-2236
> Fax: +49-821-598-2200
>
> Simon.Urbanek@Math.Uni-Augsburg.de
> http://simon.urbanek.info
>
> ______________________________________________
> R-devel@stat.math.ethz.ch mailing list
> https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
>

Maybe Matching Threads

Search for more maybe matching threads

R devel - Dec 2003 - R-devel with Darwin: some issues (mostly due to latest R.framework changes)

[Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes)

[Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes)

[Rd] R-devel with Darwin: some issues (mostly due to latest R.framework changes)

Maybe Matching Threads