Rev 7158 | Go to most recent revision | Details | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 7156 | jlepiller | 1 | # SOME DESCRIPTIVE TITLE |
| 2 | # Copyright (C) YEAR Free Software Foundation, Inc. |
||
| 3 | # This file is distributed under the same license as the PACKAGE package. |
||
| 4 | # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. |
||
| 5 | # |
||
| 6 | msgid "" |
||
| 7 | msgstr "" |
||
| 8 | "Project-Id-Version: PACKAGE VERSION\n" |
||
| 9 | "POT-Creation-Date: 2016-09-23 12:00+0200\n" |
||
| 10 | "PO-Revision-Date: 2016-08-17 09:19+0000\n" |
||
| 11 | "Last-Translator: roptat <roptat@lepiller.eu>\n" |
||
| 12 | "Language-Team: LANGUAGE <LL@li.org>\n" |
||
| 13 | "Language: fr\n" |
||
| 14 | "MIME-Version: 1.0\n" |
||
| 15 | "Content-Type: text/plain; charset=UTF-8\n" |
||
| 16 | "Content-Transfer-Encoding: 8bit\n" |
||
| 17 | "Plural-Forms: nplurals=2; plural=(n > 1);\n" |
||
| 18 | "X-Generator: Pootle 2.7\n" |
||
| 19 | "X-POOTLE-MTIME: 1471425555.000000\n" |
||
| 20 | |||
| 21 | #. type: Content of: <sect1><sect1info> |
||
| 22 | #: blfs-en/introduction/important/building-notes.xml:12 |
||
| 23 | #, fuzzy |
||
| 24 | #| msgid "" |
||
| 25 | #| "<othername>$LastChangedBy: fernando $</othername> <date>$Date: 2015-11-13 " |
||
| 26 | #| "15:24:57 +0100 (Fri, 13 Nov 2015) $</date>" |
||
| 27 | msgid "" |
||
| 28 | "<othername>$LastChangedBy: fernando $</othername> <date>$Date: 2015-11-13 " |
||
| 29 | "15:24:57 +0100 (Fri 13 Nov 2015) $</date>" |
||
| 30 | msgstr "" |
||
| 31 | "<othername>$LastChangedBy: fernando $</othername> <date>$Date: 2015-11-13 " |
||
| 32 | "15:24:57 +0100 (mer., 13 nov. 2015) $</date>" |
||
| 33 | |||
| 34 | #. type: Content of: <sect1><title> |
||
| 35 | #: blfs-en/introduction/important/building-notes.xml:16 |
||
| 36 | msgid "Notes on Building Software" |
||
| 37 | msgstr "Remarques sur la construction de logiciels" |
||
| 38 | |||
| 39 | #. type: Content of: <sect1><para> |
||
| 40 | #: blfs-en/introduction/important/building-notes.xml:18 |
||
| 41 | msgid "" |
||
| 42 | "Those people who have built an LFS system may be aware of the general " |
||
| 43 | "principles of downloading and unpacking software. Some of that information " |
||
| 44 | "is repeated here for those new to building their own software." |
||
| 45 | msgstr "" |
||
| 46 | "Il se peut que les gens qui ont construit un système LFS connaissent les " |
||
| 47 | "principes généraux du téléchargement et du déballage de logiciel. Certaines " |
||
| 48 | "de ces informations sont répétées ici pour les nouveaux qui construisent " |
||
| 49 | "leurs propres logiciels." |
||
| 50 | |||
| 51 | #. type: Content of: <sect1><para> |
||
| 52 | #: blfs-en/introduction/important/building-notes.xml:23 |
||
| 53 | msgid "" |
||
| 54 | "Each set of installation instructions contains a URL from which you can " |
||
| 55 | "download the package. The patches; however, are stored on the LFS servers " |
||
| 56 | "and are available via HTTP. These are referenced as needed in the " |
||
| 57 | "installation instructions." |
||
| 58 | msgstr "" |
||
| 59 | "Chaque groupe d'instructions d'installation contient une adresse Web depuis " |
||
| 60 | "laquelle vous pouvez télécharger le paquet. Les correctifs cependant, sont " |
||
| 61 | "enregistrés sur les serveurs LFS et sont disponibles via HTTP. Ils sont " |
||
| 62 | "référencés comme nécessaires dans les instructions d'installation." |
||
| 63 | |||
| 64 | #. type: Content of: <sect1><para> |
||
| 65 | #: blfs-en/introduction/important/building-notes.xml:28 |
||
| 66 | msgid "" |
||
| 67 | "While you can keep the source files anywhere you like, we assume that you " |
||
| 68 | "have unpacked the package and changed into the directory created by the " |
||
| 69 | "unpacking process (the 'build' directory). We also assume you have " |
||
| 70 | "uncompressed any required patches and they are in the directory immediately " |
||
| 71 | "above the 'build' directory." |
||
| 72 | msgstr "" |
||
| 73 | "Si vous pouvez mettre les fichiers sources là où vous voulez, nous supposons " |
||
| 74 | "que vous avez déballé le paquet et êtes allé dans le répertoire créé par le " |
||
| 75 | "processus de déballage (le répertoire de 'construction'). Nous supposons " |
||
| 76 | "aussi que vous avez décompressé les correctifs requis et qu'ils sont dans " |
||
| 77 | "dans le répertoire de niveau immédiatement supérieur au répertoire de " |
||
| 78 | "'construction'." |
||
| 79 | |||
| 80 | #. type: Content of: <sect1><para> |
||
| 81 | #: blfs-en/introduction/important/building-notes.xml:34 |
||
| 82 | msgid "" |
||
| 83 | "We can not emphasize strongly enough that you should start from a " |
||
| 84 | "<emphasis>clean source tree</emphasis> each time. This means that if you " |
||
| 85 | "have had an error during configuration or compilation, it's usually best to " |
||
| 86 | "delete the source tree and re-unpack it <emphasis>before</emphasis> trying " |
||
| 87 | "again. This obviously doesn't apply if you're an advanced user used to " |
||
| 88 | "hacking <filename>Makefile</filename>s and C code, but if in doubt, start " |
||
| 89 | "from a clean tree." |
||
| 90 | msgstr "" |
||
| 91 | "Nous ne saurions que trop vous recommander de démarrer àpartir d'une " |
||
| 92 | "<emphasis>arborescence de sources propre</emphasis> à chaque fois. Cela " |
||
| 93 | "veut dire que si vous avez eu une erreur lors de la configuration ou de la " |
||
| 94 | "compilation, il est généralement préférable d'effacer l'arborescence des " |
||
| 95 | "sources et de la redéballer <emphasis>avant</emphasis> de réessayer. Cela ne " |
||
| 96 | "s'applique évidemment pas si vous êtes un utilisateur avancé habitué à " |
||
| 97 | "modifier les <filename>Makefile</filename>s et le code C, mais si vous avez " |
||
| 98 | "un doute, commencez à partir d'une arborescence propre." |
||
| 99 | |||
| 100 | #. type: Content of: <sect1><sect2><title> |
||
| 101 | #: blfs-en/introduction/important/building-notes.xml:44 |
||
| 102 | msgid "Building Software as an Unprivileged (non-root) User" |
||
| 103 | msgstr "" |
||
| 104 | "Construction de logiciels en tant qu'utilisateur non privilégié (non root)" |
||
| 105 | |||
| 106 | #. type: Content of: <sect1><sect2><para> |
||
| 107 | #: blfs-en/introduction/important/building-notes.xml:46 |
||
| 108 | msgid "" |
||
| 109 | "The golden rule of Unix System Administration is to use your superpowers " |
||
| 110 | "only when necessary. Hence, BLFS recommends that you build software as an " |
||
| 111 | "unprivileged user and only become the <systemitem class='username'>root</" |
||
| 112 | "systemitem> user when installing the software. This philosophy is followed " |
||
| 113 | "in all the packages in this book. Unless otherwise specified, all " |
||
| 114 | "instructions should be executed as an unprivileged user. The book will " |
||
| 115 | "advise you on instructions that need <systemitem class='username'>root</" |
||
| 116 | "systemitem> privileges." |
||
| 117 | msgstr "" |
||
| 118 | "La règle d'or de l'administration d'un système Unix est de n'utiliser vos " |
||
| 119 | "super-pouvoirs que si nécessaire. D'où la recommandation de BLFS de " |
||
| 120 | "construire les logiciels en tant qu'utilisateur non privilégié et de ne " |
||
| 121 | "devenir l'utilisateur <systemitem class='username'>root</systemitem> que " |
||
| 122 | "lors de l'installation du logiciel. On suit cette philosophie dans tous les " |
||
| 123 | "paquets du livre. Sauf spécifications contraires, toutes les instructions " |
||
| 124 | "devraient être exécutées en tant qu'utilisateur non privilégié. Le livre " |
||
| 125 | "vous conseillera sur les instructions qui ont besoin des privilèges " |
||
| 126 | "<systemitem class='username'>root</systemitem>." |
||
| 127 | |||
| 128 | #. type: Content of: <sect1><sect2><title> |
||
| 129 | #: blfs-en/introduction/important/building-notes.xml:58 |
||
| 130 | msgid "Unpacking the Software" |
||
| 131 | msgstr "Déballer le logiciel" |
||
| 132 | |||
| 133 | #. type: Content of: <sect1><sect2><para> |
||
| 134 | #: blfs-en/introduction/important/building-notes.xml:60 |
||
| 135 | msgid "" |
||
| 136 | "If a file is in <filename class='extension'>.tar</filename> format and " |
||
| 137 | "compressed, it is unpacked by running one of the following commands:" |
||
| 138 | msgstr "" |
||
| 139 | "S'il y a un fichier compressé au format <filename class='extension'>.tar</" |
||
| 140 | "filename>, on le déballe en utilisant une des commandes suivantes :" |
||
| 141 | |||
| 142 | #. type: Content of: <sect1><sect2><screen> |
||
| 143 | #: blfs-en/introduction/important/building-notes.xml:64 |
||
| 144 | #, no-wrap |
||
| 145 | msgid "" |
||
| 146 | "<userinput>tar -xvf filename.tar.gz\n" |
||
| 147 | "tar -xvf filename.tgz\n" |
||
| 148 | "tar -xvf filename.tar.Z\n" |
||
| 149 | "tar -xvf filename.tar.bz2</userinput>" |
||
| 150 | msgstr "" |
||
| 151 | "<userinput>tar -xvf filename.tar.gz\n" |
||
| 152 | "tar -xvf filename.tgz\n" |
||
| 153 | "tar -xvf filename.tar.Z\n" |
||
| 154 | "tar -xvf filename.tar.bz2</userinput>" |
||
| 155 | |||
| 156 | #. type: Content of: <sect1><sect2><note><para> |
||
| 157 | #: blfs-en/introduction/important/building-notes.xml:70 |
||
| 158 | msgid "" |
||
| 159 | "You may omit using the <option>v</option> parameter in the commands shown " |
||
| 160 | "above and below if you wish to suppress the verbose listing of all the files " |
||
| 161 | "in the archive as they are extracted. This can help speed up the extraction " |
||
| 162 | "as well as make any errors produced during the extraction more obvious to " |
||
| 163 | "you." |
||
| 164 | msgstr "" |
||
| 165 | "Vous pouvez ne pas utiliser le paramètre <option>v</option> dans les " |
||
| 166 | "commandes décrites ci-dessus et ci-dessous si vous souhaitez supprimer le " |
||
| 167 | "listage verbeux de tous les fichiers de l'archive au fur et à mesure qu'ils " |
||
| 168 | "sont extraits. Cela peut aider à accélérer l'extraction mais aussi rendre la " |
||
| 169 | "compréhension des erreurs produites pendant l'extraction moins évidentes." |
||
| 170 | |||
| 171 | #. type: Content of: <sect1><sect2><para> |
||
| 172 | #: blfs-en/introduction/important/building-notes.xml:77 |
||
| 173 | msgid "You can also use a slightly different method:" |
||
| 174 | msgstr "Vous pouvez utiliser aussi une méthode légèrement différente :" |
||
| 175 | |||
| 176 | #. type: Content of: <sect1><sect2><screen> |
||
| 177 | #: blfs-en/introduction/important/building-notes.xml:79 |
||
| 178 | #, no-wrap |
||
| 179 | msgid "<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>" |
||
| 180 | msgstr "<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>" |
||
| 181 | |||
| 182 | #. type: Content of: <sect1><sect2><para> |
||
| 183 | #: blfs-en/introduction/important/building-notes.xml:81 |
||
| 184 | msgid "" |
||
| 185 | "Finally, you sometimes need to be able to unpack patches which are generally " |
||
| 186 | "not in <filename class='extension'>.tar</filename> format. The best way to " |
||
| 187 | "do this is to copy the patch file to the parent of the 'build' directory and " |
||
| 188 | "then run one of the following commands depending on whether the file is a " |
||
| 189 | "<filename class='extension'>.gz</filename> or <filename class='extension'>." |
||
| 190 | "bz2</filename> file:" |
||
| 191 | msgstr "" |
||
| 192 | "Enfin, vous avez parfois besoin de déballer des correctifs qui ne sont " |
||
| 193 | "généralement pas au format <filename class='extension'>.tar</filename>. La " |
||
| 194 | "meilleure manière de faire cela est de copier le chemin du fichier dans le " |
||
| 195 | "parent du répertoire de 'construction' puis d'exécuter une des commandes " |
||
| 196 | "suivantes selon que le fichier est un <filename class='extension'>.gz</" |
||
| 197 | "filename> ou un <filename class='extension'>.bz2</filename> :" |
||
| 198 | |||
| 199 | #. type: Content of: <sect1><sect2><screen> |
||
| 200 | #: blfs-en/introduction/important/building-notes.xml:88 |
||
| 201 | #, no-wrap |
||
| 202 | msgid "" |
||
| 203 | "<userinput>gunzip -v patchname.gz\n" |
||
| 204 | "bunzip2 -v patchname.bz2</userinput>" |
||
| 205 | msgstr "" |
||
| 206 | "<userinput>gunzip -v patchname.gz\n" |
||
| 207 | "bunzip2 -v patchname.bz2</userinput>" |
||
| 208 | |||
| 209 | #. type: Content of: <sect1><sect2><title> |
||
| 210 | #: blfs-en/introduction/important/building-notes.xml:94 |
||
| 211 | msgid "Verifying File Integrity Using 'md5sum'" |
||
| 212 | msgstr "Vérifier l'intégrité des fichiers en utilisant 'md5sum'" |
||
| 213 | |||
| 214 | #. type: Content of: <sect1><sect2><para> |
||
| 215 | #: blfs-en/introduction/important/building-notes.xml:96 |
||
| 216 | msgid "" |
||
| 217 | "Generally, to verify that the downloaded file is genuine and complete, many " |
||
| 218 | "package maintainers also distribute md5sums of the files. To verify the " |
||
| 219 | "md5sum of the downloaded files, download both the file and the corresponding " |
||
| 220 | "md5sum file to the same directory (preferably from different on-line " |
||
| 221 | "locations), and (assuming <filename>file.md5sum</filename> is the md5sum " |
||
| 222 | "file downloaded) run the following command:" |
||
| 223 | msgstr "" |
||
| 224 | "En général, pour vérifier que le fichier téléchargé est authentique et " |
||
| 225 | "complet, de nombreux mainteneurs de paquets distribuent aussi des sommes md5 " |
||
| 226 | "des fichiers. Pour vérifier la somme md5 des fichiers téléchargés, " |
||
| 227 | "téléchargez à la fois le fichier et le fichier md5sum correspondant dans le " |
||
| 228 | "même répertoire (de préférence à partir d'emplacements différents en ligne) " |
||
| 229 | "et (en supposant que <filename>file.md5sum</filename> est le fichier md5sum " |
||
| 230 | "téléchargé), lancez la commande suivante :" |
||
| 231 | |||
| 232 | #. type: Content of: <sect1><sect2><screen> |
||
| 233 | #: blfs-en/introduction/important/building-notes.xml:103 |
||
| 234 | #, no-wrap |
||
| 235 | msgid "<userinput>md5sum -c file.md5sum</userinput>" |
||
| 236 | msgstr "<userinput>md5sum -c file.md5sum</userinput>" |
||
| 237 | |||
| 238 | #. type: Content of: <sect1><sect2><para> |
||
| 239 | #: blfs-en/introduction/important/building-notes.xml:105 |
||
| 240 | msgid "" |
||
| 241 | "If there are any errors, they will be reported. Note that the BLFS book " |
||
| 242 | "includes md5sums for all the source files also. To use the BLFS supplied " |
||
| 243 | "md5sums, you can create a <filename>file.md5sum</filename> (place the md5sum " |
||
| 244 | "data and the exact name of the downloaded file on the same line of a file, " |
||
| 245 | "separated by white space) and run the command shown above. Alternately, " |
||
| 246 | "simply run the command shown below and compare the output to the md5sum data " |
||
| 247 | "shown in the BLFS book." |
||
| 248 | msgstr "" |
||
| 249 | "S'il y a une erreur, elle sera signalée. Remarquez que le livre BLFS " |
||
| 250 | "comprend les sommes md5 de tous les fichiers sources. Pour utiliser les " |
||
| 251 | "sommes md5 fournies par BLFS, vous pouvez créer un <filename>file.md5sum</" |
||
| 252 | "filename> (mettez les données md5sum et le nom exact du fichier téléchargé " |
||
| 253 | "sur la même ligne d'un fichier, séparés par un espace blanc), et lancez la " |
||
| 254 | "commande montrée ci-dessus. Sinon, lancez simplement la commande décrite ci-" |
||
| 255 | "dessus et comparez la sortie avec les données de somme md5 inscrites dans le " |
||
| 256 | "livre BLFS." |
||
| 257 | |||
| 258 | #. type: Content of: <sect1><sect2><screen> |
||
| 259 | #: blfs-en/introduction/important/building-notes.xml:113 |
||
| 260 | #, no-wrap |
||
| 261 | msgid "<userinput>md5sum <replaceable><name_of_downloaded_file></replaceable></userinput>" |
||
| 262 | msgstr "<userinput>md5sum <replaceable><name_of_downloaded_file></replaceable></userinput>" |
||
| 263 | |||
| 264 | #. type: Content of: <sect1><sect2><title> |
||
| 265 | #: blfs-en/introduction/important/building-notes.xml:118 |
||
| 266 | msgid "Creating Log Files During Installation" |
||
| 267 | msgstr "Créer des fichiers journaux pendant l'installation" |
||
| 268 | |||
| 269 | #. type: Content of: <sect1><sect2><para> |
||
| 270 | #: blfs-en/introduction/important/building-notes.xml:120 |
||
| 271 | msgid "" |
||
| 272 | "For larger packages, it is convenient to create log files instead of staring " |
||
| 273 | "at the screen hoping to catch a particular error or warning. Log files are " |
||
| 274 | "also useful for debugging and keeping records. The following command allows " |
||
| 275 | "you to create an installation log. Replace <replaceable><command></" |
||
| 276 | "replaceable> with the command you intend to execute." |
||
| 277 | msgstr "" |
||
| 278 | "Pour les gros paquets, il est commode de créer des fichiers journaux plutôt " |
||
| 279 | "que de dévisager l'écran en espérant récupérer une erreur ou un " |
||
| 280 | "avertissement particulier. Les fichiers journaux sont aussi utiles pour " |
||
| 281 | "déboguer et garder des enregistrements. La commande suivante vous permet de " |
||
| 282 | "créer un journal d'installation. Remplacez <replaceable><commande></" |
||
| 283 | "replaceable> par la commande que vous cherchez à exécuter." |
||
| 284 | |||
| 285 | #. type: Content of: <sect1><sect2><screen> |
||
| 286 | #: blfs-en/introduction/important/building-notes.xml:126 |
||
| 287 | #, no-wrap |
||
| 288 | msgid "<userinput>( <replaceable><command></replaceable> 2>&1 | tee compile.log && exit $PIPESTATUS )</userinput>" |
||
| 289 | msgstr "<userinput>( <replaceable><command></replaceable> 2>&1 | tee compile.log && exit $PIPESTATUS )</userinput>" |
||
| 290 | |||
| 291 | #. type: Content of: <sect1><sect2><para> |
||
| 292 | #: blfs-en/introduction/important/building-notes.xml:128 |
||
| 293 | msgid "" |
||
| 294 | "<option>2>&1</option> redirects error messages to the same location " |
||
| 295 | "as standard output. The <command>tee</command> command allows viewing of the " |
||
| 296 | "output while logging the results to a file. The parentheses around the " |
||
| 297 | "command run the entire command in a subshell and finally the <command>exit " |
||
| 298 | "$PIPESTATUS</command> command ensures the result of the <replaceable><" |
||
| 299 | "command></replaceable> is returned as the result and not the result of " |
||
| 300 | "the <command>tee</command> command." |
||
| 301 | msgstr "" |
||
| 302 | "<option>2>&1</option> redirige les messages d'erreur vers le même " |
||
| 303 | "endroit que la sortie standard. La commande <command>tee</command> vous " |
||
| 304 | "permet de voir la sortie en journalisant les résultats dans un fichier. Les " |
||
| 305 | "parenthèses autour de la commande exécutent toute la commande dans un sous-" |
||
| 306 | "shell et, enfin, la commande <command>exit $PIPESTATUS</command> s'assure " |
||
| 307 | "que c'est bien le résultat de <replaceable><commande></replaceable> " |
||
| 308 | "qui est retourné et pas le résultat de la commande <command>tee</command>." |
||
| 309 | |||
| 310 | #. type: Content of: <sect1><sect2><title> |
||
| 311 | #: blfs-en/introduction/important/building-notes.xml:139 |
||
| 312 | msgid "Using Multiple Processors" |
||
| 313 | msgstr "Utilisation de processeurs multiples" |
||
| 314 | |||
| 315 | #. type: Content of: <sect1><sect2><para> |
||
| 316 | #: blfs-en/introduction/important/building-notes.xml:141 |
||
| 317 | msgid "" |
||
| 318 | "For many modern systems with multiple processors (or cores) the compilation " |
||
| 319 | "time for a package can be reduced by performing a \"parallel make\" by " |
||
| 320 | "either setting an environment variable or telling the make program how many " |
||
| 321 | "processors are available. For instance, a Core2Duo can support two " |
||
| 322 | "simultaneous processes with:" |
||
| 323 | msgstr "" |
||
| 324 | "Pour la plupart des systèmes modernes avec des processeurs multiples ( ou " |
||
| 325 | "cœurs) le temps de compilation pour un paquet peut être réduit en effectuant " |
||
| 326 | "une « construction parallèle » soit en initialisant une variable " |
||
| 327 | "d'environnement, soit en disant au programme make combien de processeurs " |
||
| 328 | "sont disponibles. Par exemple, un Core2Duo peut supporter deux processus " |
||
| 329 | "simultanées avec :" |
||
| 330 | |||
| 331 | #. type: Content of: <sect1><sect2><screen> |
||
| 332 | #: blfs-en/introduction/important/building-notes.xml:147 |
||
| 333 | #, no-wrap |
||
| 334 | msgid "<userinput>export MAKEFLAGS='-j2'</userinput>" |
||
| 335 | msgstr "<userinput>export MAKEFLAGS='-j2'</userinput>" |
||
| 336 | |||
| 337 | #. type: Content of: <sect1><sect2><para> |
||
| 338 | #: blfs-en/introduction/important/building-notes.xml:149 |
||
| 339 | msgid "or just building with:" |
||
| 340 | msgstr "ou en compilant simplement avec :" |
||
| 341 | |||
| 342 | #. type: Content of: <sect1><sect2><screen> |
||
| 343 | #: blfs-en/introduction/important/building-notes.xml:151 |
||
| 344 | #, no-wrap |
||
| 345 | msgid "<userinput>make -j2</userinput>" |
||
| 346 | msgstr "<userinput>make -j2</userinput>" |
||
| 347 | |||
| 348 | #. type: Content of: <sect1><sect2><para> |
||
| 349 | #: blfs-en/introduction/important/building-notes.xml:153 |
||
| 350 | msgid "" |
||
| 351 | "Generally the number of processes should not exceed the number of cores " |
||
| 352 | "supported by the CPU. To list the processors on your system, issue: " |
||
| 353 | "<userinput>grep processor /proc/cpuinfo</userinput>." |
||
| 354 | msgstr "" |
||
| 355 | "Généralement le nombre de processus ne doit pas dépasser le nombre de cœurs " |
||
| 356 | "supportés par le CPU. Pour lister les processeurs de votre système, tapez : " |
||
| 357 | "<userinput>grep processor /proc/cpuinfo</userinput>." |
||
| 358 | |||
| 359 | #. type: Content of: <sect1><sect2><para> |
||
| 360 | #: blfs-en/introduction/important/building-notes.xml:158 |
||
| 361 | msgid "" |
||
| 362 | "In some cases, using multiple processors may result in a 'race' condition " |
||
| 363 | "where the success of the build depends on the order of the commands run by " |
||
| 364 | "the <command>make</command> program. For instance, if an executable needs " |
||
| 365 | "File A and File B, attempting to link the program before one of the " |
||
| 366 | "dependent components is available will result in a failure. This condition " |
||
| 367 | "usually arises because the upstream developer has not properly designated " |
||
| 368 | "all the prerequsites needed to accomplish a step in the Makefile." |
||
| 369 | msgstr "" |
||
| 370 | "Dans certains cas, l'utilisation de processeurs multiples peut amener dans " |
||
| 371 | "une sorte de « course » où le succès de la construction dépend de " |
||
| 372 | "l'ordre des commandes lancées par le programme <command>make</command>. Par " |
||
| 373 | "exemple, si un exécutable demande un fichier A et un fichier B, en essayant " |
||
| 374 | "de lier le programme avant qu'un des composants dépendants ne soit " |
||
| 375 | "disponible, aboutira à un échec. Cela est possible car les développeurs " |
||
| 376 | "n'ont pas proprement désigné tous les prérequis utiles pour accomplir une " |
||
| 377 | "étape du Makefile." |
||
| 378 | |||
| 379 | #. type: Content of: <sect1><sect2><para> |
||
| 380 | #: blfs-en/introduction/important/building-notes.xml:167 |
||
| 381 | msgid "" |
||
| 382 | "If this occurs, the best way to proceed is to drop back to a single " |
||
| 383 | "processor build. Adding '-j1' to a make command will override the similar " |
||
| 384 | "setting in the MAKEFLAGS environment variable." |
||
| 385 | msgstr "" |
||
| 386 | "Si cela arrive, la meilleure chose à faire est revenir à la construction " |
||
| 387 | "avec un seul processeur. En ajoutant « -j1 » à une commande make, " |
||
| 388 | "cela écrasera l'initialisation similaire dans une variable d'environnement " |
||
| 389 | "MAKEFLAGS." |
||
| 390 | |||
| 391 | #. type: Content of: <sect1><sect2><title> |
||
| 392 | #: blfs-en/introduction/important/building-notes.xml:174 |
||
| 393 | msgid "Automated Building Procedures" |
||
| 394 | msgstr "Procédures de construction automatique" |
||
| 395 | |||
| 396 | #. type: Content of: <sect1><sect2><para> |
||
| 397 | #: blfs-en/introduction/important/building-notes.xml:176 |
||
| 398 | msgid "" |
||
| 399 | "There are times when automating the building of a package can come in handy. " |
||
| 400 | "Everyone has their own reasons for wanting to automate building, and " |
||
| 401 | "everyone goes about it in their own way. Creating <filename>Makefile</" |
||
| 402 | "filename>s, <application>Bash</application> scripts, <application>Perl</" |
||
| 403 | "application> scripts or simply a list of commands used to cut and paste are " |
||
| 404 | "just some of the methods you can use to automate building BLFS packages. " |
||
| 405 | "Detailing how and providing examples of the many ways you can automate the " |
||
| 406 | "building of packages is beyond the scope of this section. This section will " |
||
| 407 | "expose you to using file redirection and the <command>yes</command> command " |
||
| 408 | "to help provide ideas on how to automate your builds." |
||
| 409 | msgstr "" |
||
| 410 | "Il y a des fois où automatiser la construction d'un paquet peut s'avérer " |
||
| 411 | "utile. Chacun a ses raisons de vouloir automatiser la construction, et " |
||
| 412 | "chacun le fait par ses propres moyens. Soit en créant des " |
||
| 413 | "<filename>Makefile</filename>s, des scripts <application>Bash</application>, " |
||
| 414 | "des scripts <application>Perl</application> ou simplement une liste de " |
||
| 415 | "commandes utilisées à copier-coller, sont des méthodes que vous pouvez " |
||
| 416 | "utiliser pour automatiser la construction de paquets BLFS. Détailler et " |
||
| 417 | "donner des exemples sur les nombreuses manières d'automatiser la " |
||
| 418 | "construction de paquets va au-delà des objectifs de cette section. Cette " |
||
| 419 | "section vous présentera l'utilisation de la redirection de fichiers et de la " |
||
| 420 | "commande <command>yes</command> pour vous donner des idées sur la façon " |
||
| 421 | "d'automatiser vos constructions." |
||
| 422 | |||
| 423 | #. type: Content of: <sect1><sect2><bridgehead> |
||
| 424 | #: blfs-en/introduction/important/building-notes.xml:188 |
||
| 425 | msgid "File Redirection to Automate Input" |
||
| 426 | msgstr "Redirection de fichier pour automatiser l'entrée" |
||
| 427 | |||
| 428 | #. type: Content of: <sect1><sect2><para> |
||
| 429 | #: blfs-en/introduction/important/building-notes.xml:190 |
||
| 430 | msgid "" |
||
| 431 | "You will find times throughout your BLFS journey when you will come across a " |
||
| 432 | "package that has a command prompting you for information. This information " |
||
| 433 | "might be configuration details, a directory path, or a response to a license " |
||
| 434 | "agreement. This can present a challenge to automate the building of that " |
||
| 435 | "package. Occasionally, you will be prompted for different information in a " |
||
| 436 | "series of questions. One method to automate this type of scenario requires " |
||
| 437 | "putting the desired responses in a file and using redirection so that the " |
||
| 438 | "program uses the data in the file as the answers to the questions." |
||
| 439 | msgstr "" |
||
| 440 | "Il y aura des moments, pendant votre aventure BLFS, où vous tomberez sur un " |
||
| 441 | "paquet ayant une invite de commande vous demandant des informations. Ces " |
||
| 442 | "informations peuvent être des détails de configuration, un chemin de " |
||
| 443 | "répertoire ou une réponse à un accord de licence. Il peut être un challenge " |
||
| 444 | "d'automatiser la construction de ce paquet. On vous demandera " |
||
| 445 | "occasionnellement des informations via une série de questions. Une méthode " |
||
| 446 | "pour automatiser ce type de scénario est de mettre les réponses désirées " |
||
| 447 | "dans un fichier et d'utiliser la redirection pour que le programme utilise " |
||
| 448 | "les données du fichier comme réponses aux questions." |
||
| 449 | |||
| 450 | #. type: Content of: <sect1><sect2><para> |
||
| 451 | #: blfs-en/introduction/important/building-notes.xml:200 |
||
| 452 | msgid "" |
||
| 453 | "Building the <application>CUPS</application> package is a good example of " |
||
| 454 | "how redirecting a file as input to prompts can help you automate the build. " |
||
| 455 | "If you run the test suite, you are asked to respond to a series of questions " |
||
| 456 | "regarding the type of test to run and if you have any auxiliary programs the " |
||
| 457 | "test can use. You can create a file with your responses, one response per " |
||
| 458 | "line, and use a command similar to the one shown below to automate running " |
||
| 459 | "the test suite:" |
||
| 460 | msgstr "" |
||
| 461 | "La construction du paquet <application>CUPS</application> est un bon exemple " |
||
| 462 | "de la façon de rediriger un fichier comme entrée aux invites, cela peut vous " |
||
| 463 | "aider à automatiser la construction. Si vous lancez la suite de test, on " |
||
| 464 | "vous demande de répondre à une série de questions concernant le type de test " |
||
| 465 | "à exécuter et si vous avez un programme auxiliaire que le test peut " |
||
| 466 | "utiliser. Vous pouvez créer un fichier avec vos réponses, une par ligne, et " |
||
| 467 | "utiliser une commande ressemblant à celle indiquée ci-dessous pour " |
||
| 468 | "automatiser l'exécution de la suite de tests :" |
||
| 469 | |||
| 470 | #. type: Content of: <sect1><sect2><screen> |
||
| 471 | #: blfs-en/introduction/important/building-notes.xml:208 |
||
| 472 | #, no-wrap |
||
| 473 | msgid "<userinput>make check < ../cups-1.1.23-testsuite_parms</userinput>" |
||
| 474 | msgstr "<userinput>make check < ../cups-1.1.23-testsuite_parms</userinput>" |
||
| 475 | |||
| 476 | #. type: Content of: <sect1><sect2><para> |
||
| 477 | #: blfs-en/introduction/important/building-notes.xml:210 |
||
| 478 | msgid "" |
||
| 479 | "This effectively makes the test suite use the responses in the file as the " |
||
| 480 | "input to the questions. Occasionally you may end up doing a bit of trial and " |
||
| 481 | "error determining the exact format of your input file for some things, but " |
||
| 482 | "once figured out and documented you can use this to automate building the " |
||
| 483 | "package." |
||
| 484 | msgstr "" |
||
| 485 | "Cela fait que la suite de tests utilise les réponses du fichier comme entrée " |
||
| 486 | "pour les questions. Vous pouvez finir par faire des essais et des erreurs " |
||
| 487 | "pour déterminer le format exact de votre fichier d'entrée pour certaines " |
||
| 488 | "choses, mais une fois expérimenté et documenté, vous pouvez utiliser cela " |
||
| 489 | "pour automatiser la construction du paquet." |
||
| 490 | |||
| 491 | #. type: Content of: <sect1><sect2><bridgehead> |
||
| 492 | #: blfs-en/introduction/important/building-notes.xml:216 |
||
| 493 | msgid "Using <command>yes</command> to Automate Input" |
||
| 494 | msgstr "Utiliser <command>yes</command> pour automatiser l'entrée" |
||
| 495 | |||
| 496 | #. type: Content of: <sect1><sect2><para> |
||
| 497 | #: blfs-en/introduction/important/building-notes.xml:219 |
||
| 498 | msgid "" |
||
| 499 | "Sometimes you will only need to provide one response, or provide the same " |
||
| 500 | "response to many prompts. For these instances, the <command>yes</command> " |
||
| 501 | "command works really well. The <command>yes</command> command can be used to " |
||
| 502 | "provide a response (the same one) to one or more instances of questions. It " |
||
| 503 | "can be used to simulate pressing just the <keycap>Enter</keycap> key, " |
||
| 504 | "entering the <keycap>Y</keycap> key or entering a string of text. Perhaps " |
||
| 505 | "the easiest way to show its use is in an example." |
||
| 506 | msgstr "" |
||
| 507 | "Vous n'aurez parfois besoin que de fournir une réponse ou une même réponse à " |
||
| 508 | "de nombreuses invites. Dans ces cas-là, la commande <command>yes</command> " |
||
| 509 | "fonctionne vraiment bien. On peut utiliser la commande <command>yes</" |
||
| 510 | "command> pour fournir une réponse (la même) à une ou plusieurs questions. On " |
||
| 511 | "peut l'utiliser pour simuler un simple appui sur la touche <keycap>Entrée</" |
||
| 512 | "keycap>, l'entrée de la touche <keycap>Y</keycap> ou l'entrée d'une chaîne " |
||
| 513 | "de texte. La manière la plus facile de montrer son utilisation est peut-être " |
||
| 514 | "de prendre un exemple." |
||
| 515 | |||
| 516 | #. type: Content of: <sect1><sect2><para> |
||
| 517 | #: blfs-en/introduction/important/building-notes.xml:228 |
||
| 518 | msgid "" |
||
| 519 | "First, create a short <application>Bash</application> script by entering the " |
||
| 520 | "following commands:" |
||
| 521 | msgstr "" |
||
| 522 | "Créez tout d'abord un petit script <application>Bash</application> en " |
||
| 523 | "entrant les commandes suivantes :" |
||
| 524 | |||
| 525 | #. type: Content of: <sect1><sect2><screen> |
||
| 526 | #: blfs-en/introduction/important/building-notes.xml:231 |
||
| 527 | #, no-wrap |
||
| 528 | msgid "" |
||
| 529 | "<userinput>cat > blfs-yes-test1 << \"EOF\"\n" |
||
| 530 | "<literal>#!/bin/bash\n" |
||
| 531 | "\n" |
||
| 532 | "echo -n -e \"\\n\\nPlease type something (or nothing) and press Enter ---> \"\n" |
||
| 533 | "\n" |
||
| 534 | "read A_STRING\n" |
||
| 535 | "\n" |
||
| 536 | "if test \"$A_STRING\" = \"\"; then A_STRING=\"Just the Enter key was pressed\"\n" |
||
| 537 | "else A_STRING=\"You entered '$A_STRING'\"\n" |
||
| 538 | "fi\n" |
||
| 539 | "\n" |
||
| 540 | "echo -e \"\\n\\n$A_STRING\\n\\n\"</literal>\n" |
||
| 541 | "EOF\n" |
||
| 542 | "chmod 755 blfs-yes-test1</userinput>" |
||
| 543 | msgstr "" |
||
| 544 | "<userinput>cat > blfs-yes-test1 << \"EOF\"\n" |
||
| 545 | "<literal>#!/bin/bash\n" |
||
| 546 | "\n" |
||
| 547 | "echo -n -e \"\\n\\nPlease type something (or nothing) and press Enter ---> \"\n" |
||
| 548 | "\n" |
||
| 549 | "read A_STRING\n" |
||
| 550 | "\n" |
||
| 551 | "if test \"$A_STRING\" = \"\"; then A_STRING=\"Just the Enter key was pressed\"\n" |
||
| 552 | "else A_STRING=\"You entered '$A_STRING'\"\n" |
||
| 553 | "fi\n" |
||
| 554 | "\n" |
||
| 555 | "echo -e \"\\n\\n$A_STRING\\n\\n\"</literal>\n" |
||
| 556 | "EOF\n" |
||
| 557 | "chmod 755 blfs-yes-test1</userinput>" |
||
| 558 | |||
| 559 | #. type: Content of: <sect1><sect2><para> |
||
| 560 | #: blfs-en/introduction/important/building-notes.xml:246 |
||
| 561 | msgid "" |
||
| 562 | "Now run the script by issuing <command>./blfs-yes-test1</command> from the " |
||
| 563 | "command line. It will wait for a response, which can be anything (or " |
||
| 564 | "nothing) followed by the <keycap>Enter</keycap> key. After entering " |
||
| 565 | "something, the result will be echoed to the screen. Now use the " |
||
| 566 | "<command>yes</command> command to automate the entering of a response:" |
||
| 567 | msgstr "" |
||
| 568 | "Maintenant, lancez le script en lançant <command>./blfs-yes-test1</command> " |
||
| 569 | "depuis la ligne de commande. Il attendra une réponse, qui peut être " |
||
| 570 | "n'importe quoi (ou rien) suivi de la touche <keycap>Entrée</keycap>. Après " |
||
| 571 | "avoir entré quelque chose, le résultat sera affiché à l'écran. Utilisez " |
||
| 572 | "maintenant la commande <command>yes</command> pour automatiser l'entrée " |
||
| 573 | "d'une réponse :" |
||
| 574 | |||
| 575 | #. type: Content of: <sect1><sect2><screen> |
||
| 576 | #: blfs-en/introduction/important/building-notes.xml:253 |
||
| 577 | #, no-wrap |
||
| 578 | msgid "<userinput>yes | ./blfs-yes-test1</userinput>" |
||
| 579 | msgstr "<userinput>yes | ./blfs-yes-test1</userinput>" |
||
| 580 | |||
| 581 | #. type: Content of: <sect1><sect2><para> |
||
| 582 | #: blfs-en/introduction/important/building-notes.xml:255 |
||
| 583 | msgid "" |
||
| 584 | "Notice that piping <command>yes</command> by itself to the script results in " |
||
| 585 | "<keycap>y</keycap> being passed to the script. Now try it with a string of " |
||
| 586 | "text:" |
||
| 587 | msgstr "" |
||
| 588 | "Remarquez que la redirection (le piping) de <command>yes</command> en lui-" |
||
| 589 | "même vers le script aboutit à ce que <keycap>y</keycap> est passé au script. " |
||
| 590 | "Essayez-la maintenant avec une chaîne de texte :" |
||
| 591 | |||
| 592 | #. type: Content of: <sect1><sect2><screen> |
||
| 593 | #: blfs-en/introduction/important/building-notes.xml:259 |
||
| 594 | #, no-wrap |
||
| 595 | msgid "<userinput>yes 'This is some text' | ./blfs-yes-test1</userinput>" |
||
| 596 | msgstr "<userinput>yes 'This is some text' | ./blfs-yes-test1</userinput>" |
||
| 597 | |||
| 598 | #. type: Content of: <sect1><sect2><para> |
||
| 599 | #: blfs-en/introduction/important/building-notes.xml:261 |
||
| 600 | msgid "" |
||
| 601 | "The exact string was used as the response to the script. Finally, try it " |
||
| 602 | "using an empty (null) string:" |
||
| 603 | msgstr "" |
||
| 604 | "La chaîne exacte était utilisée comme réponse au script. Enfin, essayez-la " |
||
| 605 | "en utilisant une chaîne vide (null) :" |
||
| 606 | |||
| 607 | #. type: Content of: <sect1><sect2><screen> |
||
| 608 | #: blfs-en/introduction/important/building-notes.xml:264 |
||
| 609 | #, no-wrap |
||
| 610 | msgid "<userinput>yes '' | ./blfs-yes-test1</userinput>" |
||
| 611 | msgstr "<userinput>yes '' | ./blfs-yes-test1</userinput>" |
||
| 612 | |||
| 613 | #. type: Content of: <sect1><sect2><para> |
||
| 614 | #: blfs-en/introduction/important/building-notes.xml:266 |
||
| 615 | msgid "" |
||
| 616 | "Notice this results in passing just the press of the <keycap>Enter</keycap> " |
||
| 617 | "key to the script. This is useful for times when the default answer to the " |
||
| 618 | "prompt is sufficient. This syntax is used in the <xref linkend=\"net-tools-" |
||
| 619 | "automate-example\"/> instructions to accept all the defaults to the many " |
||
| 620 | "prompts during the configuration step. You may now remove the test script, " |
||
| 621 | "if desired." |
||
| 622 | msgstr "" |
||
| 623 | "Remarquez que cela aboutit à ne passer au script que l'appui sur la touche " |
||
| 624 | "<keycap>Entrée</keycap>. C'est utile parfois quand la réponse par défaut à " |
||
| 625 | "l'invite est suffisante. Cette syntaxe est utilisée dans les instructions de " |
||
| 626 | "<xref linkend=\"net-tools-automate-example\"/> pour accepter tous les " |
||
| 627 | "réglages par défaut à toutes les invites lors de l'étape de configuration. " |
||
| 628 | "Vous pouvez maintenant supprimer le script de test si vous le désirez." |
||
| 629 | |||
| 630 | #. type: Content of: <sect1><sect2><bridgehead> |
||
| 631 | #: blfs-en/introduction/important/building-notes.xml:273 |
||
| 632 | msgid "File Redirection to Automate Output" |
||
| 633 | msgstr "Redirection de fichiers pour automatiser la sortie" |
||
| 634 | |||
| 635 | #. type: Content of: <sect1><sect2><para> |
||
| 636 | #: blfs-en/introduction/important/building-notes.xml:275 |
||
| 637 | msgid "" |
||
| 638 | "In order to automate the building of some packages, especially those that " |
||
| 639 | "require you to read a license agreement one page at a time, requires using a " |
||
| 640 | "method that avoids having to press a key to display each page. Redirecting " |
||
| 641 | "the output to a file can be used in these instances to assist with the " |
||
| 642 | "automation. The previous section on this page touched on creating log files " |
||
| 643 | "of the build output. The redirection method shown there used the " |
||
| 644 | "<command>tee</command> command to redirect output to a file while also " |
||
| 645 | "displaying the output to the screen. Here, the output will only be sent to a " |
||
| 646 | "file." |
||
| 647 | msgstr "" |
||
| 648 | "Pour automatiser la construction de certains paquets, surtout ceux qui vous " |
||
| 649 | "demandent de lire un accord de licence page après page, il faut utiliser une " |
||
| 650 | "méthode qui évite de devoir appuyer sur une touche pour afficher chaque " |
||
| 651 | "page. On peut utiliser la redirection de sortie vers un fichier dans ce cas-" |
||
| 652 | "là pour vous aider à automatiser. La section précédente de cette page a visé " |
||
| 653 | "à créer des fichiers journaux de la sortie de la construction. La méthode " |
||
| 654 | "de redirection qui y est décrite utilisait la commande <command>tee</" |
||
| 655 | "command> pour rediriger la sortie tout en affichant aussi la sortie à " |
||
| 656 | "l'écran. Ici on ne verra la sortie que dans un fichier." |
||
| 657 | |||
| 658 | #. type: Content of: <sect1><sect2><para> |
||
| 659 | #: blfs-en/introduction/important/building-notes.xml:285 |
||
| 660 | msgid "" |
||
| 661 | "Again, the easiest way to demonstrate the technique is to show an example. " |
||
| 662 | "First, issue the command:" |
||
| 663 | msgstr "" |
||
| 664 | "De nouveau, la manière la plus facile de montrer la technique est de " |
||
| 665 | "présenter un exemple. Lancez d'abord la commande :" |
||
| 666 | |||
| 667 | #. type: Content of: <sect1><sect2><screen> |
||
| 668 | #: blfs-en/introduction/important/building-notes.xml:288 |
||
| 669 | #, no-wrap |
||
| 670 | msgid "<userinput>ls -l /usr/bin | more</userinput>" |
||
| 671 | msgstr "<userinput>ls -l /usr/bin | more</userinput>" |
||
| 672 | |||
| 673 | #. type: Content of: <sect1><sect2><para> |
||
| 674 | #: blfs-en/introduction/important/building-notes.xml:290 |
||
| 675 | msgid "" |
||
| 676 | "Of course, you'll be required to view the output one page at a time because " |
||
| 677 | "the <command>more</command> filter was used. Now try the same command, but " |
||
| 678 | "this time redirect the output to a file. The special file <filename>/dev/" |
||
| 679 | "null</filename> can be used instead of the filename shown, but you will have " |
||
| 680 | "no log file to examine:" |
||
| 681 | msgstr "" |
||
| 682 | "Bien entendu, vous devrez voir la sortie page par page car on a utilisé le " |
||
| 683 | "filtre <command>more</command>. Essayez maintenant la même commande, mais en " |
||
| 684 | "redirigeant cette fois la sortie vers un fichier. Le fichier spécial " |
||
| 685 | "<filename>/dev/null</filename> peut être utilisé à la place du fichier " |
||
| 686 | "indiqué, mais vous n'aurez pas de fichier journal à examiner :" |
||
| 687 | |||
| 688 | #. type: Content of: <sect1><sect2><screen> |
||
| 689 | #: blfs-en/introduction/important/building-notes.xml:296 |
||
| 690 | #, no-wrap |
||
| 691 | msgid "<userinput>ls -l /usr/bin | more > redirect_test.log 2>&1</userinput>" |
||
| 692 | msgstr "<userinput>ls -l /usr/bin | more > redirect_test.log 2>&1</userinput>" |
||
| 693 | |||
| 694 | #. type: Content of: <sect1><sect2><para> |
||
| 695 | #: blfs-en/introduction/important/building-notes.xml:298 |
||
| 696 | msgid "" |
||
| 697 | "Notice that this time the command immediately returned to the shell prompt " |
||
| 698 | "without having to page through the output. You may now remove the log file." |
||
| 699 | msgstr "" |
||
| 700 | "Remarquez que cette fois, la commande est immédiatement revenue à l'invite " |
||
| 701 | "du shell sans devoir parcourir la sortie page par page. Vous pouvez " |
||
| 702 | "supprimer maintenant le fichier journal." |
||
| 703 | |||
| 704 | #. type: Content of: <sect1><sect2><para> |
||
| 705 | #: blfs-en/introduction/important/building-notes.xml:302 |
||
| 706 | msgid "" |
||
| 707 | "The last example will use the <command>yes</command> command in combination " |
||
| 708 | "with output redirection to bypass having to page through the output and then " |
||
| 709 | "provide a <keycap>y</keycap> to a prompt. This technique could be used in " |
||
| 710 | "instances when otherwise you would have to page through the output of a file " |
||
| 711 | "(such as a license agreement) and then answer the question of <quote>do you " |
||
| 712 | "accept the above?</quote>. For this example, another short " |
||
| 713 | "<application>Bash</application> script is required:" |
||
| 714 | msgstr "" |
||
| 715 | "Le dernier exemple utilisera la commande <command>yes</command> associée à " |
||
| 716 | "la redirection de sortie pour éviter de naviguer page par page dans la " |
||
| 717 | "sortie, puis de fournir un <keycap>y</keycap> à l'invite. Cette technique " |
||
| 718 | "peut être utilisée dans les cas où vous devriez, sans elle, naviguer page " |
||
| 719 | "par page dans la sortie d'un fichier (tel qu'un accord de licence), puis " |
||
| 720 | "répondre à la question <quote>Acceptez-vous ce qui précède ?</quote>. " |
||
| 721 | "Pour cet exemple, on a besoin d'un autre petit script <application>Bash</" |
||
| 722 | "application> :" |
||
| 723 | |||
| 724 | #. type: Content of: <sect1><sect2><screen> |
||
| 725 | #: blfs-en/introduction/important/building-notes.xml:310 |
||
| 726 | #, no-wrap |
||
| 727 | msgid "" |
||
| 728 | "<userinput>cat > blfs-yes-test2 << \"EOF\"\n" |
||
| 729 | "<literal>#!/bin/bash\n" |
||
| 730 | "\n" |
||
| 731 | "ls -l /usr/bin | more\n" |
||
| 732 | "\n" |
||
| 733 | "echo -n -e \"\\n\\nDid you enjoy reading this? (y,n) \"\n" |
||
| 734 | "\n" |
||
| 735 | "read A_STRING\n" |
||
| 736 | "\n" |
||
| 737 | "if test \"$A_STRING\" = \"y\"; then A_STRING=\"You entered the 'y' key\"\n" |
||
| 738 | "else A_STRING=\"You did NOT enter the 'y' key\"\n" |
||
| 739 | "fi\n" |
||
| 740 | "\n" |
||
| 741 | "echo -e \"\\n\\n$A_STRING\\n\\n\"</literal>\n" |
||
| 742 | "EOF\n" |
||
| 743 | "chmod 755 blfs-yes-test2</userinput>" |
||
| 744 | msgstr "" |
||
| 745 | "<userinput>cat > blfs-yes-test2 << \"EOF\"\n" |
||
| 746 | "<literal>#!/bin/bash\n" |
||
| 747 | "\n" |
||
| 748 | "ls -l /usr/bin | more\n" |
||
| 749 | "\n" |
||
| 750 | "echo -n -e \"\\n\\nDid you enjoy reading this? (y,n) \"\n" |
||
| 751 | "\n" |
||
| 752 | "read A_STRING\n" |
||
| 753 | "\n" |
||
| 754 | "if test \"$A_STRING\" = \"y\"; then A_STRING=\"You entered the 'y' key\"\n" |
||
| 755 | "else A_STRING=\"You did NOT enter the 'y' key\"\n" |
||
| 756 | "fi\n" |
||
| 757 | "\n" |
||
| 758 | "echo -e \"\\n\\n$A_STRING\\n\\n\"</literal>\n" |
||
| 759 | "EOF\n" |
||
| 760 | "chmod 755 blfs-yes-test2</userinput>" |
||
| 761 | |||
| 762 | #. type: Content of: <sect1><sect2><para> |
||
| 763 | #: blfs-en/introduction/important/building-notes.xml:327 |
||
| 764 | msgid "" |
||
| 765 | "This script can be used to simulate a program that requires you to read a " |
||
| 766 | "license agreement, then respond appropriately to accept the agreement before " |
||
| 767 | "the program will install anything. First, run the script without any " |
||
| 768 | "automation techniques by issuing <command>./blfs-yes-test2</command>." |
||
| 769 | msgstr "" |
||
| 770 | "On peut utiliser ce script pour simuler un programme qui demande que vous " |
||
| 771 | "lisiez un accord de licence et que vous acceptiez le contrat avant que le " |
||
| 772 | "programme n'installe quoique ce soit. Lancez d'abord le script sans " |
||
| 773 | "techniques d'automatisation en exécutant <command>./blfs-yes-test2</command>." |
||
| 774 | |||
| 775 | #. type: Content of: <sect1><sect2><para> |
||
| 776 | #: blfs-en/introduction/important/building-notes.xml:333 |
||
| 777 | msgid "" |
||
| 778 | "Now issue the following command which uses two automation techniques, making " |
||
| 779 | "it suitable for use in an automated build script:" |
||
| 780 | msgstr "" |
||
| 781 | "Maintenant lancez la commande suivante qui utilise les techniques " |
||
| 782 | "d'automatisation, rendant l'utilisation convenable dans un script de " |
||
| 783 | "construction automatisé :" |
||
| 784 | |||
| 785 | #. type: Content of: <sect1><sect2><screen> |
||
| 786 | #: blfs-en/introduction/important/building-notes.xml:336 |
||
| 787 | #, no-wrap |
||
| 788 | msgid "<userinput>yes | ./blfs-yes-test2 > blfs-yes-test2.log 2>&1</userinput>" |
||
| 789 | msgstr "<userinput>yes | ./blfs-yes-test2 > blfs-yes-test2.log 2>&1</userinput>" |
||
| 790 | |||
| 791 | #. type: Content of: <sect1><sect2><para> |
||
| 792 | #: blfs-en/introduction/important/building-notes.xml:338 |
||
| 793 | msgid "" |
||
| 794 | "If desired, issue <command>tail blfs-yes-test2.log</command> to see the end " |
||
| 795 | "of the paged output, and confirmation that <keycap>y</keycap> was passed " |
||
| 796 | "through to the script. Once satisfied that it works as it should, you may " |
||
| 797 | "remove the script and log file." |
||
| 798 | msgstr "" |
||
| 799 | "Si vous le désirez, lancez <command>tail blfs-yes-test2.log</command> pour " |
||
| 800 | "voir la fin de la sortie paginée et la confirmation que <keycap>y</keycap> a " |
||
| 801 | "été passé au script. Une fois que cela marche comme cela devrait, vous " |
||
| 802 | "pouvez supprimer le script et le fichier journal." |
||
| 803 | |||
| 804 | #. type: Content of: <sect1><sect2><para> |
||
| 805 | #: blfs-en/introduction/important/building-notes.xml:343 |
||
| 806 | msgid "" |
||
| 807 | "Finally, keep in mind that there are many ways to automate and/or script the " |
||
| 808 | "build commands. There is not a single <quote>correct</quote> way to do it. " |
||
| 809 | "Your imagination is the only limit." |
||
| 810 | msgstr "" |
||
| 811 | "Enfin, gardez à l'esprit qu'il y a de nombreux moyens d'automatiser et/ou de " |
||
| 812 | "scripter les commandes de construction. Il n'y a pas <quote>une seule</" |
||
| 813 | "quote> manière de procéder. Votre imagination est la seule limite." |
||
| 814 | |||
| 815 | #. type: Content of: <sect1><sect2><title> |
||
| 816 | #: blfs-en/introduction/important/building-notes.xml:350 |
||
| 817 | msgid "Dependencies" |
||
| 818 | msgstr "Dépendances" |
||
| 819 | |||
| 820 | #. type: Content of: <sect1><sect2><para> |
||
| 821 | #: blfs-en/introduction/important/building-notes.xml:352 |
||
| 822 | msgid "" |
||
| 823 | "For each package described, BLFS lists the known dependencies. These are " |
||
| 824 | "listed under several headings, whose meaning is as follows:" |
||
| 825 | msgstr "" |
||
| 826 | "Pour chaque paquet décrit, BLFS liste les dépendances connues. Elles sont " |
||
| 827 | "listées sous plusieurs en-têtes, dont la signification est la suivante :" |
||
| 828 | |||
| 829 | #. type: Content of: <sect1><sect2><itemizedlist><listitem><para> |
||
| 830 | #: blfs-en/introduction/important/building-notes.xml:357 |
||
| 831 | msgid "" |
||
| 832 | "<emphasis>Required</emphasis> means that the target package cannot be " |
||
| 833 | "correctly built without the dependency having first been installed." |
||
| 834 | msgstr "" |
||
| 835 | "<emphasis>Requis</emphasis> signifie que le paquet cible ne peut pas se " |
||
| 836 | "construire correctement sans avoir d'abord installé la dépendance." |
||
| 837 | |||
| 838 | #. type: Content of: <sect1><sect2><itemizedlist><listitem><para> |
||
| 839 | #: blfs-en/introduction/important/building-notes.xml:362 |
||
| 840 | msgid "" |
||
| 841 | "<emphasis>Recommended</emphasis> means that BLFS strongly suggests this " |
||
| 842 | "package is installed first for a clean and trouble-free build, that won't " |
||
| 843 | "have issues either during the build process, or at run-time. The " |
||
| 844 | "instructions in the book assume these packages are installed. Some changes " |
||
| 845 | "or workarounds may be required if these packages are not installed." |
||
| 846 | msgstr "" |
||
| 847 | "<emphasis>Recommandées</emphasis> signifie que BLFS suggère fortement " |
||
| 848 | "d'installer préalablement ce paquet pour une construction propre et sans " |
||
| 849 | "problème, ni pendant le processus de construction ni au moment de " |
||
| 850 | "l'exécution. Les instructions dans le livre considèrent que ses paquets sont " |
||
| 851 | "installés. Des modifications ou contournements peuvent être requis si ces " |
||
| 852 | "paquets ne sont pas installés." |
||
| 853 | |||
| 854 | #. type: Content of: <sect1><sect2><itemizedlist><listitem><para> |
||
| 855 | #: blfs-en/introduction/important/building-notes.xml:370 |
||
| 856 | msgid "" |
||
| 857 | "<emphasis>Optional</emphasis> means that this package might be installed for " |
||
| 858 | "added functionality. Often BLFS will describe the dependency to explain the " |
||
| 859 | "added functionality that will result." |
||
| 860 | msgstr "" |
||
| 861 | "<emphasis>Facultatives</emphasis> signifie que ce paquet pourrait être " |
||
| 862 | "installé pour ajouter des fonctions. BLFS décrira souvent la dépendance pour " |
||
| 863 | "expliquer la fonctionnalité supplémentaire résultante." |
||
| 864 | |||
| 865 | #. type: Content of: <sect1><sect2><title> |
||
| 866 | #: blfs-en/introduction/important/building-notes.xml:379 |
||
| 867 | msgid "Using the Most Current Package Sources" |
||
| 868 | msgstr "Utilisation de paquets sources plus récents" |
||
| 869 | |||
| 870 | #. type: Content of: <sect1><sect2><para> |
||
| 871 | #: blfs-en/introduction/important/building-notes.xml:381 |
||
| 872 | msgid "" |
||
| 873 | "On occasion you may run into a situation in the book when a package will not " |
||
| 874 | "build or work properly. Though the Editors attempt to ensure that every " |
||
| 875 | "package in the book builds and works properly, sometimes a package has been " |
||
| 876 | "overlooked or was not tested with this particular version of BLFS." |
||
| 877 | msgstr "" |
||
| 878 | "Occasionnellement, dans le livre, vous pourrez être dans la situation ou un " |
||
| 879 | "paquet ne se construit pas ou ne fonctionne pas correctement. Bien que les " |
||
| 880 | "éditeurs tentent de faire en sorte que chaque paquet dans le livre se " |
||
| 881 | "construise et fonctionne correctement, parfois un paquet a été oublié ou n'a " |
||
| 882 | "pas été testé avec cette version particulière de BLFS." |
||
| 883 | |||
| 884 | #. type: Content of: <sect1><sect2><para> |
||
| 885 | #: blfs-en/introduction/important/building-notes.xml:387 |
||
| 886 | msgid "" |
||
| 887 | "If you discover that a package will not build or work properly, you should " |
||
| 888 | "see if there is a more current version of the package. Typically this means " |
||
| 889 | "you go to the maintainer's web site and download the most current tarball " |
||
| 890 | "and attempt to build the package. If you cannot determine the maintainer's " |
||
| 891 | "web site by looking at the download URLs, use Google and query the package's " |
||
| 892 | "name. For example, in the Google search bar type: 'package_name " |
||
| 893 | "download' (omit the quotes) or something similar. Sometimes typing: " |
||
| 894 | "'package_name home page' will result in you finding the maintainer's web " |
||
| 895 | "site." |
||
| 896 | msgstr "" |
||
| 897 | "Si vous découvrez un paquet qui ne se construit pas ou ne fonctionne pas " |
||
| 898 | "correctement, vous pouvez regarder s'il s'agit de la version la plus récente " |
||
| 899 | "du paquet. Typiquement, cela signifie que vous irez sur le site web du " |
||
| 900 | "mainteneur et téléchargerez l'archive la plus récente et tenterez de " |
||
| 901 | "construire le paquet. Si vous ne pouvez pas déterminer le site web du " |
||
| 902 | "mainteneur en regardant l'URL de chargement, utilisez Google et cherchez le " |
||
| 903 | "nom du paquet. Par exemple, dans la barre de recherche de Google tapez: " |
||
| 904 | "'nom_du_paquet download' (sans les guillemets) ou quelque chose de " |
||
| 905 | "similaire. Parfois en tapant : 'nom_du_paquet home page' vous trouverez " |
||
| 906 | "le site web du mainteneur." |
||
| 907 | |||
| 908 | #. type: Content of: <sect1><sect2><title> |
||
| 909 | #: blfs-en/introduction/important/building-notes.xml:400 |
||
| 910 | msgid "Stripping One More Time" |
||
| 911 | msgstr "Nettoyage une fois de plus" |
||
| 912 | |||
| 913 | #. type: Content of: <sect1><sect2><para> |
||
| 914 | #: blfs-en/introduction/important/building-notes.xml:402 |
||
| 915 | msgid "" |
||
| 916 | "In LFS, stripping of debugging symbols was discussed a couple of times. " |
||
| 917 | "When building BLFS packages, there are generally no special instructions " |
||
| 918 | "that discuss stripping again. It is probably not a good idea to strip an " |
||
| 919 | "executable or a library while it is in use, so exiting any windowing " |
||
| 920 | "environment is a good idea. Then you can do:" |
||
| 921 | msgstr "" |
||
| 922 | "Dans LFS, le nettoyage des symboles de déboguage a été discuté de nombreuses " |
||
| 923 | "fois. Pour la construction des paquets BLFS, il n'y a généralement pas " |
||
| 924 | "d'instructions qui discute de nouveau du nettoyage. Ce n'est probablement " |
||
| 925 | "pas une bonne idée de nettoyer un exécutable ou une bibliothèque tant qu'ils " |
||
| 926 | "sont utilisés, alors sortir des environnements de fenêtrage est une bonne " |
||
| 927 | "idée. Ensuite vous pouvez faire :" |
||
| 928 | |||
| 929 | #. type: Content of: <sect1><sect2><screen> |
||
| 930 | #: blfs-en/introduction/important/building-notes.xml:408 |
||
| 931 | #, no-wrap |
||
| 932 | msgid "<userinput>find /{,usr/}{bin,lib,sbin} -type f -exec strip --strip-unneeded {} \\;</userinput>" |
||
| 933 | msgstr "<userinput>find /{,usr/}{bin,lib,sbin} -type f -exec strip --strip-unneeded {} \\;</userinput>" |
||
| 934 | |||
| 935 | #. type: Content of: <sect1><sect2><para> |
||
| 936 | #: blfs-en/introduction/important/building-notes.xml:410 |
||
| 937 | msgid "" |
||
| 938 | "If you install programs in other directories such as /opt or /usr/local, you " |
||
| 939 | "may want to strip the files there too." |
||
| 940 | msgstr "" |
||
| 941 | "Si vous installez des programmes dans d'autres répertoires tels que /opt ou /" |
||
| 942 | "usr/local, vous pouvez vouloir nettoyer les fichiers ici aussi." |
||
| 943 | |||
| 944 | #. type: Content of: <sect1><sect2><para> |
||
| 945 | #: blfs-en/introduction/important/building-notes.xml:413 |
||
| 946 | msgid "" |
||
| 947 | "For more information on stripping, see <ulink url=\"http://www.technovelty." |
||
| 948 | "org/linux/stripping-shared-libraries.html\"/>." |
||
| 949 | msgstr "" |
||
| 950 | "Pour plus d'information sur le nettoyage, regardez <ulink url=\"http://www." |
||
| 951 | "technovelty.org/linux/stripping-shared-libraries.html\"/>." |
||
| 952 | |||
| 953 | #. type: Content of: <sect1><sect2><title> |
||
| 954 | #: blfs-en/introduction/important/building-notes.xml:419 |
||
| 955 | msgid "Libtool files" |
||
| 956 | msgstr "Fichiers Libtool" |
||
| 957 | |||
| 958 | #. type: Content of: <sect1><sect2><para> |
||
| 959 | #: blfs-en/introduction/important/building-notes.xml:421 |
||
| 960 | msgid "" |
||
| 961 | "One of the side effects of packages that use Autotools, including libtool, " |
||
| 962 | "is that they create many files with an .la extension. These files are not " |
||
| 963 | "needed in an LFS environment. If there are conflicts with pkgconfig " |
||
| 964 | "entries, they can actually prevent successful builds. You may want to " |
||
| 965 | "consider removing these files periodically:" |
||
| 966 | msgstr "" |
||
| 967 | "Un des effets de bord des paquets qui utilisent Autotools, incluant libtool, " |
||
| 968 | "est qu'ils créent beaucoup de fichiers avec une extension .la. Ces fichiers " |
||
| 969 | "ne sont pas utiles dans un environnement LFS. S'il y a des conflits avec des " |
||
| 970 | "entrées pkconfig, ils peuvent même empêcher des constructions correctes. " |
||
| 971 | "Vous pouvez songer à effacer ces fichiers périodiquement :" |
||
| 972 | |||
| 973 | #. type: Content of: <sect1><sect2><screen> |
||
| 974 | #: blfs-en/introduction/important/building-notes.xml:427 |
||
| 975 | #, no-wrap |
||
| 976 | msgid "<userinput>find /lib /usr/lib -not -path \"*Image*\" -a -name \\*.la -delete</userinput>" |
||
| 977 | msgstr "<userinput>find /lib /usr/lib -not -path \"*Image*\" -a -name \\*.la -delete</userinput>" |
||
| 978 | |||
| 979 | #. type: Content of: <sect1><sect2><para> |
||
| 980 | #: blfs-en/introduction/important/building-notes.xml:429 |
||
| 981 | msgid "" |
||
| 982 | "The above command removes all .la files with the exception of those that " |
||
| 983 | "have \"Image\" as a part of the path. These .la files are used by the " |
||
| 984 | "ImageMagick programs. There may be other exceptions by packages not in BLFS." |
||
| 985 | msgstr "" |
||
| 986 | "La commande suivante efface tous les fichiers .la sauf ceux ayant « " |
||
| 987 | "Image » dans une partie de leur chemin. Ces fichiers .la sont utilisés " |
||
| 988 | "par les programmes de ImageMagick. Il peut y avoir d'autres exceptions avec " |
||
| 989 | "des paquets qui ne sont pas dans BLFS." |