From 473e50fc158ff0847b193107f16c9d464828b534 Mon Sep 17 00:00:00 2001 From: rillig Date: Thu, 8 Feb 2007 23:27:40 +0000 Subject: regen --- doc/pkgsrc.html | 106 ++++++++++++++++++++------------------------------------ doc/pkgsrc.txt | 71 +++++++++++-------------------------- 2 files changed, 59 insertions(+), 118 deletions(-) (limited to 'doc') diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index f7c73a798de..9ec43634222 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -901,7 +901,7 @@ and dashes.

quarterly basis from the current branch and only gets modified for security updates. The names of the stable branches are built from the year and the quarter, for example - 2006Q3.

+ 2006Q4.

The second step is to decide how you want to download pkgsrc. You can get it as a tar file, via SUP, or via CVS. All three ways are described here.

@@ -915,8 +915,8 @@ and dashes.

The tar file for the current branch is in the directory current and is called pkgsrc.tar.gz. It is autogenerated daily.

-

The tar file for the stable branch 2006Q3 is in the - directory pkgsrc-2006Q3 and is also called pkgsrc-2006Q3.tar.gz.

+

The tar file for the stable branch 2006Q4 is in the + directory pkgsrc-2006Q4 and is also called pkgsrc-2006Q4.tar.gz.

After downloading the tar file, change to the directory where you want to have pkgsrc. This is usually /usr. Then, run gzcat @@ -963,7 +963,7 @@ and dashes.

/usr. In that directory you run the checkout command, which is cvs -q checkout -P pkgsrc for the current branch and cvs -q - checkout -rpkgsrc-2006Q3 -P pkgsrc for the stable + checkout -rpkgsrc-2006Q4 -P pkgsrc for the stable branch. This command will create a directory called pkgsrc with all the pkgsrc files in it.

@@ -1016,7 +1016,7 @@ and dashes.

by adding the option “-A” after the “update” keyword. To switch from the current branch back to the stable branch, add the - “-rpkgsrc-2006Q3” option.

+ “-rpkgsrc-2006Q4” option.

@@ -1749,67 +1749,37 @@ file and inspect the contents before extracting it.

  • SPROlang - Sun WorkShop Compilers common components

    • -

    You should set CC, CXX and - optionally, CPP in /etc/mk.conf, - e.g.:

    +

    You should set the following variables in your + mk.conf file:

    -	  CC=     cc
-	  CXX=    CC
-	  CPP=    /usr/ccs/lib/cpp
-
    + CC= cc + CXX= CC + CPP= cc -E + CXXCPP= CC -E + +
    +

    Note

    +

    The CPP setting might break some + packages that use the C preprocessor for processing things other + than C source code.

    +

    3.3.7.3. Building 64-bit binaries with SunPro

    -

    Building 64-bit binaries is a little trickier. First, you - need to bootstrap pkgsrc in 64-bit mode. One problem here is - that while building one of the programs in the bootstrap kit - (bmake), the CFLAGS - variable is not honored, even if it is set in the environment. - To work around this bug, you can create a simple shell script - called cc64 and put it somewhere in the - PATH:

    -
    -	  #! /bin/sh
-	  exec /opt/SUNWspro/bin/cc -xtarget=ultra -xarch=v9 ${1+"$@"}
-
    -

    Then, pass the definition for CC in the - environment of the bootstrap command:

    -
    -	  $ cd bootstrap
-	  $ CC=cc64 ./bootstrap
-
    -

    After bootstrapping, there are two alternative ways, - depending on whether you want to find bugs in packages or get - your system ready quickly. If you just want a running system, - add the following lines to your mk.conf +

    To build 64-bit packages, you just need to have the + following lines in your mk.conf file:

    -	  CC=                     cc64
