Differences between revisions 42 and 43
Revision 42 as of 2007-09-08 13:31:49
Size: 11743
Comment:
Revision 43 as of 2007-09-08 13:43:12
Size: 11743
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
With the kind help of Dirk Van Hertem <dirk.vanhertem@ieee.org> and Boris (?) <boris@mogwitz.eu> we have managed to build the ROOT packages on hppa and mips.  With the kind help of Dirk Van Hertem <dirk.vanhertem@ieee.org> and Boris (?) <boris@mogwitz.eu> we have managed to build the ROOT packages on hppa and mips.
Line 13: Line 13:
That brings the list of supported and confirmed architectures up to 
||<|2>byte order|| || ||
||word size || little-endian || big-endian||
||
32-bit || i386 || powerpc, mips, hppa||
||64-bit || amd64 || || 
That brings the list of supported and confirmed architectures up to
|| '''byte order/word size''' || ''little-endian'' || ''big-endian'' ||
|| ''32-bit'' || i386 || powerpc, mips, hppa ||
|| ''64-bit'' || amd64 || ||
Line 19: Line 18:
The list of unconfirmed architectures is now {{{
byte order | |
word size  | little-endian | big-endian  -----------+---------------+---------------------
32-bit     | mipsel, arm | armeb[*], m68k,
           | |
sparc, s390
64 bit     | ia64, alpha | powerpc64[*],             | | s390x[*], sparc64[*]
        

[*] Experimental or not fully supported ports.  }}}
Apart from that, there's a number of non-linux ports, like{{{
hurd-i386, netbsd-i386, netbsd-alpha, kfreebsd-gnu
}}}
The list of unconfirmed architectures is now
|| '''
byte order/word size''' || ''little-endian'' || ''big-endian'' ||
|| ''
32-bit'' || mipsel, arm || armeb[*], m68k, sparc, s390 ||
|| ''
64 bit'' || ia64, alpha || powerpc64[*], s390x[*], sparc64[*] ||

[*] Experimental or not fully supported ports.

Apart from that, there's a number of non-linux ports, like

|| '''byte order/word size''' || ''little-endian'' || ''big-endian'' ||
|| ''32-bit'' ||
hurd-i386, netbsd-i386, kfreebsd-gnu || ||
|| ''64-bit'' || netbsd-alpha || ||
Line 34: Line 32:
haven't tried it in a very long time.  haven't tried it in a very long time.
Line 43: Line 41:
 1. If the generic {{{linux}}} arch does not fit the machine (e.g., 64bit word-size, or big-endian, unsupported compiler options, or the like), we need to define a new platform.  
   i. Look for a similar architecture, and copy that architectures {{{config/Makefile.linux}}}''other'' to {{{config/Makefile}}}''foo''.  
 1. If the generic {{{linux}}} arch does not fit the machine (e.g., 64bit word-size, or big-endian, unsupported compiler options, or the like), we need to define a new platform.
   i. Look for a similar architecture, and copy that architectures {{{config/Makefile.linux}}}''other'' to {{{config/Makefile}}}''foo''.
