1N/AIf you read this file _as_is_, just ignore the funny characters you
1N/Aspecifically designed to be readable as is.
1N/AThis document describes various features of Sun's Solaris operating system
1N/Athat will affect how Perl version 5 (hereafter just perl) is
1N/Acompiled
and/or runs. Some issues relating to the older SunOS
4.x are
1N/Aalso discussed, though they may be out of date.
1N/AFor the most part, everything should just work.
1N/AStarting with Solaris 8, perl5.00503 (or higher) is supplied with the
1N/Aoperating system, so you might not even need to build a newer version
1N/Aof perl at all. The Sun-supplied version is installed in
/usr/perl5 1N/Athat installation unless you really know what you are doing. If you
1N/Aremove the perl supplied with the OS, you will render some bits of
1N/Ayour system inoperable. If you wish to install a newer version of perl,
1N/Ainstall it under a different prefix from
/usr/perl5. Common prefixes
1N/AYou may wish to put your version of perl in the PATH of all users by
1N/Ashipped with Solaris use an explicit path. Solaris ships with a
1N/Arange of Solaris-specific modules. If you choose to install your own
1N/Aversion of perl you will find the source of many of these modules is
1N/Aavailable on CPAN under the Sun::Solaris:: namespace.
1N/ASolaris may include two versions of perl,
e.g. Solaris 9 includes
1N/Aboth 5.005_03 and 5.6.1 and Solaris 10 includes both 5.6.1 and 5.8.3.
1N/AThis is to provide stability across Solaris releases, in cases where
1N/Aa later perl version has incompatibilities with the version included
1N/Ain the preceeding Solaris release. The default perl version will always
1N/Abe the most recent, and in general the old version will only be
1N/Aretained for one Solaris release. Note also that the default perl will
1N/ANOT be configured to search for modules in the older version, again due
1N/Athat you installed for the previous Solaris version. See the CPAN manpage
1N/Aunder 'autobundle' for a quick way of doing this.
1N/AAs an interim measure, you may either change the #! line of your
1N/Ascripts to specifically refer to the old perl version,
e.g. on
1N/Athat was the default for Solaris 9, or if you have a large number of
1N/Ascripts it may be more convenient to make the old version of perl the
1N/Adefault on your system. You can do this by changing the appropriate
1N/AIn both cases this should only be considered to be a temporary
1N/Ameasure - you should upgrade to the later version of perl as soon as
1N/ANote also that the perl command-line utilities (
e.g. perldoc) and any
1N/Athat are added by modules that you install will be under
1N/AIf you wish to build and install add-on modules from CPAN using gcc, you can do
1N/A=head2 Solaris Version Numbers.
1N/AFor consistency with common usage, perl's Configure script performs
1N/Asome minor manipulations on the operating system name and version
1N/Anumber as reported by uname. Here's a partial translation table:
1N/A Sun: perl's Configure:
1N/A uname uname -r Name osname osvers
1N/A SunOS 4.1.3 Solaris 1.1 sunos 4.1.3
1N/A SunOS 5.6 Solaris 2.6 solaris 2.6
1N/A SunOS 5.8 Solaris 8 solaris 2.8
1N/A SunOS 5.9 Solaris 9 solaris 2.9
1N/A SunOS 5.10 Solaris 10 solaris 2.10
1N/AThe complete table can be found in the Sun Managers' FAQ
1N/A"9.1) Which Sun models run which versions of SunOS?".
1N/AThere are many, many sources for Solaris information. A few of the
1N/Aimportant ones for perl:
1N/AThe Solaris FAQ is available at
1N/AThe Sun Managers' FAQ is available at
1N/A=item Precompiled Binaries
1N/APrecompiled binaries, links to many sites, and much, much more are
1N/A=item Solaris Documentation
1N/A=head2 File Extraction Problems on Solaris.
1N/ABe sure to use a tar program compiled under Solaris (not SunOS
4.x)
1N/Afor SunOS4 on Solaris. (GNU tar compiled for Solaris should be fine.)
1N/AWhen you run SunOS4 binaries on Solaris, the run-time system magically
1N/Aalters pathnames matching m#
lib/locale# so that when tar tries to create
1N/AIf you found this advice too late and used a SunOS4-compiled tar
1N/Aanyway, you must find the incorrectly renamed file and move it back
1N/A=head2 Compiler and Related Tools on Solaris.
1N/AYou must use an ANSI C compiler to build perl. Perl can be compiled
1N/Awith either Sun's add-on C compiler or with gcc. The C compiler that
1N/Ashipped with SunOS4 will not do.
1N/ASeveral tools needed to build perl are located in
/usr/bin/: ar,
1N/Aas, ld, and make. Make sure that
/usr/bin/ is in your PATH.
1N/AYou need to make sure the following packages are installed
1N/A(this info is extracted from the Solaris FAQ):
1N/Afor tools (sccs, lex, yacc, make, nm, truss, ld, as): SUNWbtool,
1N/Afor libraries & headers: SUNWhea, SUNWarc, SUNWlibm, SUNWlibms, SUNWdfbh,
1N/ASUNWcg6h, SUNWxwinc, SUNWolinc
1N/Afor 64 bit development: SUNWarcx, SUNWbtoox, SUNWdplx, SUNWscpux,
1N/ASUNWsprox, SUNWtoox, SUNWlmsx, SUNWlmx, SUNWlibCx
1N/AIf you are in doubt which package contains a file you are missing,
1N/Atry to find an installation that has that file. Then do a
1N/AThis will display a line like this:
1N/AThe last item listed (SUNWhea in this example) is the package you need.
1N/AYou don't need to have
/usr/ucb/ in your PATH to build perl. If you
1N/Ain your PATH before the directory containing the right C compiler.
1N/A=head3 Sun's C Compiler
1N/AIf you use Sun's C compiler, make sure the correct directory
1N/AIf you use gcc, make sure your installation is recent and complete.
1N/Aperl versions since 5.6.0 build fine with gcc > 2.8.1 on Solaris >=
1N/AYou must Configure perl with
1N/A $ sh Configure -Dcc=gcc
1N/AIf you don't, you may experience strange build errors.
1N/AIf you have updated your Solaris version, you may also have to update
1N/Ayour gcc. For example, if you are running Solaris 2.6 and your gcc is
1N/Asure you have the appropriate directory, sparc-sun-solaris2.6/ or
1N/Ai386-pc-solaris2.6/. If gcc's directory is for a different version of
1N/ASolaris than you are running, then you will need to rebuild gcc for
1N/Ayour new version of Solaris.
1N/AYou can get a precompiled version of gcc from
1N/Asure you pick up the package for your Solaris release.
1N/AIf you wish to use gcc to build add-on modules for use with the perl
1N/Ashipped with Solaris, you should use the Solaris::PerlGcc module
1N/Awhich is available from CPAN. The perl shipped with Solaris
1N/Ais configured and built with the Sun compilers, and the compiler
1N/Aconfiguration information stored in
Config.pm is therefore only
1N/Arelevant to the Sun compilers. The Solaris:PerlGcc module contains a
1N/Areplacement
Config.pm that is correct for gcc - see the module for
1N/A=head3 GNU as and GNU ld
1N/AThe following information applies to gcc version 2. Volunteers to
1N/Aupdate it as appropropriate for gcc version 3 would be appreciated.
1N/AThe versions of as and ld supplied with Solaris work fine for building
1N/Aperl. There is normally no need to install the GNU versions to
1N/AIf you decide to ignore this advice and use the GNU versions anyway,
1N/Athen be sure that they are relatively recent. Versions newer than 2.7
1N/Aare apparently new enough. Older versions may have trouble with
1N/AIf you wish to use GNU ld, then you need to pass it the -Wl,-E flag.
1N/Athe following Configure variables:
1N/A ccdlflags="$ccdlflags -Wl,-E"
1N/A lddlflags="$lddlflags -Wl,-E -G"
1N/AHowever, over the years, changes in gcc, GNU ld, and Solaris ld have made
1N/Ait difficult to automatically detect which ld ultimately gets called.
1N/AYou may have to manually edit
config.sh and add the -Wl,-E flags
1N/Ayourself, or else run Configure interactively and add the flags at the
1N/AIf your gcc is configured to use GNU as and ld but you want to use the
1N/ASolaris ones instead to build perl, then you'll need to add
1N/A-B
/usr/bin/ to the gcc command line. One convenient way to do
1N/ANote that the trailing slash is required. This will result in some
1N/Aharmless warnings as Configure is run:
1N/AThese messages may safely be ignored.
1N/A(Note that for a SunOS4 system, you must use -B/bin/ instead.)
1N/AAlternatively, you can use the GCC_EXEC_PREFIX environment variable to
1N/Aensure that Sun's as and ld are used. Consult your gcc documentation
1N/Afor further information on the -B option and the GCC_EXEC_PREFIX variable.
1N/A=head3 Sun and GNU make
1N/AThe make under
/usr/bin works fine for building perl. If you
1N/Ahave the Sun C compilers, you will also have a parallel version of
1N/Amake (dmake). This works fine to build perl, but can sometimes cause
1N/Aproblems when running 'make test' due to underspecified dependencies
1N/Abetween the different test harness files. The same problem can also
1N/Aaffect the building of some add-on modules, so in those cases either
1N/Aspecify '-m serial' on the dmake command line, or use
1N/Athe set-group-id bit is not set. If it is, then arrange your PATH so
1N/Aadministrator disable the set-group-id bit on GNU make.
1N/APerl will not build and run correctly if linked against -lucb since it
1N/Acontains routines that are incompatible with the standard Solaris libc.
1N/ANormally this is not a problem since the solaris hints file prevents
1N/Aexplicitly omits -lucb.
1N/A=head2 Environment for Compiling perl on Solaris
1N/Ausing Sun's compiler) as well as
/usr/bin/ to pick up the other
1N/Adevelopment tools (such as make, ar, as, and ld). Make sure your path
1N/Aeither doesn't include
/usr/ucb or that it includes it after the
1N/Acompiler and compiler tools and other standard Solaris directories.
1N/A=head3 LD_LIBRARY_PATH
1N/AIf you have the LD_LIBRARY_PATH environment variable set, be sure that
1N/Ait does NOT include /lib or
/usr/lib. If you will be building
1N/Aextensions that call third-party shared libraries (
e.g. Berkeley DB)
1N/Athen make sure that your LD_LIBRARY_PATH environment variable includes
1N/AIf you get an error message
1N/A dlopen: stub interception failed
1N/Ait is probably because your LD_LIBRARY_PATH environment variable
1N/Aincludes a directory which is a symlink to
/usr/lib (such as /lib).
1N/AThe reason this causes a problem is quite subtle. The file
1N/Ainterception failed' errors! The runtime linker intercepts links to
1N/Afunctions instead. [Thanks to Tim Bunce for this explanation.]
1N/A=head1 RUN CONFIGURE.
1N/ASee the INSTALL file for general information regarding Configure.
1N/AOnly Solaris-specific issues are discussed here. Usually, the
1N/Adefaults should be fine.
1N/A=head2 64-bit perl on Solaris.
1N/ASee the INSTALL file for general information regarding 64-bit compiles.
1N/AIn general, the defaults should be fine for most people.
1N/ABy default, perl-5.6.0 (or later) is compiled as a 32-bit application
1N/Awith largefile and long-long support.
1N/A=head3 General 32-bit vs. 64-bit issues.
1N/ASolaris 7 and above will run in either 32 bit or 64 bit mode on SPARC
1N/ACPUs, via a reboot. You can build 64 bit apps whilst running 32 bit
1N/Amode and vice-versa. 32 bit apps will run under Solaris running in
1N/Aeither 32 or 64 bit mode. 64 bit apps require Solaris to be running
1N/AExisting 32 bit apps are properly known as LP32,
i.e. Longs and
1N/APointers are 32 bit. 64-bit apps are more properly known as LP64.
1N/AThe discriminating feature of a LP64 bit app is its ability to utilise a
1N/A64-bit address space. It is perfectly possible to have a LP32 bit app
1N/Athat supports both 64-bit integers (long long) and largefiles (> 2GB),
1N/Aand this is the default for perl-5.6.0.
1N/AFor a more complete explanation of 64-bit issues, see the
1N/AYou can detect the OS mode using "isainfo -v",
e.g. 1N/A $ isainfo -v # Ultra 30 in 64 bit mode
1N/A 64-bit sparcv9 applications
1N/A 32-bit sparc applications
1N/ABy default, perl will be compiled as a 32-bit application. Unless
1N/Ayou want to allocate more than ~ 4GB of memory inside perl, or unless
1N/Ayou need more than 255 open file descriptors, you probably don't need
1N/Aperl to be a 64-bit app.
1N/A=head3 Large File Support
1N/AFor Solaris 2.6 and onwards, there are two different ways for 32-bit
1N/Aapplications to manipulate large files (files whose size is > 2GByte).
1N/A(A 64-bit application automatically has largefile support built in
1N/AFirst is the "transitional compilation environment", described in
1N/Alfcompile64(5). According to the man page,
1N/A The transitional compilation environment exports all the
1N/A explicit 64-bit functions (xxx64()) and types in addition to
1N/A all the regular functions (xxx()) and types. Both xxx() and
1N/A xxx64() functions are available to the program source. A
1N/A 32-bit application must use the xxx64() functions in order
1N/A to access large files. See the lf64(5) manual page for a
1N/A complete listing of the 64-bit transitional interfaces.
1N/AThe transitional compilation environment is obtained with the
1N/Afollowing compiler and linker flags:
1N/A getconf LFS64_CFLAGS -D_LARGEFILE64_SOURCE
1N/A getconf LFS64_LDFLAG # nothing special needed
1N/A getconf LFS64_LIBS # nothing special needed
1N/ASecond is the "large file compilation environment", described in
1N/Alfcompile(5). According to the man page,
1N/A Each interface named xxx() that needs to access 64-bit entities
1N/A to access large files maps to a xxx64() call in the
1N/A resulting binary. All relevant data types are defined to be
1N/A of correct size (for example, off_t has a typedef definition
1N/A for a 64-bit entity).
1N/A An application compiled in this environment is able to use
1N/A the xxx() source interfaces to access both large and small
1N/A files, rather than having to explicitly utilize the transitional
1N/A xxx64() interface calls to access large files.
1N/ATwo exceptions are fseek() and ftell(). 32-bit applications should
1N/Ause fseeko(3C) and ftello(3C). These will get automatically mapped
1N/Ato fseeko64() and ftello64().
1N/AThe large file compilation environment is obtained with
1N/A getconf LFS_CFLAGS -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
1N/A getconf LFS_LDFLAGS # nothing special needed
1N/A getconf LFS_LIBS # nothing special needed
1N/ABy default, perl uses the large file compilation environment and
1N/Arelies on Solaris to do the underlying mapping of interfaces.
1N/A=head3 Building an LP64 perl
1N/ATo compile a 64-bit application on an UltraSparc with a recent Sun Compiler,
1N/Ayou need to use the flag "-xarch=v9". getconf(1) will tell you this,
e.g. 1N/A $ getconf -a | grep v9
1N/A XBS5_LP64_OFF64_CFLAGS: -xarch=v9
1N/A XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
1N/A XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
1N/A XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
1N/A XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
1N/A XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
1N/A _XBS5_LP64_OFF64_CFLAGS: -xarch=v9
1N/A _XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
1N/A _XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
1N/A _XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
1N/A _XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
1N/A _XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
1N/AThis flag is supported in Sun WorkShop Compilers 5.0 and onwards
1N/A(now marketed under the name Forte) when used on Solaris 7 or later on
1N/AIf you are using gcc, you would need to use -mcpu=v9 -m64 instead. This
1N/A GCC version 2.95 is not able to compile code correctly for sparc64
1N/A targets. Users of the Linux kernel, at least, can use the sparc32
1N/A program to start up a new shell invocation with an environment that
1N/A causes configure to recognize (via uname -a) the system as sparc-*-*
1N/AAll this should be handled automatically by the hints file, if
1N/AAs of 5.8.1, long doubles are working if you use the Sun compilers
1N/A(needed for additional math routines not included in libm).
1N/A=head2 Threads in perl on Solaris.
1N/AIt is possible to build a threaded version of perl on Solaris. The entire
1N/Aperl thread implementation is still experimental, however, so beware.
1N/A=head2 Malloc Issues with perl on Solaris.
1N/AStarting from perl 5.7.1 perl uses the Solaris malloc, since the perl
1N/Amalloc breaks when dealing with more than 2GB of memory, and the Solaris
1N/Amalloc also seems to be faster.
1N/AIf you for some reason (such as binary backward compatibility) really
1N/Aneed to use perl's malloc, you can rebuild perl from the sources
1N/Aand Configure the build with
1N/A $ sh Configure -Dusemymalloc
1N/AYou should not use perl's malloc if you are building with gcc. There
1N/Aare reports of core dumps, especially in the PDL module. The problem
1N/Aappears to go away under -DDEBUGGING, so it has been difficult to
1N/Atrack down. Sun's compiler appears to be okay with or without perl's
1N/Amalloc. [XXX further investigation is needed here.]
1N/A=head1 MAKE PROBLEMS.
1N/A=item Dynamic Loading Problems With GNU as and GNU ld
1N/AIf you have problems with dynamic loading using gcc on SunOS or
1N/ASolaris, and you are using GNU as and GNU ld, see the section
1N/AL<"GNU as and GNU ld"> above.
1N/AIf you get this message on SunOS or Solaris, and you're using gcc,
1N/Ait's probably the GNU as or GNU ld problem in the previous item
1N/AL<"GNU as and GNU ld">.
1N/A=item dlopen: stub interception failed
1N/AThe primary cause of the 'dlopen: stub interception failed' message is
1N/Athat the LD_LIBRARY_PATH environment variable includes a directory
1N/AL<"LD_LIBRARY_PATH"> above.
1N/A=item #error "No DATAMODEL_NATIVE specified"
1N/AThis is a common error when trying to build perl on Solaris 2.6 with a
1N/Agcc installation from Solaris 2.5 or 2.5.1. The Solaris header files
1N/Achanged, so you need to update your gcc installation. You can either
1N/Arerun the fixincludes script from gcc or take the opportunity to
1N/Aupdate your gcc installation.
1N/A=item sh: ar: not found
1N/AThis is a message from your shell telling you that the command 'ar'
1N/Awas not found. You need to check your PATH environment variable to
1N/Amake sure that it includes the directory with the 'ar' command. This
1N/Ais a common problem on Solaris, where 'ar' is in the
/usr/bin/
1N/Aop/stat.t test 4 may fail if you are on a tmpfs of some sort.
1N/ABuilding in /tmp sometimes shows this behavior. The
1N/Atest suite detects if you are building in /tmp, but it may not be able
1N/Ato catch all tmpfs situations.
1N/A=head1 PREBUILT BINARIES OF PERL FOR SOLARIS.
1N/AYou can pick up prebuilt binaries for Solaris from
1N/Apage. There are probably other sources as well. Please note that
1N/Athese sites are under the control of their respective owners, not the
1N/A=head1 RUNTIME ISSUES FOR PERL ON SOLARIS.
1N/A=head2 Limits on Numbers of Open Files on Solaris.
1N/AThe stdio(3C) manpage notes that for LP32 applications, only 255
1N/Afiles may be opened using fopen(), and only file descriptors 0
1N/Athrough 255 can be used in a stream. Since perl calls open() and
1N/Athen fdopen(3C) with the resulting file descriptor, perl is limited
1N/Ato 255 simultaneous open files, even if sysopen() is used. If this
1N/Aproves to be an insurmountable problem, you can compile perl as a
1N/ALP64 application, see L<Building an LP64 perl> for details. Note
1N/Aalso that the default resource limit for open file descriptors on
1N/ASolaris is 255, so you will have to modify your ulimit or rctl
1N/A(Solaris 9 onwards) appropriately.
1N/A=head1 SOLARIS-SPECIFIC MODULES.
1N/ASee the modules under the Solaris:: and Sun::Solaris namespaces on CPAN,
1N/A=head1 SOLARIS-SPECIFIC PROBLEMS WITH MODULES.
1N/A=head2 Proc::ProcessTable on Solaris
1N/AProc::ProcessTable does not compile on Solaris with perl5.6.0 and higher
1N/Aif you have LARGEFILES defined. Since largefile support is the
1N/Adefault in 5.6.0 and later, you have to take special steps to use this
1N/AThe problem is that various structures visible via procfs use off_t,
1N/Aand if you compile with largefile support these change from 32 bits to
1N/A64 bits. Thus what you get back from procfs doesn't match up with
1N/Athe structures in perl, resulting in garbage. See proc(4) for further
1N/AA fix for Proc::ProcessTable is to edit Makefile to
1N/Aexplicitly remove the largefile flags from the ones MakeMaker picks up
1N/Afrom
Config.pm. This will result in Proc::ProcessTable being built
1N/Aunder the correct environment. Everything should then be OK as long as
1N/AProc::ProcessTable doesn't try to share off_t's with the rest of perl,
1N/Aor if it does they should be explicitly specified as off64_t.
1N/A=head2 BSD::Resource on Solaris
1N/ABSD::Resource versions earlier than 1.09 do not compile on Solaris
1N/Awith perl 5.6.0 and higher, for the same reasons as Proc::ProcessTable.
1N/ABSD::Resource versions starting from 1.09 have a workaround for the problem.
1N/A=head2 Net::SSLeay on Solaris
1N/Aavailable from Solaris 9 onwards. For earlier Solaris versions you
1N/Acan either get the package SUNWski (packaged with several Sun
1N/Asoftware products, for example the Sun WebServer, which is part of
1N/Athe Solaris Server Intranet Extension, or the Sun Directory Services,
1N/Apart of Solaris for ISPs) or download the ANDIrand package from
1N/AIt may be possible to use the Entropy Gathering Daemon (written in
1N/Asince the more recent versions of GNU ld (like 2.13) do not seem to
1N/Awork for building Perl anymore. When linking the extensions, the
1N/AGNU ld gets very unhappy and spews a lot of errors like this
1N/A ... relocation truncated to fit: BASE13 ...
1N/Aand dies. Therefore the SunOS 4.1 hints file explicitly sets the
1N/AAs of Perl 5.8.1 the dynamic loading of libraries (DynaLoader, XSLoader)
1N/Aalso seems to have become broken in in SunOS
4.x. Therefore the default
1N/Ais to build Perl statically.
1N/ARunning the test suite in SunOS 4.1 is a bit tricky since the
1N/Aunknown reason. Just stop the test and kill that particular Perl
1N/AThere are various other failures, that as of SunOS 4.1.4 and gcc 3.2.2
1N/Alook a lot like gcc bugs. Many of the failures happen in the Encode
1N/Atests, where for example when the test expects "0" you get "0"
1N/Awhich should after a little squinting look very odd indeed.
1N/Aexpected but the test fails because the result is chr(0xff). Exactly.
1N/AThis is the "make test" result from the said combination:
1N/A Failed 27 test scripts out of 745, 96.38% okay.
1N/ARunning the C<harness> is painful because of the many failing
1N/AUnicode-related tests will output megabytes of failure messages,
1N/Abut if one patiently waits, one gets these results:
1N/A Failed Test Stat Wstat Total Fail Failed List of Failed
1N/A -----------------------------------------------------------------------------
1N/A Failed Test Stat Wstat Total Fail Failed List of Failed
1N/A ------------------------------------------------------------------------------
1N/A 56 tests and 467 subtests skipped.
1N/A Failed 27/811 test scripts, 96.67% okay. 1383/75399 subtests failed, 98.17% okay.
1N/AThe alarm() test failure is caused by system() apparently blocking
1N/Aalarm(). That is probably a libc bug, and given that SunOS
4.x 1N/Ahas been end-of-lifed years ago, don't hold your breath for a fix.
1N/AIn addition to that, don't try anything too Unicode-y, especially
1N/Awith Encode, and you should be fine in SunOS
4.x. 1N/AThe original was written by Andy Dougherty F<doughera@lafayette.edu>
1N/Adrawing heavily on advice from Alan Burlison, Nick Ing-Simmons, Tim Bunce,
1N/Aand many other Solaris users over the years.
1N/APlease report any errors, updates, or suggestions to F<perlbug@perl.org>.