-	  CXX=                    CC64
-	  PKGSRC_COMPILER=        sunpro
-
    -

    This way, all calls to the compiler will be intercepted by - the above wrapper and therefore get the necessary ABI options - automatically. (Don't forget to create the shell script - CC64, too.)

    -

    To find packages that ignore the user-specified - CFLAGS and CXXFLAGS, add - the following lines to your mk.conf - file:

    -
    -	  CC=                     cc
-	  CXX=                    CC
-	  PKGSRC_COMPILER=        sunpro
-	  CFLAGS=                 -xtarget=ultra -xarch=v9
-	  CXXFLAGS=               -xtarget=ultra -xarch=v9
-	  LDFLAGS=                -xtarget=ultra -xarch=v9
-
    -

    Packages that don't use the flags provided in the - configuration file will try to build 32-bit binaries and fail - during linking. Detecting this is useful to prevent bugs on - other platforms where the error would not show up but pass - silently.

    + PKGSRC_COMPILER= sunpro + ABI= 64 + +
    +

    Note

    +

    This setting has been tested for the SPARC + architecture. Intel and AMD machines need some more + work.

    +

    @@ -9336,7 +9306,7 @@ do? -21.1. +21.1.

    What is the difference between MAKEFLAGS, .MAKEFLAGS and @@ -9352,7 +9322,7 @@ do? -21.2. +21.2.

    What is the difference between MAKE, GMAKE and @@ -9370,7 +9340,7 @@ do? -21.3. +21.3.

    What is the difference between CC, PKG_CC and @@ -9388,7 +9358,7 @@ do? -21.4. +21.4.

    What is the difference between BUILDLINK_LDFLAGS, @@ -9401,7 +9371,7 @@ do? -21.5. +21.5.

    Why does make show-var VARNAME=BUILDLINK_PREFIX.foo @@ -9417,7 +9387,7 @@ do? -21.6. +21.6.

    What does ${MASTER_SITE_SOURCEFORGE:=package/} mean? I @@ -9441,7 +9411,7 @@ do? -21.7. +21.7.

    Which mailing lists are there for package developers?

    @@ -9466,7 +9436,7 @@ do? -21.8. +21.8.

    Where is the pkgsrc documentation?

    @@ -9514,7 +9484,7 @@ do? -21.9. +21.9.

    I have a little time to kill. What shall I do?

    diff --git a/doc/pkgsrc.txt b/doc/pkgsrc.txt index ea0625db5e5..c364f6521c7 100644 --- a/doc/pkgsrc.txt +++ b/doc/pkgsrc.txt @@ -804,7 +804,7 @@ Before you download any pkgsrc files, you should decide whether you want the current branch or the stable branch. The latter is forked on a quarterly basis from the current branch and only gets modified for security updates. The names of the stable branches are built from the year and the quarter, for example -2006Q3. +2006Q4. The second step is to decide how you want to download pkgsrc. You can get it as a tar file, via SUP, or via CVS. All three ways are described here. @@ -818,8 +818,8 @@ described in detail in Appendix C, Directory layout of the pkgsrc FTP server. The tar file for the current branch is in the directory current and is called pkgsrc.tar.gz. It is autogenerated daily. -The tar file for the stable branch 2006Q3 is in the directory pkgsrc-2006Q3 and -is also called pkgsrc-2006Q3.tar.gz. +The tar file for the stable branch 2006Q4 is in the directory pkgsrc-2006Q4 and +is also called pkgsrc-2006Q4.tar.gz. After downloading the tar file, change to the directory where you want to have pkgsrc. This is usually /usr. Then, run gzcat pkgsrc.tar.gz | tar xf - to @@ -853,7 +853,7 @@ Or, the same for the bourne shell: Then, you change to the directory where you want to have your copy of pkgsrc. In most cases this is /usr. In that directory you run the checkout command, which is cvs -q checkout -P pkgsrc for the current branch and cvs -q checkout --rpkgsrc-2006Q3 -P pkgsrc for the stable branch. This command will create a +-rpkgsrc-2006Q4 -P pkgsrc for the stable branch. This command will create a directory called pkgsrc with all the pkgsrc files in it. 2.2. Keeping pkgsrc up-to-date @@ -894,7 +894,7 @@ When updating pkgsrc, the CVS program keeps track of the branch you selected. But if you, for whatever reason, want to switch from the stable branch to the current one, you can do it by adding the option "-A" after the "update" keyword. To switch from the current branch back to the stable branch, add the -"-rpkgsrc-2006Q3" option. +"-rpkgsrc-2006Q4" option. 2.2.2.2. What happens to my changes when updating? @@ -1474,59 +1474,30 @@ You will need at least the following packages installed (from WorkShop 5.0) * SPROlang - Sun WorkShop Compilers common components -You should set CC, CXX and optionally, CPP in /etc/mk.conf, e.g.: +You should set the following variables in your mk.conf file: - CC= cc - CXX= CC - CPP= /usr/ccs/lib/cpp + CC= cc + CXX= CC + CPP= cc -E + CXXCPP= CC -E +Note -3.3.7.3. Building 64-bit binaries with SunPro - -Building 64-bit binaries is a little trickier. First, you need to bootstrap -pkgsrc in 64-bit mode. One problem here is that while building one of the -programs in the bootstrap kit (bmake), the CFLAGS variable is not honored, even -if it is set in the environment. To work around this bug, you can create a -simple shell script called cc64 and put it somewhere in the PATH: - - #! /bin/sh - exec /opt/SUNWspro/bin/cc -xtarget=ultra -xarch=v9 ${1+"$@"} - - -Then, pass the definition for CC in the environment of the bootstrap command: - - $ cd bootstrap - $ CC=cc64 ./bootstrap - - -After bootstrapping, there are two alternative ways, depending on whether you -want to find bugs in packages or get your system ready quickly. If you just -want a running system, add the following lines to your mk.conf file: - - CC= cc64 - CXX= CC64 - PKGSRC_COMPILER= sunpro - +The CPP setting might break some packages that use the C preprocessor for +processing things other than C source code. -This way, all calls to the compiler will be intercepted by the above wrapper -and therefore get the necessary ABI options automatically. (Don't forget to -create the shell script CC64, too.) +3.3.7.3. Building 64-bit binaries with SunPro -To find packages that ignore the user-specified CFLAGS and CXXFLAGS, add the -following lines to your mk.conf file: +To build 64-bit packages, you just need to have the following lines in your +mk.conf file: - CC= cc - CXX= CC - PKGSRC_COMPILER= sunpro - CFLAGS= -xtarget=ultra -xarch=v9 - CXXFLAGS= -xtarget=ultra -xarch=v9 - LDFLAGS= -xtarget=ultra -xarch=v9 + PKGSRC_COMPILER= sunpro + ABI= 64 +Note -Packages that don't use the flags provided in the configuration file will try -to build 32-bit binaries and fail during linking. Detecting this is useful to -prevent bugs on other platforms where the error would not show up but pass -silently. +This setting has been tested for the SPARC architecture. Intel and AMD machines +need some more work. 3.3.7.4. Common problems -- cgit v1.2.3