Line 52: Line 50:
   i. In {{{config/root-config.in}}} add an appropriate entry for the new architecture {{{     i. In {{{config/root-config.in}}} add an appropriate entry for the new architecture {{{
Line 79: Line 77:
 to see a list of GCC predefined pre-processor symbols. Look for an chip definition (e.g., {{{__i386__}}}, {{{__powerpc__}}}). If no valid entry exists in {{{base/inc/RConfig.h}}}, then add something like {{{#!cplusplus   to see a list of GCC predefined pre-processor symbols. Look for an chip definition (e.g., {{{__i386__}}}, {{{__powerpc__}}}). If no valid entry exists in {{{base/inc/RConfig.h}}}, then add something like {{{#!cplusplus
Line 92: Line 90:
 1.#4 Check that the chip/os combo is properly detected in {{{clib/src/Getline.c}}}. The generic entries may be OK - that is the pre-processor conditional {{{#!cplusplus   1.#4 Check that the chip/os combo is properly detected in {{{clib/src/Getline.c}}}. The generic entries may be OK - that is the pre-processor conditional {{{#!cplusplus
Line 108: Line 106:
 the ''second'' POSIX branch will be chosen ({{{termios.h}}} is included). If not, add detection code as for for example {{{R__MIPSLINUX}}} and include that define in the BSD excluded list above.   the ''second'' POSIX branch will be chosen ({{{termios.h}}} is included). If not, add detection code as for for example {{{R__MIPSLINUX}}} and include that define in the BSD excluded list above.
Line 110: Line 108:
Non-Linux platforms may need more work. The basic thing is to assume that the OS is like Linux, except of course, if there's a closer alternative, like BSD or Cygwin.  Non-Linux platforms may need more work. The basic thing is to assume that the OS is like Linux, except of course, if there's a closer alternative, like BSD or Cygwin.
Line 114: Line 112:
See end of bug [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325306 325306].  See end of bug [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325306 325306].
Line 116: Line 114:
You will be able to use your favorite "experimental" mirror to download and install the packages. Just put  You will be able to use your favorite "experimental" mirror to download and install the packages. Just put
Line 120: Line 118:
where '''NN''' is your mirror country code, into your ''/etc/apt/sources.list'' or ''/etc/apt/sources.list.d/experimental.list''. 
 
where '''NN''' is your mirror country code, into your ''/etc/apt/sources.list'' or ''/etc/apt/sources.list.d/experimental.list''.
Line 126: Line 124:
 * Unfortunately the next production release of ROOT, '''5.16.00''', is not expected until post-Etch, but we intend to upload ROOT 5.16 to [http://backports.org backports.org] for Etch users once it is in unstable.   * Unfortunately the next production release of ROOT, '''5.16.00''', is not expected until post-Etch, but we intend to upload ROOT 5.16 to [http://backports.org backports.org] for Etch users once it is in unstable.
Line 134: Line 132:
   * These packages were unfortunately rejected due to "too generic name". We (KevinMcCarty and ChristianHolm) have asked the FTP masters for input on names that would be acceptable, but so far we have had no response.     * These packages were unfortunately rejected due to "too generic name". We (KevinMcCarty and ChristianHolm) have asked the FTP masters for input on names that would be acceptable, but so far we have had no response.
Line 142: Line 140:
 * ROOT [http://lists.debian.org/debian-science/2005/08/msg00056.html provides a direct way to build deb packages from the sources] but is not in Debian main. 
   * See [http://mirror.phy.bnl.gov/debian-root/ the unofficial ROOT deb repository] for some build instructions and a repository for unstable (i386, amd64, powerpc) and stable (i386 only). 
 * ROOT [http://lists.debian.org/debian-science/2005/08/msg00056.html provides a direct way to build deb packages from the sources] but is not in Debian main.
   * See [http://mirror.phy.bnl.gov/debian-root/ the unofficial ROOT deb repository] for some build instructions and a repository for unstable (i386, amd64, powerpc) and stable (i386 only).
Line 147: Line 145:
 
Line 149: Line 147:
 
The approach is that the ROOT source tree contains [http://root.cern.ch/viewcvs/build/package/lib/ scripts] and [http://root.cern.ch/viewcvs/build/package/common templates] to deal with packaging in general (that is for Debian and RPM), as well as some [http://root.cern.ch/viewcvs/build/package/debian Debian] and [http://root.cern.ch/viewcvs/build/package/redhat RPM] specific templates.   
     

The approach is that the ROOT source tree contains [http://root.cern.ch/viewcvs/build/package/lib/ scripts] and [http://root.cern.ch/viewcvs/build/package/common templates] to deal with packaging in general (that is for Debian and RPM), as well as some [http://root.cern.ch/viewcvs/build/package/debian Debian] and [http://root.cern.ch/viewcvs/build/package/redhat RPM] specific templates.
Line 156: Line 154:
In the eventual "official" Debian packages to come, the package maintainer would presumably run these two commands himself before '''dpkg-buildpackage''', and the results of the commands (for instance the debian/ directory) would therefore enter into the diff.gz of the source package. Thus the source package uploaded to Debian would always be buildable with the normal steps of '''dpkg-buildpackage -rfakeroot'''.   In the eventual "official" Debian packages to come, the package maintainer would presumably run these two commands himself before '''dpkg-buildpackage''', and the results of the commands (for instance the debian/ directory) would therefore enter into the diff.gz of the source package. Thus the source package uploaded to Debian would always be buildable with the normal steps of '''dpkg-buildpackage -rfakeroot'''.

1. ROOT for DebianScience

Obsolete text formerly on this page has been archived at ["DebianScienceROOT/Obsolete"].

1.1. Port status (8/9/2007): 2 more architectures, mips and hppa

With the kind help of Dirk Van Hertem <dirk.vanhertem@ieee.org> and Boris (?) <boris@mogwitz.eu> we have managed to build the ROOT packages on hppa and mips.

That brings the list of supported and confirmed architectures up to

byte order/word size

little-endian

big-endian

32-bit

i386

powerpc, mips, hppa

64-bit

amd64

The list of unconfirmed architectures is now

byte order/word size

little-endian

big-endian

32-bit

mipsel, arm

armeb[*], m68k, sparc, s390

64 bit

ia64, alpha

powerpc64[*], s390x[*], sparc64[*]

[*] Experimental or not fully supported ports.

Apart from that, there's a number of non-linux ports, like

byte order/word size

little-endian

big-endian

32-bit

hurd-i386, netbsd-i386, kfreebsd-gnu

64-bit

netbsd-alpha

which have not been tested. In principle it should work on HURD but I haven't tried it in a very long time.

1.2. Porting notes

When porting to a non i386 platform not already supported for Linux, the following points should be considered.

  1. Enable auto-detection in configure. This normally involves figuring out what platform uname -m returns, and then add something like

          linux:<arch>*:*)      arch=linux ;;
  2. If the generic linux arch does not fit the machine (e.g., 64bit word-size, or big-endian, unsupported compiler options, or the like), we need to define a new platform.

    1. Look for a similar architecture, and copy that architectures config/Makefile.linuxother to config/Makefilefoo.

    2. Set the definition in configure to

            linux:<arch>*:*)      arch=linux<foo> ;;

      where <foo> is the Debian system name.

    3. Add an entry for the architecture to config/ARCHS

      linuxfoo             for FOO Linux gcc and glibc
    4. In config/root-config.in add an appropriate entry for the new architecture

      linuxfoo)
         # Linux with gcc >= 3.x
         auxcflags="-m32"   # replace with -m64 for 64bit machines
         auxldflags="-m32"  # replace with -m64 for 64bit machines
         auxlibs="-lm -ldl -rdynamic"
         ;;
    5. In test/Makefile.arch add appropriate lines for the new architecture.

      ifeq ($(ARCH),linux)
      # Linux with egcs, gcc 2.9x, gcc 3.x
      CXX           = g++
      CXXFLAGS      = $(OPT2) -Wall -fPIC
      LD            = g++
      LDFLAGS       = $(OPT2)
      SOFLAGS       = -shared
      endif
    6. Check that the platform is properly identified by the XRootd in the xrootd/src/xrootd/configure.classic script

             linux:foo*:*)    arch=foo_linux      ; platform=linux; ccflv=gcc;;
    7. Also add an entry to xrootd/src/xrootd/ARCHS

      foo_linux       gcc       all    for GNU/Linux on FOO
  3. Check that the system is properly recognized in base/inc/RConfig.h. Run

     touch dummy_file.c; gcc -E -dM dummy_file.c

    to see a list of GCC predefined pre-processor symbols. Look for an chip definition (e.g., __i386__, __powerpc__). If no valid entry exists in base/inc/RConfig.h, then add something like

       1 #if defined(linux) && defined(<cpp_arch>)
       2 #   define R__LINUX
       3 #   define R__UNIX
       4 #   define NEED_SIGJMP
       5 #   if defined(_ABI64) // For 64-bit word size
       6 #      define R__B64
       7 #   endif
       8 #   if defined(__BYTE_ORDER) && __BYTE_ORDER == __LITTLE_ENDIAN
       9 #      define R__BYTESWAP // For little endian machines
      10 #   endif
      11 #endif
      12 
    
  4. Check that the chip/os combo is properly detected in clib/src/Getline.c. The generic entries may be OK - that is the pre-processor conditional

       1 #if defined(TIOCGETP) && !defined(__sgi) && !defined(R__PPCLINUX) && \
       2     !defined(R__ALPHALINUX)  && !defined(R__MIPSLINUX) /* use BSD interface if possible */
       3 #include <sgtty.h>
       4 struct sgttyb   new_tty, old_tty;
       5 struct tchars   tch;
       6 struct ltchars  ltch;
       7 #else
       8 #ifdef SIGTSTP          /* need POSIX interface to handle SUSP */
       9 #include <termios.h>
      10 #if defined(__sun) || defined(__sgi) || defined(R__PPCLINUX) || \
      11     defined(R__ALPHALINUX) || defined(R__MIPSLINUX)
      12 #undef TIOCGETP         /* Solaris and SGI define TIOCGETP in <termios.h> */
      13 #undef TIOCSETP
      14 #endif
      15 
    

    the second POSIX branch will be chosen (termios.h is included). If not, add detection code as for for example R__MIPSLINUX and include that define in the BSD excluded list above.

Non-Linux platforms may need more work. The basic thing is to assume that the OS is like Linux, except of course, if there's a closer alternative, like BSD or Cygwin.

1.3. Breaking news (17/05/2007): ROOT accepted for experimental

See end of bug [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325306 325306].

You will be able to use your favorite "experimental" mirror to download and install the packages. Just put

deb ftp://ftp.NN.debian.org/debian/ ../project/experimental main contrib

where NN is your mirror country code, into your /etc/apt/sources.list or /etc/apt/sources.list.d/experimental.list.

Note: the name of the metapackage and source package, at the request of FTP masters, has been changed to root-system. If you only want a minimal ROOT environment you may instead try installing root-system-bin.

1.4. Future plans

  • The intent is to upload ROOT "development" versions 5.odd.xx only to "experimental", and ROOT "production" versions 5.even.00 to "unstable", allowing the production versions to propagate into testing and stable over time.

  • Unfortunately the next production release of ROOT, 5.16.00, is not expected until post-Etch, but we intend to upload ROOT 5.16 to [http://backports.org backports.org] for Etch users once it is in unstable.

  • Next production release of ROOT (5.16.00) is planed for June 27, 2007. We will make packages of that, and upload to "unstable".

1.5. History

  • [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325306 ITP] submitted by ChristianHolm.

    • Packages uploaded to [http://ftp-master.debian.org/new.html NEW] queue on April 27, 2006, by KevinMcCarty and ChristianHolm. These were targeted for "experimental".

    • FTPmaster rejected these packages on the grounds of licensing issues. In the mean time, these issues have been worked out with the upstream authors and 3rd party developers.
    • Since then, the debian/copyright file has been greatly expanded, and the copyright holders of the non-free material were contacted and agreed to relicense it under LGPL. New ROOT packages targeted at "experimental" were uploaded to the NEW queue on November 3, 2006.
    • These packages were unfortunately rejected due to "too generic name". We (KevinMcCarty and ChristianHolm) have asked the FTP masters for input on names that would be acceptable, but so far we have had no response.

    • To use the experimental archive, add the following to your "/etc/apt/sources.list", where "NN" is your favorite mirror (say, us, no, fi, jp, or dk), and run "apt-get update":

        deb ftp://ftp.NN.debian.org/debian/ ../project/experimental main

1.6. The current unofficial repository

1.7. Technical issues for packaging

The approach is that the ROOT source tree contains [http://root.cern.ch/viewcvs/build/package/lib/ scripts] and [http://root.cern.ch/viewcvs/build/package/common templates] to deal with packaging in general (that is for Debian and RPM), as well as some [http://root.cern.ch/viewcvs/build/package/debian Debian] and [http://root.cern.ch/viewcvs/build/package/redhat RPM] specific templates.

The debian packaging directory is then build by running the script [http://root.cern.ch/viewcvs/build/package/lib/makedebdir.sh makedebdir.sh], followed by fakeroot debian/rules debian/control. The packaging scripts will try to build as many packages as possible on the build host. Note, that that sometimes means that you can get packages that wouldn't be possible on a pristine build system.

Note, that this scheme does not change the way the packages are built. It merely changes how the debian directory is prepared. After the debian directory is made, the developer can still tweak it to fit the system. Of course, such tweaks should eventually be propegated back to the packaging scripts in ROOT itself, to assure consistency.

In the eventual "official" Debian packages to come, the package maintainer would presumably run these two commands himself before dpkg-buildpackage, and the results of the commands (for instance the debian/ directory) would therefore enter into the diff.gz of the source package. Thus the source package uploaded to Debian would always be buildable with the normal steps of dpkg-buildpackage -rfakeroot.

If an end-user does apt-get source root and then re-runs the makedebdir script, it will overwrite the existing debian directory with information about the dependencies installed on the end-user's system. Hence an end-user may recompile Debian packages of ROOT building with support for unofficial (non-DFSG-free) libraries.

It is important that the maintainer ensure that he has all the needed "official" build-depends installed on his system when running the makedebdir.sh script, and none of the "unofficial" non-DFSG-free libraries (e.g. Pythia) installed, perhaps by building on a pristine machine or in a pristine chroot. That is, use pbuilder :-). In any case, official packages are not allowed to munge debian/control in such a way that their Build-Depends change during the dpkg-buildpackage step!

1.8. Licensing

1.9. Thanks