--- /dev/null
+.\" Hey Emacs! This file is -*- nroff -*- source.
+.\" Original manpage cvs revision 1.4
+.\" Translated by KURASAWA Nozomu <nabetaro@debian.or.jp>
+.\" Last modified: Sun Nov 30 21:48:11 JST 2003
+.\"WORD: architecture ¥¢¡¼¥¥Æ¥¯¥Á¥ã
+.\"WORD: facility µ¡¹½
+.rn '' }`
+''' $RCSfile$$Revision$$Date$
+'''
+''' $Log$
+''' Revision 1.1.2.1 2004-03-11 11:23:46 keybuk
+''' Add two new japanese manual pages.
+'''
+''' Revision 1.2.2.1 2003/12/02 05:25:41 nabetaro
+''' update for dpkg_1.10.18
+'''
+''' Revision 1.4 1999/09/27 01:37:25 wakkerma
+''' Updated to dpkg 1.4.1.11
+'''
+'''
+.de Sh
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp
+.if t .sp .5v
+.if n .sp
+..
+.de Ip
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.de Vb
+.ft CW
+.nf
+.ne \\$1
+..
+.de Ve
+.ft R
+
+.fi
+..
+'''
+'''
+''' Set up \*(-- to give an unbreakable dash;
+''' string Tr holds user defined translation string.
+''' Bell System Logo is used as a dummy character.
+'''
+.tr \(*W-|\(bv\*(Tr
+.ie n \{\
+.ds -- \(*W-
+.ds PI pi
+.if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
+.if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
+.ds L" ""
+.ds R" ""
+''' \*(M", \*(S", \*(N" and \*(T" are the equivalent of
+''' \*(L" and \*(R", except that they are used on ".xx" lines,
+''' such as .IP and .SH, which do another additional levels of
+''' double-quote interpretation
+.ds M" """
+.ds S" """
+.ds N" """""
+.ds T" """""
+.ds L' '
+.ds R' '
+.ds M' '
+.ds S' '
+.ds N' '
+.ds T' '
+'br\}
+.el\{\
+.ds -- \(em\|
+.tr \*(Tr
+.ds L" ``
+.ds R" ''
+.ds M" ``
+.ds S" ''
+.ds N" ``
+.ds T" ''
+.ds L' `
+.ds R' '
+.ds M' `
+.ds S' '
+.ds N' `
+.ds T' '
+.ds PI \(*p
+'br\}
+.\" If the F register is turned on, we'll generate
+.\" index entries out stderr for the following things:
+.\" TH Title
+.\" SH Header
+.\" Sh Subsection
+.\" Ip Item
+.\" X<> Xref (embedded
+.\" Of course, you have to process the output yourself
+.\" in some meaninful fashion.
+.if \nF \{
+.de IX
+.tm Index:\\$1\t\\n%\t"\\$2"
+..
+.nr % 0
+.rr F
+.\}
+.TH DPKG-ARCHITECTURE 1 "perl 5.004, patch 04" "24/Jul/99" "User Contributed Perl Documentation"
+.UC
+.if n .hy 0
+.if n .na
+.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
+.de CQ \" put $1 in typewriter font
+.ft CW
+'if n "\c
+'if t \\&\\$1\c
+'if n \\&\\$1\c
+'if n \&"
+\\&\\$2 \\$3 \\$4 \\$5 \\$6 \\$7
+'.ft R
+..
+.\" @(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2
+. \" AM - accent mark definitions
+.bd B 3
+. \" fudge factors for nroff and troff
+.if n \{\
+. ds #H 0
+. ds #V .8m
+. ds #F .3m
+. ds #[ \f1
+. ds #] \fP
+.\}
+.if t \{\
+. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
+. ds #V .6m
+. ds #F 0
+. ds #[ \&
+. ds #] \&
+.\}
+. \" simple accents for nroff and troff
+.if n \{\
+. ds ' \&
+. ds ` \&
+. ds ^ \&
+. ds , \&
+. ds ~ ~
+. ds ? ?
+. ds ! !
+. ds /
+. ds q
+.\}
+.if t \{\
+. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
+. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
+. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
+. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
+. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
+. ds ? \s-2c\h'-\w'c'u*7/10'\u\h'\*(#H'\zi\d\s+2\h'\w'c'u*8/10'
+. ds ! \s-2\(or\s+2\h'-\w'\(or'u'\v'-.8m'.\v'.8m'
+. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
+. ds q o\h'-\w'o'u*8/10'\s-4\v'.4m'\z\(*i\v'-.4m'\s+4\h'\w'o'u*8/10'
+.\}
+. \" troff and (daisy-wheel) nroff accents
+.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
+.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
+.ds v \\k:\h'-(\\n(.wu*9/10-\*(#H)'\v'-\*(#V'\*(#[\s-4v\s0\v'\*(#V'\h'|\\n:u'\*(#]
+.ds _ \\k:\h'-(\\n(.wu*9/10-\*(#H+(\*(#F*2/3))'\v'-.4m'\z\(hy\v'.4m'\h'|\\n:u'
+.ds . \\k:\h'-(\\n(.wu*8/10)'\v'\*(#V*4/10'\z.\v'-\*(#V*4/10'\h'|\\n:u'
+.ds 3 \*(#[\v'.2m'\s-2\&3\s0\v'-.2m'\*(#]
+.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
+.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
+.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
+.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
+.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
+.ds ae a\h'-(\w'a'u*4/10)'e
+.ds Ae A\h'-(\w'A'u*4/10)'E
+.ds oe o\h'-(\w'o'u*4/10)'e
+.ds Oe O\h'-(\w'O'u*4/10)'E
+. \" corrections for vroff
+.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
+.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
+. \" for low resolution devices (crt and lpr)
+.if \n(.H>23 .if \n(.V>19 \
+\{\
+. ds : e
+. ds 8 ss
+. ds v \h'-1'\o'\(aa\(ga'
+. ds _ \h'-1'^
+. ds . \h'-1'.
+. ds 3 3
+. ds o a
+. ds d- d\h'-1'\(ga
+. ds D- D\h'-1'\(hy
+. ds th \o'bp'
+. ds Th \o'LP'
+. ds ae ae
+. ds Ae AE
+. ds oe oe
+. ds Oe OE
+.\}
+.rm #[ #] #H #V #F C
+.\" .SH "NAME"
+.SH "̾¾Î"
+.\" dpkg-architecture \- set and determine the architecture for package building
+dpkg-architecture \- ¥Ñ¥Ã¥±¡¼¥¸¹½ÃÛÍѤ˥¢¡¼¥¥Æ¥¯¥Á¥ã¤ò·èÄꡦÀßÄꤹ¤ë
+.\" .SH "SYNOPSIS"
+.SH "½ñ¼°"
+dpkg-architecture [options] [action]
+.PP
+.\" Valid options:
+͸ú¤Ê¥ª¥×¥·¥ç¥ó:
+\fB\-a\fRDebian-Architecture
+\fB\-t\fRGnu-System-Type
+\fB\-f\fR
+.PP
+.\" Valid actions:
+͸ú¤Ê¥¢¥¯¥·¥ç¥ó:
+\fB\-l\fR, \fB\-q\fRVariable-Name, \fB\-s\fR, \fB\-u\fR, \fB\-c\fR Command
+.\" .SH "DESCRIPTION"
+.SH "ÀâÌÀ"
+.\" dpkg-architecture does provide a facility to determine and set the build and
+.\" host architecture for package building.
+dpkg-architecture ¤Ï¥Ñ¥Ã¥±¡¼¥¸¹½ÃÛÍѤˡ¢
+¥Ó¥ë¥É¡¦¥Û¥¹¥È¥¢¡¼¥¥Æ¥¯¥Á¥ã¤ò·èÄꡦÀßÄꤹ¤ëµ¡¹½¤òÄ󶡤¹¤ë¡£
+.\" .SH "OVERVIEW"
+.SH "³µÍ×"
+.\" The build architecture is always determined by an external call to dpkg, and
+.\" can not be set at the command line.
+¥Ó¥ë¥É¥¢¡¼¥¥Æ¥¯¥Á¥ã¤Ï¡¢¾ï¤Ë dpkg ¤Ø¤Î³°Éô¸Æ¤Ó½Ð¤·¤Ë¤è¤Ã¤Æ·èÄꤵ¤ì¡¢
+¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ç¤ÏÀßÄê¤Ç¤¤Ê¤¤¡£
+.PP
+.\" You can specify the host architecture by providing one or both of the options \fB\-a\fR
+.\" and \fB\-t\fR. The default is determined by an external call to gcc, or the same as
+.\" the build architecture if CC or gcc are both not available. One out of \fB\-a\fR and \fB\-t\fR
+.\" is sufficient, the value of the other will be set to a usable default.
+.\" Indeed, it is often better to only specify one, because dpkg-architecture
+.\" will warn you if your choice doesn't match the default.
+\fB\-a\fR ¤« \fB\-t\fR ¤Þ¤¿¤ÏξÊý¤Î¥ª¥×¥·¥ç¥ó¤Ç¡¢
+¥Û¥¹¥È¥¢¡¼¥¥Æ¥¯¥Á¥ã¤ò»ØÄê¤Ç¤¤ë¡£
+¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢gcc ¤Ø¤Î³°Éô¸Æ¤Ó½Ð¤·¤Ç·èÄꤵ¤ì¤ë¤¬¡¢
+CC ¤È gcc ¤ÎξÊý¤¬ÍøÍѤǤ¤Ê¤¤¾ì¹ç¡¢¥Ó¥ë¥É¥¢¡¼¥¥Æ¥¯¥Á¥ã¤ÈƱ¤¸¤Ë¤Ê¤ë¡£
+\fB\-a\fR ¤È \fB\-t\fR ¤Î¤É¤Á¤é¤«¤Ç½½Ê¬¤À¤¬¡¢
+¾Êý¤ÎÃͤϻÈÍѲÄǽ¤Ê¥Ç¥Õ¥©¥ë¥È¤Ë¥»¥Ã¥È¤µ¤ì¤ë¡£
+¼ÂºÝ¤Ë¤Ï¡¢ÁªÂò¤·¤¿¤â¤Î¤¬¥Ç¥Õ¥©¥ë¥È¤È°ìÃפ·¤Ê¤¤¾ì¹ç¡¢
+dpkg-architecture ¤¬·Ù¹ð¤¹¤ë¤Î¤Ç¡¢¤¿¤¤¤Æ¤¤ 1 ¤Ä¤ò»ØÄꤹ¤ë¤À¤±¤Î¤Û¤¦¤¬¤è¤¤¡£
+.PP
+.\" The default action is \fB\-l\fR, which prints the environment variales, one each line,
+.\" in the format VARIABLE=value. If you are only interested in the value of a
+.\" single variable, you can use \fB\-q\fR. If you specify \fB\-s\fR, it will output an export
+.\" command. This can be used to set the environment variables using eval. \fB\-u\fR
+.\" does return a similar command to unset all variables. \fB\-c\fR does execute a
+.\" command in an environment which has all variables set to the determined
+.\" value.
+¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥·¥ç¥ó¤Ï \fB\-l\fR ¤Ç¡¢
+1¹Ô¤´¤È ÊÑ¿ô̾=ÃÍ ¤Î·Á¤Ç´Ä¶ÊÑ¿ô¤òɽ¼¨¤¹¤ë¡£
+.\" variales ¤Ï variables ¤Î typo?
+ñ°ì¤ÎÊÑ¿ô¤ÎÃͤòɽ¼¨¤·¤¿¤¤¤À¤±¤Ê¤é¡¢\fB\-q\fR ¤òÍøÍѤ·¤Æ¤â¤è¤¤¡£
+\fB\-s\fR ¤ò»ØÄꤷ¤¿¾ì¹ç¡¢export ¥³¥Þ¥ó¥É·Á¼°¤Ç½ÐÎϤ¹¤ë¡£
+¤³¤ì¤Ë eval ¤òÍѤ¤¤Æ¡¢´Ä¶ÊÑ¿ô¤ÎÀßÄê (set) ¤Ë»ÈÍѤǤ¤ë¡£
+\fB\-u\fR ¤Ï¡¢Á´ÊÑ¿ô¤ò²ò½ü (unset) ¤¹¤ë¥³¥Þ¥ó¥É¤òÊÖ¤¹¡£
+\fB\-c\fR ¤Ï¡¢·èÄꤷ¤¿ÃͤòÁ´ÊÑ¿ô¤ËÀßÄꤷ¤¿´Ä¶¤Ç¡¢¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¡£
+.PP
+.\" Existing environment variables with the same name as used by the scripts are
+.\" not overwritten, except if the \fB\-f\fR force flag is present. This allows the user
+.\" to override a value even when the call to dpkg-architecture is buried in
+.\" some other script (for example dpkg-buildpackage). The \fB\-q\fR query option
+.\" implies \fB\-f\fR, and is therefore not affected by existing environment settings.
+\fB\-f\fR ¶¯À©¥Õ¥é¥°¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¤ò½ü¤¡¢
+¥¹¥¯¥ê¥×¥È¤Ç»ÈÍѤµ¤ì¤ë¤Î¤ÈƱ̾¤Î´û¸¤Î´Ä¶ÊÑ¿ô¤Ï¡¢¾å½ñ¤¤µ¤ì¤Ê¤¤¡£
+¤³¤ì¤Ï dpkg-architecture ¤Ø¤Î¸Æ¤Ó½Ð¤·¤ò¡¢
+¾¤Î¥¹¥¯¥ê¥×¥È (Î㤨¤Ð dpkg-buildpackage) ¤ËËä¤á¹þ¤ó¤Ç¤â¡¢
+¥æ¡¼¥¶¤¬Ãͤò¾å½ñ¤¤Ç¤¤ë¤È¤¤¤¦¤³¤È¤Ç¤¢¤ë¡£
+\fB\-q\fR ¥¯¥¨¥ê¥ª¥×¥·¥ç¥ó¤Ë¤Ï¡¢\fB\-f\fR ¤ò°ÅÌۤ˻ØÄꤹ¤ë¡£
+¤½¤Î¤¿¤á¡¢´û¸¤Î´Ä¶ÀßÄê¤Ë¤è¤Ã¤Æ±Æ¶Á¤µ¤ì¤Ê¤¤¡£
+.\" .SH "TERMS"
+.SH "ÍѸì"
+.\" .Ip "build machine" 4
+.Ip "¥Ó¥ë¥É¥Þ¥·¥ó (build machine)" 4
+.\" The machine the package is build on.
+¥Ñ¥Ã¥±¡¼¥¸¤Î¹½ÃÛ¤ò¹Ô¤¦¥Þ¥·¥ó¡£
+.\" .Ip "host machine" 4
+.Ip "¥Û¥¹¥È¥Þ¥·¥ó (host machine)" 4
+.\" The machine the package is build for.
+¹½ÃÛ¤·¤¿¥Ñ¥Ã¥±¡¼¥¸¤ò»ÈÍѤ¹¤ë¥Þ¥·¥ó¡£
+.Ip "Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã (Debian Architecture)" 4
+.\" The Debian archietcture string, which specifies the binary tree in the \s-1FTP\s0
+.\" archive. Examples: i386, sparc, hurd-i386.
+\s-1FTP\s0 ¥¢¡¼¥«¥¤¥Ö¤Î¥Ð¥¤¥Ê¥ê¥Ä¥ê¡¼¤Ç»ØÄꤹ¤ë Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ãʸ»úÎó¡£
+Îã: i386, sparc, hurd-i386.
+.Ip "\s-1GNU\s0 ¥·¥¹¥Æ¥à¥¿¥¤¥× (\s-1GNU\s0 System Type)" 4
+.\" An architecture specification string consisting of two or three parts,
+.\" cpu-system or cpu-vendor-system. Examples: i386-linux, sparc-linux, i386-gnu.
+cpu-system ¤ä cpu-vendor-system ¤È¤¤¤Ã¤¿¡¢
+2, 3 ¥Ñ¡¼¥È¤«¤éÀ®¤ë¥¢¡¼¥¥Æ¥¯¥Á¥ã»ÅÍÍʸ»úÎó¡£
+Îã: i386-linux, sparc-linux, i386-gnu.
+.\" .SH "EXAMPLES"
+.SH "Îã"
+.\" dpkg-buildpackage accepts the \fB\-a\fR option and passes it to dpkg-architecture.
+.\" Other examples:
+dpkg-buildpackage ¤Ï \fB\-a\fR ¥ª¥×¥·¥ç¥ó¤ò¼õ¤±ÉÕ¤±¡¢
+¤½¤Î¤Þ¤Þ dpkg-architecture ¤ËÅϤ¹¡£
+¤½¤Î¾¤ÎÍÑÎã:
+.PP
+CC=i386-gnu-gcc dpkg-architecture \f(CW-c\fR debian/rules build
+.PP
+eval `dpkg-architecture \f(CW-u\fR`
+.\" .SH "VARIABLES"
+.SH "ÊÑ¿ô"
+.\" The following variables are set by dpkg-architecture:
+dpkg-architecture ¤Ï°Ê²¼¤ÎÊÑ¿ô¤òÀßÄꤹ¤ë:
+.Ip "\s-1DEB_BUILD_ARCH\s0" 4
+.\" The Debian architecture of the build machine.
+¥Ó¥ë¥É¥Þ¥·¥ó¤Î Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã
+.Ip "\s-1DEB_BUILD_GNU_TYPE\s0" 4
+.\" The \s-1GNU\s0 system type of the build machine.
+¥Ó¥ë¥É¥Þ¥·¥ó¤Î \s-1GNU\s0 ¥·¥¹¥Æ¥à¥¿¥¤¥×
+.Ip "\s-1DEB_BUILD_GNU_CPU\s0" 4
+.\" The \s-1CPU\s0 part of \s-1DEB_BUILD_GNU_TYPE\s0
+\s-1DEB_BUILD_GNU_TYPE\s0 ¤Î \s-1CPU\s0 Éô
+.Ip "\s-1DEB_BUILD_GNU_SYSTEM\s0" 4
+.\" The System part of \s-1DEB_BUILD_GNU_TYPE\s0
+\s-1DEB_BUILD_GNU_TYPE\s0 ¤Î¥·¥¹¥Æ¥àÉô
+.Ip "\s-1DEB_HOST_ARCH\s0" 4
+.\" The Debian architecture of the host machine.
+¥Û¥¹¥È¥Þ¥·¥ó¤Î Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã
+.Ip "\s-1DEB_HOST_GNU_TYPE\s0" 4
+.\" The \s-1GNU\s0 system type of the host machine.
+¥Û¥¹¥È¥Þ¥·¥ó¤Î \s-1GNU\s0 ¥·¥¹¥Æ¥à¥¿¥¤¥×
+.Ip "\s-1DEB_HOST_GNU_CPU\s0" 4
+.\" The \s-1CPU\s0 part of \s-1DEB_HOST_GNU_TYPE\s0
+\s-1DEB_HOST_GNU_TYPE\s0 ¤Î \s-1CPU\s0 Éô
+.Ip "\s-1DEB_HOST_GNU_SYSTEM\s0" 4
+.\" The System part of \s-1DEB_HOST_GNU_TYPE\s0
+\s-1DEB_HOST_GNU_TYPE\s0 ¤Î¥·¥¹¥Æ¥àÉô
+.SH "DEBIAN/RULES"
+.\" The environment variables set by dpkg-architecture are passed to
+.\" debian/rules as make variables (see make documentation). You can and should
+.\" use them in the build process as needed. Here are some examples, which also
+.\" show how you can improve the cross compilation support in your package:
+dpkg-architecture ¤ÇÀßÄꤷ¤¿´Ä¶ÊÑ¿ô¤Ï¡¢
+debian/rules ¤Ë make ÊÑ¿ô (make ʸ½ñ¤ò»²¾È) ¤È¤·¤ÆÅϤµ¤ì¤ë¡£
+ɬÍפǤ¢¤ì¤Ð¡¢¹½ÃÛ¥×¥í¥»¥¹¤Ç¤³¤ÎÊÑ¿ô¤ò»ÈÍѤǤ¤ë¤·¡¢»ÈÍѤ¹¤ë¤Ù¤¤Ç¤¢¤ë¡£
+°Ê²¼¡¢¥Ñ¥Ã¥±¡¼¥¸¤Ç¤Î¥¯¥í¥¹¥³¥ó¥Ñ¥¤¥ë¥µ¥Ý¡¼¥È¤Î²þÎÉÊýË¡¤â¼¨¤¹¡¢»ÈÍÑÎã¤Ç¤¢¤ë:
+.\" .PP
+.\" Instead:
+.\" .PP
+.\" ARCH=`dpkg --print-architecture`
+.\" configure $(ARCH)\-linux
+.\" .PP
+.\" please use the following:
+.\" .PP
+.\" B_ARCH=$(DEB_BUILD_GNU_TYPE)
+.\" H_ARCH=$(DEB_HOST_GNU_TYPE)
+.\" configure --build=$(B_ARCH) --host=$(H_ARCH)
+.\" .PP
+.\" Instead:
+.\" .PP
+.\" ARCH=`dpkg --print-architecture`
+.\" ifeq ($(ARCH),alpha)
+.\" ...
+.\" endif
+.\" .PP
+.\" please use:
+.\" .PP
+.\" ARCH=$(DEB_HOST_ARCH)
+.\" ifeq ($(ARCH),alpha)
+.\" ...
+.\" endif
+.PP
+ARCH=`dpkg --print-architecture`
+configure $(ARCH)\-linux
+.PP
+¾åµ¤ËÂ夨¤Æ
+.PP
+B_ARCH=$(DEB_BUILD_GNU_TYPE)
+H_ARCH=$(DEB_HOST_GNU_TYPE)
+configure --build=$(B_ARCH) --host=$(H_ARCH)
+.PP
+¤È¤¹¤ë¡£
+.PP
+ARCH=`dpkg --print-architecture`
+ifeq ($(ARCH),alpha)
+ ...
+endif
+.PP
+¤³¤ÎÂå¤ï¤ê¤Ë
+.PP
+ARCH=$(DEB_HOST_ARCH)
+ifeq ($(ARCH),alpha)
+ ...
+endif
+.PP
+¤È¤¹¤ë¡£
+.PP
+.\" In general, calling dpkg in the rules file to get architecture information
+.\" is deprecated (until you want to provide backward compatibility, see below).
+.\" Especially the --print-architecture option is unreliable since we have
+.\" Debian architectures which don't equal a processor name.
+°ìÈÌŪ¤Ë¡¢¥¢¡¼¥¥Æ¥¯¥Á¥ã¾ðÊó¤ò¼èÆÀ¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
+rules ¥Õ¥¡¥¤¥ë¤Ç dpkg ¤ò¸Æ¤Ö¤Ù¤¤Ç¤Ï¤Ê¤¤(¸å½Ò¤Î¸åÊý¸ß´¹À¤òÄ󶡤¹¤ë¤Þ¤Ç)¡£
+ÆÃ¤Ë --print-architecture ¥ª¥×¥·¥ç¥ó¤Ï¡¢
+¥×¥í¥»¥Ã¥µÌ¾¤ÈÅù¤·¤¯¤Ê¤¤ Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã¤¬¤Ç¤¤Æ°ÊÍè¡¢Åö¤Æ¤Ë¤Ç¤¤Ê¤¤¡£
+.\" .SH "BACKWARD COMPATIBILITY"
+.SH "¸åÊý¸ß´¹À"
+.\" When providing a new facility, it is always a good idea to stay compatible with old
+.\" versions of the programs. Note that dpkg-architecture does not affect old
+.\" debian/rules files, so the only thing to consider is using old building
+.\" scripts with new debian/rules files. The following does the job:
+¿·µ¡¹½¤òÄ󶡤¹¤ë¤È¤¤Ë¡¢¥×¥í¥°¥é¥à¤Îµì¥Ð¡¼¥¸¥ç¥ó¤È¤Î¸ß´¹À¤ò³ÎÊݤ¹¤ë¤Î¤Ï¡¢
+¾ï¤Ë¤è¤¤¹Í¤¨¤Ç¤¢¤ë¡£
+dpkg-architecture ¤Ï¸Å¤¤ debian/rules ¥Õ¥¡¥¤¥ë¤Ë¤Ï±Æ¶Á¤òµÚ¤Ü¤µ¤Ê¤¤¡£
+¤½¤Î¤¿¤á¡¢¿·¤·¤¤ debian/rules ¥Õ¥¡¥¤¥ë¤Ç¡¢
+¸Å¤¤¹½ÃÛ¥¹¥¯¥ê¥×¥È¤ò»ÈÍѤ¹¤ë»ö¤ò¹Íθ¤¹¤ë¤À¤±¤Ç¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤Û¤·¤¤¡£
+°Ê²¼¤Ï¤½¤ÎÊýË¡¤Ç¤¢¤ë:
+.PP
+DEB_BUILD_ARCH := $(shell dpkg --print-installation-architecture)
+DEB_BUILD_GNU_CPU := $(patsubst hurd-%,%,$(DEB_BUILD_ARCH))
+ifeq ($(filter-out hurd-%,$(DEB_BUILD_ARCH)),)
+ DEB_BUILD_GNU_SYSTEM := gnu
+else
+ DEB_BUILD_GNU_SYSTEM := linux
+endif
+DEB_BUILD_GNU_TYPE=$(DEB_BUILD_GNU_CPU)\-$(DEB_BUILD_GNU_SYSTEM)
+.PP
+DEB_HOST_ARCH=$(DEB_BUILD_ARCH)
+DEB_HOST_GNU_CPU=$(DEB_BUILD_GNU_CPU)
+DEB_HOST_GNU_SYSTEM=$(DEB_BUILD_GNU_SYSTEM)
+DEB_HOST_GNU_TYPE=$(DEB_BUILD_GNU_TYPE)
+.PP
+.\" Put a subset of these lines at the top of your debian/rules file; these
+.\" default values will be overwritten if dpkg-architecture is used.
+debian/rules ¥Õ¥¡¥¤¥ë¤Î°ìÈÖ¾å¤Ë¤Î¾åµ¤Î¹Ô¤Î¥µ¥Ö¥»¥Ã¥È¤òÃÖ¤¯¤³¤È¡£
+dpkg-architecture ¤ò»ÈÍѤ¹¤ë¾ì¹ç¤Ï¡¢¤³¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤ¬¾å½ñ¤¤µ¤ì¤ë¡£
+.PP
+.\" You don't need the full set. Choose a consistent set which contains the
+.\" values you use in the rules file. For example, if you only need the host
+.\" Debian architecture, `DEB_HOST_ARCH=`dpkg --print-installation-architecture`
+.\" is sufficient (this is indeed the Debian architecture of the build machine,
+.\" but remember that we are only trying to be backward compatible with native
+.\" compilation).
+¥Õ¥ë¥»¥Ã¥È¤ÏɬÍפʤ¤¡£
+rules ¥Õ¥¡¥¤¥ë¤Ç»ÈÍѤ¹¤ëÃͤò´Þ¤à¡¢Ì·½â¤·¤Ê¤¤¥»¥Ã¥È¤òÁª¤Ö¤³¤È¡£
+Î㤨¤Ð¡¢¥Û¥¹¥È Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã¤Î¤ßɬÍפȤ¹¤ë¾ì¹ç¡¢
+ `DEB_HOST_ARCH=`dpkg --print-installation-architecture` ¤Ç½½Ê¬¤Ç¤¢¤ë¡£
+(¤³¤ì¤Ï³Î¤«¤Ë¥Ó¥ë¥É¥Þ¥·¥ó¤Î Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã¤Ç¤¢¤ë¡£
+¤·¤«¤·¡¢¥Í¥¤¥Æ¥£¥Ö¥³¥ó¥Ñ¥¤¥ë¤È¤Î¸åÊý¸ß´¹À¤ò»ý¤È¤¦¤È¤·¤Æ¤¤¤ë¤À¤±¤Ç¤¢¤ë¤³¤È¤ò
+»×¤¤½Ð¤¹¤³¤È)
+.PP
+.\" You may not want to care about old build packages (for example, if you have
+.\" sufficient source dependencies declared anyway). But you should at least
+.\" support the traditional way to build packages by calling `debian/rules
+.\" build\*(R' directly, without setting environment variables. To do this, use the
+.\" \fB\-q\fR option to query suitable default values:
+(Î㤨¤Ð¡¢½½Ê¬¤Ê¥½¡¼¥¹°Í¸´Ø·¸¤ò¤È¤Ë¤«¤¯Àë¸À¤¹¤ë¾ì¹ç¤Ê¤É)
+µì¼°¤Î¹½Ãۥѥ屡¼¥¸¤Ë¤Ï´Ø¿´¤¬¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤¡£
+¤·¤«¤·¡¢¾¯¤Ê¤¯¤È¤â´Ä¶ÊÑ¿ô¤òÀßÄꤻ¤º¡¢`debian/rules build\*(R' ¤òľÀܸƤó¤Ç
+¥Ñ¥Ã¥±¡¼¥¸¤ò¹½ÃÛ¤¹¤ë¤È¤¤¤¦¡¢½¾Íè¤ÎÊýË¡¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤Ù¤¤À¡£
+¤½¤Î¤¿¤á¤Ë¤Ï¡¢Å¬Àڤʥǥե©¥ë¥ÈÃͤò¼èÆÀ¤¹¤ë \fB\-q\fR ¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤³¤È¡£
+.PP
+DEB_BUILD_ARCH=`dpkg-architecture \-qDEB_BUILD_ARCH`
+DEB_BUILD_GNU=`dpkg-architecture \-qDEB_BUILD_GNU`
+.PP
+.\" etc. You get the idea. This way, you can ensure that the variables are never
+.\" undeclared. Note that this breaks backwards compatibility with old build
+.\" scripts, and you should only do that if source dependencies are implemented
+.\" and declared accordingly.
+¾åµÅù¤ÎÍÑË¡¤¬¹Í¤¨¤é¤ì¤ë¡£
+¤³¤Î¤è¤¦¤Ë¡¢ÊÑ¿ô¤¬Ì¤Àë¸À¤Ç¤Ê¤¤¤³¤È¤òÊݾڤǤ¤ë¡£
+¤³¤ì¤¬µì¼°¤Î¹½ÃÛ¥¹¥¯¥ê¥×¥È¤È¤Î¸åÊý¸ß´¹À¤ò²õ¤·¡¢
+¤½¤Î¤¿¤á¤Ë¥½¡¼¥¹°Í¸´Ø·¸¤¬¼ÂÁõ¡¦Àë¸À¤µ¤ì¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
+¤¢¤¨¤Æ¤½¤¦¤¹¤ë¤Ù¤¤Ç¤¢¤ë¡£
+.\" .SH "SEE ALSO"
+.SH "´ØÏ¢¹àÌÜ"
+dpkg-buildpackage
+dpkg-cross
+.\" .SH "CONTACT"
+.SH "Ï¢Íí"
+.\" If you have questions about the usage of the make variables in your rules
+.\" files, or about cross compilation support in your packages, please email me.
+.\" The addresse is Marcus Brinkmann <brinkmd@debian.org>.
+rules ¥Õ¥¡¥¤¥ë¤Ç¤Î make ÊÑ¿ô¤Î»È¤¤Êý¤ä¡¢
+¥Ñ¥Ã¥±¡¼¥¸¤Î¥¯¥í¥¹¥³¥ó¥Ñ¥¤¥ë¥µ¥Ý¡¼¥È¤Ë¤Ä¤¤¤Æ¤Îµ¿Ìä¤Ï¡¢
+Marcus Brinkmann <brinkmd@debian.org> ¤Þ¤Ç email ¤òÁ÷¤Ã¤Æ¤Û¤·¤¤¡£
+.SH "ËÝÌõ¼Ô"
+ÁÒß· ˾ <nabetaro@debian.or.jp>
+.rn }` ''
+.IX Title "DPKG-ARCHITECTURE 1"
+.\" .IX Name "dpkg-architecture - set and determine the architecture for package building"
+.IX Name "dpkg-architecture - ¥Ñ¥Ã¥±¡¼¥¸¹½ÃÛÍѤ˥¢¡¼¥¥Æ¥¯¥Á¥ã¤ò·èÄꡦÀßÄꤹ¤ë"
+
+.\" .IX Header "NAME"
+.IX Header "̾¾Î"
+
+.\" .IX Header "SYNOPSIS"
+.IX Header "½ñ¼°"
+
+.\" .IX Header "DESCRIPTION"
+.IX Header "ÀâÌÀ"
+
+.\" .IX Header "OVERVIEW"
+.IX Header "³µÍ×"
+
+.\" .IX Header "TERMS"
+.IX Header "ÍѸì"
+
+.\" .IX Item "build machine"
+.IX Item "¥Ó¥ë¥É¥Þ¥·¥ó (build machine)"
+
+.\" .IX Item "host machine"
+.IX Item "¥Û¥¹¥È¥Þ¥·¥ó (host machine)"
+
+.\" .IX Item "Debian Architecture"
+.IX Item "Debian ¥¢¡¼¥¥Æ¥¯¥Á¥ã (Debian Architecture)"
+
+.\" .IX Item "\s-1GNU\s0 System Type"
+.IX Item "\s-1GNU\s0 ¥·¥¹¥Æ¥à¥¿¥¤¥× (\s-1GNU\s0 System Type)"
+
+.\" .IX Header "EXAMPLES"
+.IX Header "Îã"
+
+.\" .IX Header "VARIABLES"
+.IX Header "ÊÑ¿ô"
+
+.IX Item "\s-1DEB_BUILD_ARCH\s0"
+
+.IX Item "\s-1DEB_BUILD_GNU_TYPE\s0"
+
+.IX Item "\s-1DEB_BUILD_GNU_CPU\s0"
+
+.IX Item "\s-1DEB_BUILD_GNU_SYSTEM\s0"
+
+.IX Item "\s-1DEB_HOST_ARCH\s0"
+
+.IX Item "\s-1DEB_HOST_GNU_TYPE\s0"
+
+.IX Item "\s-1DEB_HOST_GNU_CPU\s0"
+
+.IX Item "\s-1DEB_HOST_GNU_SYSTEM\s0"
+
+.IX Header "DEBIAN/RULES"
+
+.\" .IX Header "BACKWARD COMPATIBILITY"
+.IX Header "¸åÊý¸ß´¹À"
+
+.\" .IX Header "SEE ALSO"
+.IX Header "´ØÏ¢¹àÌÜ"
+
+.\" .IX Header "CONTACT"
+.IX Header "Ï¢Íí"
+
projects / dpkg / commitdiff