Host/Target specific installation notes for GCC

Please read this document carefully before installing the GNU Compiler Collection on your machine.

´ç½ÅÀÇ ÄÄÇ»ÅÍ¿¡ GNU Compiler¸¦ ¼³Ä¡Çϱâ Àü¿¡ ÀÌ ¹®¼­¸¦ ÁÖÀDZí°Ô ÀоîÁֱ⠹ٶõ´Ù.


alpha*-dec-linux*

We strongly recommend to upgrade to binutils 2.10 (or newer).

¿ì¸®´Â binutils 2.10 ¶Ç´Â ±× ÀÌ»óÀÇ ¹öÀüÀ¸·Î ¾÷±×·¹À̵å Çϱ⸦ °­·ÂÈ÷ ±ÇÀåÇÑ´Ù.

The following error:

  Error: macro requires $at register while noat in effect

´ÙÀ½°ú °°Àº ¿¡·¯´Â:

  
  Error: macro requires $at register while noat in effect

indicates that you should upgrade to a newer version of the assembler, 2.9 or later. If you can not upgrade the assembler, the compiler option "-Wa,-m21164a" may work around this problem.

¹öÀü 2.9³ª ±× ÀÌ»óÀÇ ¹öÀüÀ¸·Î ¾î¼Àºí·¯ ¹öÀüÀ» ¾÷±×·¹À̵å ÇؾßÇÔÀ» ³ªÅ¸³½´Ù. ¸¸¾à ´ç½ÅÀÌ ¾î¼Àºí·¯¸¦ ¾÷±×·¹À̵å ÇÒ¼ö ¾ø´Ù¸é "-Wa,-m21164a"À̶ó°í ¿É¼ÇÀ» Á־ ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö ÀÖ´Ù.


alpha*-dec-osf*

If you install a shared libstdc++ and, when you link a non-trivial C++ program (for example, gcc/testsuite/g++.other/delete3.C), the linker reports a couple of errors about multiply-defined symbols (for example, nothrow, __throw and terminate(void)), you've probably got a linker bug, for which there's no known fix. The officially recommended work-around is to remove the shared libstdc++.

¸¸¾à ´ç½ÅÀÌ °øÀ¯µÈ(shared) libstdc++¸¦ ¼³Ä¡Çϱ⸦ ¿øÇÏ°í , Æò¹üÇÏÁö ¾ÊÀº(non-trivial) C++ ÇÁ·Î±×·¥À» ¸µÅ©ÇÑ´Ù°í ÇÒ¶§, (¿¹¸¦ µé¸é, gcc/testsuite/g++.other/delete3.C), ´ÙÁßÀ¸·Î Á¤ÀÇµÈ ½Éº¼(¿¹¸¦µé¸é, nothrow, __throw and terminate(void))¿¡ °üÇÑ ¸î¸îÀÇ ¿¡·¯¸¦ ¸µÄ¿°¡ º¸°íÇÒ °ÍÀÌ´Ù. À̸¦ °íÄ¡´Â ¾Ë·ÁÁø ¹æ¹ýÀÌ ¾ø±â ¶§¹®¿¡, ´ç½ÅÀº ¾Æ¸¶µÎ ¸µÄ¿ ¹ö±×¸¦ °¡Áö°Ô µÉ °ÍÀÌ´Ù. °ø½ÄÀûÀ¸·Î Á¦¾ÈµÈ ¹®Á¦ÇØ°á¹æ¹ýÀº °øÀ¯µÈ(shared) libstdc++¸¦ Á¦°ÅÇÏ´Â °ÍÀÌ´Ù.

An alternative solution is to arrange that all symbols from libgcc get copied to the shared libstdc++; see detailed solution below. (Surprising as it may seem, this does indeed fix the problem!) Beware that this may bring you binary-compatibility problems in the future, if you don't use the same work-around next time you build libstdc++: if programs start to depend on libstdc++ to provide symbols that used to be only in libgcc, you must arrange that libstdc++ keeps providing them, otherwise the programs will have to be relinked.

¶Ç ´Ù¸¥ ÇØ°áÃ¥Àº libgccÀÇ ¸ðµç ½Éº¼À» °øÀ¯µÈ libstdc++¿¡¼­ Ä«ÇÇÇؼ­ ¼öÁ¤ÇÏ´Â °ÍÀÌ´Ù. ÀÚ¼¼ÇÑ ÇØ°á¹æ¹ýÀ» ¾Æ·¡¸¦ Âü°íÇضó.(³î¶ó¿ó°Ôµµ º¸¸é, ÀÌ°ÍÀº ½ÇÁ¦·Î ¹®Á¦¸¦ ÇØ°áÇÑ´Ù.) ¸¸¾à ´ç½ÅÀÌ libstdc++¸¦ ÄÄÆÄÀÏ(build)ÇÏ´Â ´ÙÀ½¹ø¿¡ °°Àº ¹æ¹ýÀ¸·Î ÇÏÁö ¾ÊÀ¸¸é °¡±î¿î ¹Ì·¡¿¡ ¹ÙÀ̳ʸ®-ȣȯ¼º(binary-compatibility)¹®Á¦¸¦ ¾ß±âÇÒ °ÍÀÌ´Ù : ¸¸¾à ÇÁ·Î±×·¥ÀÌ ´ÜÁö libgcc¾È¿¡¼­ »ç¿ëµÇ´Â ½Éº¼µéÀ» Á¦°øÇϱâ À§Çؼ­ libstdc++¿¡ ÀÇÁöÇؼ­ ½ÃÀ۵Ǿî Áø´Ù¸é, ´ç½ÅÀº libstdc++°¡ °è¼ÓÀûÀ¸·Î ±×°ÍµéÀ» Á¦°øÇϵµ·Ï ¼öÁ¤ÇؾßÇϸç, »Ó¸¸¾Æ´Ï¶ó ÇÁ·Î±×·¥À» À縵ũ½ÃÄѾ߸¸ ÇÑ´Ù.

The magic spell is to add -Wl,-all,-lgcc,-none to the definition of macro SHDEPS in libstdc++/config/dec-osf.ml before alpha*-dec-osf*/libstdc++/Makefile is created (a patch that does just that is available). If the Makefile already exists, run ./config.status within directory alpha*-dec-osf*/libstdc++ (and alpha*-dec-osf*/ieee/libstdc++, if it also exists). Remove any existing libstdc++.so* from such directories, and run make all-target-libstdc++ in the top-level directory, then make install-target-libstdc++.

alpha*-dec-osf*/libstdc++/MakefileÀÌ ¸¸µé¾îÁö±â Àü¿¡ (¸· »ç¿ë°¡´ÉÇÑ patch ) libstdc++/config/dec-osf.ml¿¡¼­ ¸ÅÅ©·Î SHDEPSÀ» Á¤ÀÇÇϱâ À§Çؼ­ -Wl,-all,-lgcc,-none¸¦ Ãß°¡½ÃÅ°´Â °ÍÀº ¸¶¼ú°°Àº ÇØ°áÃ¥ÀÌ´Ù. ¸¸¾à MakefileÀÌ ÀÌ¹Ì Á¸ÀçÇÑ´Ù¸é, alpha*-dec-osf*/libstdc++µð·ºÅ丮¿¡¼­ (±×¸®°í alpha*-dec-osf*/ieee/libstdc++ÀÌ ¶ÇÇÑ Á¸ÀçÇÑ´Ù¸é) ./config.statusÀ» ½ÇÇàÇÑ´Ù. ±×·¯ÇÑ µð·ºÅ丮µé¿¡ Á¸ÀçÇÏ´Â ¾î¶² libstdc++.so*µµ Á¦°ÅÇ϶ó. ±×¸®°í ž-·¹º§ µð·ºÅ丮¿¡¼­ make all-target-libstdc++¸¦ ½ÇÇàÇÏ°í ÀÌÈÄ¿¡ make install-target-libstdc++¶ó°í ½ÇÇàÇÑ´Ù.

If you have already removed the build tree, you may just remove libstdc++.so.2.10.0 from the install tree and re-create it with the command gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm. If the ieee sub-directory exists, repeat this command in it, with the additional flag -mieee.

¸¸¾à ´ç½ÅÀÌ ÀÌ¹Ì ÄÄÆÄÀÏ(build) Æ®¸®¸¦ Á¦°ÅÇÏ¿´´Ù¸é, ´ç½ÅÀº libstdc++.so.2.10.0¸¦ Á¦°ÅÇؾßÇϸç, gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm¶ó´Â ¸í·É°ú ÇÔ²² ±× Æ®¸®¸¦ ´Ù½Ã ¼³Ä¡ÇÏ°í ´Ù½Ã ¸¸µé¾î¾ß ÇÒ °ÍÀÌ´Ù.ieee ¼­ºê µð·ºÅ丮°¡ Á¸ÀçÇÑ´Ù¸é, ±× ¾È¿¡¼­ -mieee¶ó´Â Ãß°¡ÀûÀÎ Ç÷¡±×¿Í ÇÔ²² À§¿Í °°Àº ¸í·ÉÀ» ³»·Á¶ó.


DOS

Please have a look at our binaries page.

¿ì¸®ÀÇ binaries page(¹ÙÀ̳ʸ® ÆäÀÌÁö)¸¦ º¸¼¼¿ä.


hppa*-hp-hpux*

We highly recommend using gas/binutils-2.8 or newer on all hppa platforms; you may encounter a variety of problems when using the HP assembler.

¿ì¸®´Â ¸ðµç hppa Ç÷§Æû¿¡¼­ gas/binutils-2.8À̳ª ±× ÀÌ»óÀÇ ¹öÀüÀ» ¾²±â¸¦ °­·ÂÈ÷ Á¦¾ÈÇÑ´Ù; ´ç½ÅÀº HP ¾î¼Àºí·¯¸¦ »ç¿ëÇÒ¶§, ´Ù¾çÇÑ ¹®Á¦¸¦ ¸¸³¯ ¼ö ÀÖ´Ù.

If you wish to use pa-risc 2.0 architecture support, you must use either the HP assembler or a recent snapshot of gas.

¸¸¾à ´ç½ÅÀÌ pa-risc 2.0 ¾ÆÅ°ÅØÃÄ Áö¿øÀ» »ç¿ëÇÏ°í ½Í´Ù¸é, ´ç½ÅÀº HP ¾î¼Àºí·¯³ª ¶Ç´Â ÃÖ±ÙÀÇ gasÀÇ ½º³À¼¦À» »ç¿ëÇؾ߸¸ ÇÑ´Ù.

More specific information to hppa*-hp-hpux* targets follows.

´õ ÀÚ¼¼ÇÑ »çÇ×Àº hppa*-hp-hpux* Ÿ°Ù ¸Ó½ÅÀ» Âü°íÇϼ¼¿ä.


hppa*-hp-hpux9

The HP assembler has major problems on this platform. We've tried to work around the worst of the problems. However, those workarounds may be causing linker crashes in some circumstances; the workarounds also probably prevent shared libraries from working. Use the GNU assembler to avoid these problems.

HP ¾î¼Àºí·¯´Â ÀÌ Ç÷§Æû¿¡¼­ Å« ¹®Á¦¸¦ °¡Áö°í ÀÖ´Ù. ¿ì¸®´Â ÀÌ ¹®Á¦µéÀ» ÃÖ¼ÒÈ­Çϱâ À§ÇØ ³ë·ÂÇØ¿Ô´Ù. ±×·¯³ª, ÀÌ·¯ÇÑ ³ë·ÂµéÀº ¸î¸îÀÇ È¯°æ¿¡¼­ ¸µÄ¿ ±úÁü(linker crashes) Çö»óµéÀ» ¾ß±â½ÃŲ´Ù; ÀÌ·¯ÇÑ ³ë·ÂÀº ¶ÇÇÑ ÀÛ¾÷À¸·ÎºÎÅÍ °øÀ¯ ¶óÀ̺귯¸®¸¦ ¸·´Â´Ù. ÀÌ·¯ÇÑ ¹®Á¦¸¦ ÇÇÇϱâ À§Çؼ­ GNU ¾î¼Àºí·¯¸¦ »ç¿ëÇ϶ó..

The configuration scripts for GCC will also trigger a bug in the hpux9 shell. To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to /bin/ksh in your environment.

GCC¸¦ À§ÇÑ ¼³Á¤ ½ºÅ©¸³Æ®´Â hpux9 ½©¿¡¼­ ¹ö±×¸¦ ¹ß»ý½ÃŲ´Ù. ÀÌ·¯ÇÑ ¹®Á¦¸¦ ÇÇÇϱâ À§Çؼ­ ´ç½ÅÀÇ È¯°æ¿¡¼­ CONFIG_SHELLÀ» /bin/ksh·Î SHELL¸¦ /bin/ksh·Î ¼³Á¤ÇؾßÇÑ´Ù.


hppa*-hp-hpux10

For hpux10.20, we highly recommend you pick up the latest sed patch PHCO_19798 from HP. HP has two sites which provide patches free of charge:

hpux10.20¸¦ À§Çؼ­, ¿ì¸®´Â HP·ÎºÎÅÍ °¡Àå ÃÖ±ÙÀÇ sed patch, PHCO_19798¸¦ °¡Á®¿À±â¸¦ °­·ÂÈ÷ ±ÇÀåÇÑ´Ù. HP´Â ¹«·áÀÇ ÆÐÄ¡¸¦ µÎ°³ÀÇ »çÀÌÆ®¿¡¼­ Á¦°øÇÑ´Ù:

The HP assembler on these systems is much better than the hpux9 assembler, but still has some problems. Most notably the assembler inserts timestamps into each object file it creates, causing the 3-stage comparison test to fail during a `make bootstrap'. You should be able to continue by saying `make all' after getting the failure from `make bootstrap'.

ÀÌ·¯ÇÑ ½Ã½ºÅÛ¿¡¼­ÀÇ HP ¾î¼Àºí·¯´Â hpux9 ¿¡¼Àºí·¯º¸´Ù ÈξÀ ³´´Ù. ±×·¯³ª ¸î¸î ¹®Á¦Á¡À» °¡Áø´Ù. ±×Áß¿¡ °¡Àå µÎµå·¯Áø °ÍÀº ±×°ÍÀÌ ¸¸µç °¢°¢ÀÇ ¿ÀºêÁ§Æ® È­ÀϾȿ¡ ŸÀÓ½ºÅÛÇÁ¸¦ »ðÀÔÇÑ´Ù´Â °ÍÀÌ´Ù. ÀÌ°ÍÀº `make bootstrap'½Ã¿¡ 3´Ü°è ºñ±³Å×½ºÆ®(the 3-stage comparison test)°¡ ½ÇÆÐÇϵµ·Ï ¸¸µç´Ù. ´ç½ÅÀº `make bootstrap'·Î ºÎÅÍ ½ÇÆи¦ ¾òÀº ÈÄ¿¡ `make all'¶ó°í ÇÔÀ¸·Î½á °è¼ÓÁøÇàÇØ¾ß ÇÑ´Ù.


hppa*-hp-hpux11

GCC 2.95.2 does not support HP-UX 11, and it cannot generate 64-bit object files. Current (as of late 2000) snapshots and GCC 3.0 do support HP-UX 11.

GCC 2.95.2´Â HP-UX 11¸¦ Áö¿øÇÏÁö ¾Ê´Â´Ù. ±×¸®°í, ±×°ÍÀº 64-bit¿ÀºêÁ§Æ® È­ÀÏÀ» ¸¸µéÁö ¸øÇÑ´Ù. ÇöÀçÀÇ ½º³À¼¦(2000³â ¸»)°ú GCC 3.0Àº HP-UX 11¸¦ Áö¿øÇÑ´Ù.


*-*-linux-gnu

If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install out-of-the-box. You'll get compile errors while building libstdc++. The patch glibc-2.2.patch, that is to be applied in the GCC source tree, fixes the compatibility problems.

¸¸¾à ´ç½ÅÀÌ glibc 2.2 (or 2.1.9x)¸¦ »ç¿ëÇÑ´Ù¸é, GCC 2.95.2´Â out-of-the-box¸¦ ¼³Ä¡ÇÒ ¼ö ¾øÀ» °ÍÀÌ´Ù. ´ç½ÅÀº libstdc++¸¦ ÄÄÆÄÀÏ(build)ÇÏ´Â °úÁ¤¿¡¼­ ¿¡·¯µéÀ» ¾ò°Ô µÉ °ÍÀÌ´Ù. ÆÐÄ¡ glibc-2.2.patch¸¦ GCC ¼Ò½º Æ®¸®¿¡ Àû¿ë½ÃÅ°¸é, ȣȯ¼º¹®Á¦´Â ¾ø¾îÁú °ÍÀÌ´Ù.


i?86-*-linux*

You will need binutils-2.9.1.0.15 or newer for exception handling to work.

´ç½ÅÀº ÀÛ¾÷¿¡¼­ ¿¹¿Ü 󸮸¦ Çϱâ À§Çؼ­ binutils-2.9.1.0.15À̳ª ±× ÀÌ»ó¹öÀüÀÌ ÇÊ¿äÇÒ °ÍÀÌ´Ù.

If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on www.bitwizard.nl.

GNU/Linux¿¡¼­ ÄÄÆÄÀÏ(build)ÇÏ°í ÀÖ´ÂÁß¿¡ ½Ã±×³Î 11 ¿¡·¯¸¦ ¹Þ´Â´Ù¸é, ±×°ÍÀº Çϵå¿þ¾î ¹®Á¦¸¦ °¡Áö°í ÀÖÀ½À» À̾߱âÇÑ´Ù. ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â http://www.bitwizard.nl/sig11/¿¡¼­ ¾òÀ» ¼ö ÀÖ´Ù


i?86-*-sco3.2v5*

If you are building languages other than C, you must follow the instructions about invoking `make bootstrap' because the native OpenServer compiler will build a cc1plus that will not correctly parse many valid C++ programs including those in libgcc.a. You must do a `make bootstrap' if you are building with the native compiler.

¸¸¾à ´ç½ÅÀÌ Cº¸´Ù ³ªÀº ¾ð¾î¸¦ ¸¸µå´Â ÁßÀ̶ó¸é, ¿ø·¡ÀÇ ¿ÀǼ­¹ö ÄÄÆÄÀÏ·¯°¡ libgcc.a¿¡¼­ ±×°ÍµéÀ» Æ÷ÇÔÇÑ ¸Å¿ì ´Ù¾çÇÑ C++ÇÁ·Î±×·¥µéÀ» ¿Ç°Ô ÆĽÌÇÏÁö ¸øÇÏ´Â cc1plus¸¦ ¸¸µé °ÍÀ̱⠶§¹®¿¡ ´ç½ÅÀº `make bootstrap'¸¦ È£ÃâÇÏ´Â °Í¿¡ °üÇؼ­ ÀνºÆ®·°¼ÇµéÀ» µû¶ó¾ßÇÑ´Ù. ¸¸¾à ´ç½ÅÀÌ ³×ÀÌƼºê ÄÄÆÄÀÏ·¯¿Í ÇÔ²² ¸¸µå´Â ÁßÀ̶ó¸é `make bootstrap'¸¦ ²À »ç¿ëÇØ¾ß ÇÑ´Ù.

Use of the `-march-pentiumpro' flag can result in unrecognized opcodes when using the native assembler. While it's rather rare to see these emitted by GCC yet, errors of the basic form:

  /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
  /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip

`-march-pentiumpro' Ç÷¡±×ÀÇ »ç¿ëÀº ³×ÀÌƼºê ¾î¼Àºí·¯¸¦ »ç¿ëÇÒ ¶§ ÀνĵÇÁö ¾Ê´Â opcodeµé·Î °á°ú¸¦ ³¾¼ö ÀÖ´Ù. GCC¿¡ ÀÇÇØ »ý·«µÈ ÀÌ·¯ÇÑ °ÍµéÀ» º¸´Â °ÍÀº °ÅÀÇ ½¬¿î ÀÏÀÌ ¾Æ´ÏÁö¸¸, ±âº» ¿¡·¯ÀÇ ÆûÀº ´ÙÀ½°ú °°´Ù:

 
 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip

are symptoms of this problem. You may work around this by not building affected files with that flag or by using the GNU assembler. Users of GNU assembler should see the note below for hazards on doing so.

Àº ÀÌ·¯ÇÑ ¹®Á¦ÀÇ Áõ»óÀÌ´Ù. GNU ¾î¼Àºí·¯¸¦ »ç¿ëÇÔÀ¸·Î½á ¶Ç´Â ÀÌ·¯ÇÑ Ç÷¡±×¿Í ÇÔ²² ¿µÇâÀ» ¹Þ´Â ÆÄÀϵéÀ» ÄÄÆÄÀÏ(build)ÇÏÁö ¾ÊÀ½À¸·¯½á ´ç½ÅÀº ÀÌ ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö ÀÖ´Ù. GNU ¾î¼Àºí·¯ À¯ÀúµéÀº ÀÌ·¯ÇÑ À§ÇèÀ» À§Çؼ­ ¾Æ·¡¿Í °°Àº ÁÖÀǸ¦ º¸¾Æ¾ß ÇÑ´Ù.

If you choose to configure with --enable-shared you should also specify --with-gnu-as --disable-multilib even if you are not using the GNU assembler. In doing so you will give up the ability to generate COFF executables as described below. This combination of flags is necessary to suppress negative interactions with multilibing.

¸¸¾à ´ç½ÅÀÌ --enable-shared¿Í ÇÔ²² ȯ°æ¼³Á¤(configuration)À» ÇÑÇϸé, ´ç½ÅÀº ºñ·Ï GNU ¾î¼Àºí·¯¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù ÇÒÁö¶óµµ --with-gnu-as --disable-multilib¸¦ ½áÁÖ¾î¾ß ÇÑ´Ù. ±×·¸°Ô ÇÔÀ¸·Î½á ¾Æ·¡¿¡ ±â¼úµÈ ´ë·Î ½ÇÇàµÇ´Â COFF¸¦ ¸¸µé ¼ö ÀÖ´Â ´É·ÂÀ» Æ÷±âÇÏ°Ô µÉ °ÍÀÌ´Ù. ÀÌ·¯ÇÑ Ç÷¡±×ÀÇ Á¶È­´Â ´ÙÁß ¹ÙÀεùÀ¸·Î ÀÎÇÑ ºÎÁ¤ÀûÀÎ »óÈ£ÀÛ¿ëÀ» ¾ïÁ¦Çϱâ À§Çؼ­ ÇÊ¿äÇÏ´Ù

The native SCO assembler that is provided with the OS at no charge is normally required. If, however, you must be able to use the GNU assembler you may configure this package using the flags --with-gnu-as. You must use a recent version of GNU binutils; version 2.9.1 seems to work well. If you select this option, you will be unable to reliably build COFF images. In general, the --with-gnu-as option isn't as well tested as the native assembler.

OSÇÔ°Ô ¹«·á·Î Á¦°øµÇ´Â ³×ÀÌƼºê SCO¾î¼Àºí·¯´Â º¸Åë ÇÊ¿äÇÏ´Ù. ±×·¯³ª ¸¸¾à ´ç½ÅÀÌ GNU ¾î¼Àºí·¯¸¦ »ç¿ëÇÒ ¼ö ÀÖ¾î¾ß¸¸ ÇÑ´Ù¸é, --with-gnu-as Ç÷¡±×¸¦ »ç¿ëÇÔÀ¸·Î½á ÀÌ ÆÐÅ°Áö¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ´ç½ÅÀº GNU binutilsÀÇ °¡Àå ÃֽŠ¹öÀüÀ» »ç¿ëÇؾ߸¸ ÇÑ´Ù; ¹öÀü 2.9.1¿¡¼­ Àß ÀÛµ¿ÇÑ´Ù. ¸¸¾à ´ç½ÅÀÌ ÀÌ ¿É¼ÇÀ» »ç¿ëÇÑ´Ù¸é, ´ç½ÅÀº ¹ÏÀ» ¼ö ÀÖ°Ô COFF À̹ÌÁö¸¦ ¸¸µé ¼ö ¾øÀ» °ÍÀÌ´Ù. ÀϹÝÀûÀ¸·Î, --with-gnu-as ¿É¼ÇÀº ³×ÀÌƼºê ¾î¼Àºí·¯·Î½á Å×½ºÆ® µÇ¾îÁú ¼ö ¾ø´Ù.

Unlike various prereleases of GCC that used -belf and defaulted to COFF, you must now use the -melf and -mcoff flags to toggle between the two object file formats. ELF is now the default.

»ç¿ëµÇ´Â -belf°ú COFF¸¦ µðÆúÆ®·Î »ç¿ëÇÏ´Â ¹Ì·¡ÀÇ ¹öÀüÀÇ GCC¿Í´Â ´Ù¸£°Ô, ¿ì¸®´Â µÎ°³ÀÇ ¿ÀÇÁÁ§Æ® ÆÄÀÏ Æ÷¸Ë »çÀ̸¦ ¸Å¾îÁÖ±â(toggle) À§Çؼ­´Â ÇöÀç -melf Ç÷¡±×¿Í -mcoff Ç÷¡±×¸¦ »ç¿ëÇؾßÇÑ´Ù. ELF´Â µðÆúÆ®ÀÌ´Ù

Look in gcc/config/i386/sco5.h (search for "messy") for additional OpenServer-specific flags.

Ãß°¡ÀûÀÎ OpenServer-specific Ç÷¡±×¸¦ À§Çؼ­ gcc/config/i386/sco5.h ("messy" ã¾Æº¸±â) ¸¦ »ìÆ캸±â ¹Ù¶õ´Ù.

Systems based on OpenServer before 5.0.4 (`uname -X' will tell you what you're running) require TLS597 from ftp.sco.com/TLS for C++ constructors and destructors to work right.

Systems based on OpenServer before 5.0.4 ¹öÀü(`uname -X' ´Â ´ç½Å¿¡°Ô ¹«¾ùÀÌ µ¹¾Æ°¡°í ÀÖ´ÂÁö ¸»ÇØÁÙ°ÍÀÌ´Ù)ÀÌÀüÀÇ OpenServer¸¦ ±â¹ÝÀ¸·ÎÇÑ ½Ã½ºÅÛÀº ¿Ã¹Ù¸£°Ô ¿òÁ÷ÀÌ´Â C++ ÄÁ½ºÆ®·°ÅÍ¿Í µðÄÁ½ºÆ®·°Å͸¦ À§Çؼ­ ftp.sco.com/TLS¿¡ ÀÖ´Â TLS597À» ÇÊ¿ä·Î ÇÑ´Ù.

The system linker in (at least) 5.0.4 and 5.0.5 will sometimes do the wrong thing for a construct that GCC will emit for PIC code. This can be seen as execution testsuite failures when using -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c. For 5.0.5, an updated linker that will cure this problem is available. You must install both ftp://ftp.sco.com/Supplements/rs505a/ and OSS499A.

¹öÀü 5.0.4¿Í 5.0.5¿¡ ÀÖ´Â ½Ã½ºÅÛ ¸µÄ¿´Â GCC°¡ PIC code¸¦ À§ÇØ ¸¸µå´Â ÄÁ½ºÆ®·°Æ® ºÎºÐ¿¡¼­ ¶§¶§·Î ÀÌ»óÇÏ°Ô ÀÛµ¿ÇÏ´Â °ÍÀ» º¼ ¼ö ÀÖ´Ù. ÀÌ°ÍÀº 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.cÀ§¿¡¼­ -fPICÀ» »ç¿ëÇÒ ¶§ ½ÇÇà Å×½ºÆ®½´Æ® ½ÇÆÐ·Î½á º¸¿©Áú ¼ö ÀÖ´Ù. 5.0.5¿¡ À־, ÀÌ·¯ÇÑ ¹®Á¦¸¦ °íÄ£ °ÍÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. ´ç½ÅÀº ftp://ftp.sco.com/Supplements/rs505a/ °ú OSS499A¿¡¼­ ¹Þ¾Æ ÀÌ°ÍÀ» ¼³Ä¡ÇؾßÇÑ´Ù.

The dynamic linker in OpenServer 5.0.5 (earlier versions may show the same problem) aborts on certain g77-compiled programs. It's particularly likely to be triggered by building Fortran code with the -fPIC flag. Although it's conceivable that the error could be triggered by other code, only G77-compiled code has been observed to cause this abort. If you are getting core dumps immediately upon execution of your g77 program - and especially if it's compiled with -fPIC - try applying `sco_osr5_g77.patch' to your libf2c and rebuilding GCC. Affected faults, when analyzed in a debugger, will show a stack backtrace with a fault occurring in rtld() and the program running as /usr/lib/ld.so.1. This problem has been reported to SCO engineering and will hopefully be addressed in later releases.

OpenServer 5.0.5(ÀÌÀü¹öÀü¿¡¼­´Â °°Àº ¹®Á¦¸¦ º¼ ¼ö ÀÖÀ» °ÍÀÌ´Ù)¿¡¼­ µ¿Àû ¸µÄ¿´Â ¾î¶² g77¿¡¼­ ÄÄÆÄÀÏµÈ ÇÁ·Î±×·¥¿¡¼­ ½ÇÆÐÇß´Ù. ±×°ÍÀº Ưº°È÷ -fPIC Ç÷¡±×¿Í ÇÔ²² »ç¿ëµÇ´Â Fortran Äڵ带 ÄÄÆÄÀÏ(build)ÇÔÀ¸·Î ¾ß±âµÇ±â ½±´Ù. ºñ·Ï ´Ù¸¥ ÄÚµå·ÎÀÎÇØ ¿¡·¯°¡ ¾ß±âµÇ´Â °ÍÀ¸·Î »ý°¢ÇÒ ¼ö ÀÖÁö¸¸, ¿ÀÁ÷ G77¿¡¼­ ÄÄÆÄÀÏµÈ Äڵ忡¼­ ÀÌ·¯ÇÑ ½ÇÆи¦ °¡Á®¿À´Â °ÍÀ» °üÂûÇÒ ¼ö ÀÖ¾ú´Ù. ¸¸¾à ´ç½ÅÀÌ g77 ÇÁ·Î±×·¥ÀÇ ½ÇÇàÀ§¿¡ Áï½Ã ÄÚ¾î ´ýÇÁ¸¦ ¾ò°Ô µÈ´Ù¸é, ±×¸®°í Ưº°ÇÏ°Ô ±×°ÍÀÌ -fPIC - try°ú ÇÔ²² libf2c¿Í GCCÀÇ ÀçÄÄÆÄÀÏÀ» À§Çؼ­ `sco_osr5_g77.patch'À» Àû¿ëÇÏ¿© ÄÄÆÄÀÏ µÇ¾ú´Ù¸é, ¿µÇâ¹ÞÀº À߸øÀÌ µð¹ö°Å¿¡¼­ ºÐ¼®ÇßÀ»¶§ /usr/lib/ld.so.1·Î½á ÇÁ·Î±×·¥À» µ¹¸±¶§¿Í rtld()¿¡¼­ ÆúÆ®¿Í ÇÔ²² ÀϾ´Â ½ºÅà ¹éÆ®·¹À̽º¸¦ º¼ °ÍÀÌ´Ù. ÀÌ ÇÁ·Î±×·¥Àº SCO ¿£Áö´Ï¾î¸µ¿¡ ¸®Æ÷Æ®µÇ¾î ÀÖ°í ÈÄ¿¡ ¸±¸®Áî¿¡¼­ ¾ð±ÞµÇ¾îÁú °ÍÀÌ´Ù.


i?86-*-solaris*

GCC 2.95.2, when configured to use the GNU assembler, would invoke it with the -s switch, that GNU as up to 2.9.5.0.12 does not support. If you'd rather not use a newer GNU as nor the native assembler, you'll need the patch `x86-sol2-gas.patch'.

GNU ¾î¼Àºí·¯¸¦ »ç¿ëÇϱâ À§ÇÑ ¼³Á¤À¸·Î GCC 2.95.2´Â -s ½ºÀ§Ä¡¿Í ÇÔ²² ±×°ÍÀ» ºÎ¸¦¼ö ÀÖ´Ù. 2.9.5.0.12¹öÀü GNU¿¡¼­´Â Áö¿øÇÏÁö ¾Ê´Â´Ù. ¸¸¾à ´ç½ÅÀÌ ´õ »õ·Î¿î GNU¸¦ »ç¿ëÇÏÁö ¾Ê°Å³ª ³×ÀÌƼºê ¾î¼Àºí·¯¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù¸é ÆÐÄ¡ `x86-sol2-gas.patch'¸¦ ÇÒ ÇÊ¿ä°¡ ÀÖ´Ù.


i?86-*-udk

This target emulates the SCO Universal Development Kit and requires that package be installed. (If it is installed, you will have a /udk/usr/ccs/bin/cc file present.) It's very much like the i?86-*-unixware7* target but is meant to be used when hosting on a system where UDK isn't the default compiler such as OpenServer 5 or Unixware 2. This target will generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, with the same warnings and caveats as the SCO UDK.

ÀÌ Å¸°Ù ¸Ó½Å¿¡¼­´Â SCO Universal Development KitÀ» ¿¡¹Ä·¹ÀÌÆ®ÇÏ°í ¼³Ä¡µÈ ÆÐÅ°Áö¸¦ ¿ä±¸ÇÑ´Ù. (¸¸¾à ±×°ÍÀÌ ¼³Ä¡µÇ¾îÀÖ´Ù¸é, ´ç½ÅÀº /udk/usr/ccs/bin/cc È­ÀÏÀ» °¡Áö°í ÀÖÀ» °ÍÀÌ´Ù.) ÀÌ°ÍÀº i?86-*-unixware7*À» ¸Å¿ì ºñ½ÁÇÏÁö¸¸ OpenServer 5 ¶Ç´Â Unixware 2°ú °°ÀÌ UDK°¡ µðÆúÆ® ÄÄÆÄÀÏ·¯°¡ ¾Æ´Ñ ½Ã½ºÅÛ¿¡ È£½ºÆÃÇÒ¶§ »ç¿ëÇÏÁö ¾ÊÀ¸¸é ¾ÈµÈ´Ù. ÀÌ Å¸°Ù¸Ó½ÅÀº SCO UDK·Î½áÀÇ °°Àº °æ°í(same warnings and caveats)¿Í ÇÔ²² OpenServer, Unixware 2, ¶Ç´Â Unixware 7¿¡¼­ ½ÇÇàµÇ´Â ¹ÙÀ̳ʸ®¸¦ ¸¸µé¾î³¾ °ÍÀÌ´Ù.

You can stage1 with either your native compiler or with UDK. If you don't do a full bootstrap when initially building with your native compiler you will have an utterly unusable pile of bits as your reward.

´ç½ÅÀº ³×ÀÌƼºê ÄÄÆÄÀÏ·¯³ª UDK¸¦ °¡Áö°í ½ºÅ×ÀÌÁö1À» ÇÒ ¼ö ÀÖ´Ù. ¸¸¾à Ãʱ⿡ ÀÚ½ÅÀÇ ³×ÀÌƼºê ÄÄÆÄÀÏ·¯¿Í ÇÔ²² ÄÄÆÄÀÏ(build)ÇÒ¶§ Ç® ºÎÆ®½ºÆ®·¦ÇÏÁö ¾Ê´Â´Ù¸é, °á°ú·Î½á ÀüÇô »ç¿ëÇÒ ¼ö ¾ø´Â ºñÆ®ÀÇ ´õ¹Ì¸¦ °¡Áö°Ô µÉ °ÍÀÌ´Ù.

This target is a little tricky to build because we have to distinguish it from the native tools (so it gets headers, startups, and libraries from the right place) while making the tools not think we're actually building a cross compiler. The easiest way to do this is with a configure command like this:

  CC=/udk/usr/ccs/bin/cc /your/path/to/gcc/configure --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
¹ø¿ªÀÌ Àß ¾ÈµÇ´Â ºÎºÐÀ̳׿ä ^^;

This target is a little tricky to build because we have to distinguish it from the native tools (so it gets headers, startups, and libraries from the right place) while making the tools not think we're actually building a cross compiler. The easiest way to do this is with a configure command like this:

  
  CC=/udk/usr/ccs/bin/cc /your/path/to/gcc/configure --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-

You should substitute 'i686' in the above command with the appropriate processor for your host.

´ç½ÅÀÇ È£½ºÆ®¸¦ À§ÇØ ÀûÀýÇÑ ÇÁ·Î¼¼¼­¿Í ÇÔ²² À§¿¡ Ä¿¸Çµå¿¡ 'i686'À» ½á¾î ³Ö¾î¾ß ÇÑ´Ù.

You should follow this with a `make bootstrap' then `make install'. You can then access the UDK-targeted GCC tools by adding udk- before the commonly known name. For example, to invoke the C compiler, you would use `udk-gcc'. They will coexist peacefully with any native-target GCC tools you may have installed.

`make bootstrap' ±× ÈÄ¿¡ `make install'¶ó´Â ¸í·ÉÀ» ÇؾßÇÑ´Ù. º¸Åë ¾Ë·ÁÁø À̸§Àü¿¡ udk-À» Ãß°¡ÇÔÀ¸·Î½á UDK Ÿ°ÙÀÇ GCC ÅøµéÀ» ¾×¼¼½ºÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¸é, C ÄÄÆÄÀÏ·¯¸¦ È£ÃâÇϱâ À§Çؼ­ ´ç½ÅÀº `udk-gcc'À» »ç¿ëÇÒ °ÍÀÌ´Ù. ±×°ÍµéÀº ´ç½ÅÀÌ ¼³Ä¡ÇßÀ» ¾î¶² ³×ÀÌƼºê¿Í Ÿ°Ù(native-target) GCC°¡ ÇÔ²² ÆòÈ­ÀûÀ¸·Î Á¸ÀçÇÒ °ÍÀÌ´Ù.


*-ibm-aix*

AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or newer is recommended to build on this platform.

AIX Make´Â GCC ¸ÞÀÌÅ©È­ÀÏ°ú ÇÔ²² ºó¹øÈ÷ ¹®Á¦¸¦ ÀÏÀ¸Å²´Ù. GNU Make 3.76 ¶Ç´Â ´õ »õ·Î¿î ¹öÀüÀº ÀÌ Ç÷§Æû¿¡¼­ ¸¸µé°ÍÀ» ±ÇÀåÇÑ´Ù.

Errors involving "alloca" when building GCC generally are due to an incorrect definition of CC in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of the build, the native AIX compiler must be invoked as "cc" (not "xlc"). Once configure has been informed of "xlc", one needs to use "make distclean" to remove the configure cache files and ensure that $CC environment variable does not provide a definition that will confuse configure. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above).

ÀϹÝÀûÀÌ·Î GCC ÄÄÆÄÀÏ(build)ÇÒ¶§ "alloca"¸¦ Æ÷ÇÔÇÏ´Â ¿¡·¯µéÀº Makefile¿¡¼­ CCÀÇ À߸øµÈ Á¤ÀǶ§¹®À̰ųª ³×ÀÌƼºê C ÄÄÆÄÀÏ·¯¿Í GCC¿Í ÇÔ²² ÄÄÆÄÀÏµÈ È¥ÇÕµÈ ÆÄÀϵ鶧¹®ÀÌ´Ù. buildÀÇ ½ºÅ×ÀÌÁö1 °úÁ¤µ¿¾È¿¡, ³×ÀÌƼºê AIX ÄÄÆÄÀÏ·¯´Â ¹Ýµå½Ã "xlc"°¡ ¾Æ´Ï¶ó "cc"·Î½á È£ÃâµÇ¾î¾ßÇÑ´Ù. ´ÜÁö configure´Â "xls"¿¡ ÀÇÇØ ÅëÁö¸¦ ¹Þ±â ¶§¹®¿¡, ȯ°æ¼³Á¤(configure) ij½¬ ÆÄÀÏÁ¦°ÅÇϱâ À§Çؼ­ ±×¸®°í $CC ȯ°æº¯¼ö°¡ configure½Ã¿¡ È¥¶õÀ» ÀÏÀ¸Å°´Â Á¤ÀǸ¦ Á¦°øÇÏÁö ¾Ê±â À§Çؼ­ "make distclean"¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. ¸¸¾à ÀÌ ¿¡·¯°¡ ½ºÅ×ÀÌÁö 2 ³ª ±× ÈÄ¿¡ ¹ß»ýÇÑ´Ù¸é, ¹®Á¦´Â ´ëºÎºÐ Make ¹öÀü¶§¹®ÀÏ °ÍÀÌ´Ù.

Some versions of the AIX binder (linker) can fail with a relocation overflow severe error when the -bbigtoc option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its service.boulder.ibm.com website as PTF U455193.

TOCÀ» ³ÑÄ¡°ÔÇÏ´Â(overflow) ½ÇÇàÇÒ ¼ö ÀÖ´Â °Í¼ÓÀ¸·Î GCC°¡ ¸¸µç ¿ÀºêÁ§Æ® È­ÀϵéÀ» ¸µÅ©Çϱâ À§Çؼ­ -bbigtoc ¿É¼ÇÀ» »ç¿ëÇÒ¶§, AIX ¹ÙÀδõ(¸µÄ¿)ÀÇ ¸î¸î ¹öÀüÀº ¸®·ÎÄÉÀ̼Ç(relocation)°ú ÇÔ²² ½ÇÆÐÇÒ ¼ö ÀÖ´Ù. APAR IX75823(GCC¿Í -BBIGTOC¸¦ »ç¿ëÇÒ ¶§, ¸µÅ©ÇÏ´Â µ¿¾ÈÀÇ ¿À¹öÇ÷οì)¸¦ À§ÇÑ °íħÀº ±×°ÍÀÇ service.boulder.ibm.com À¥ »çÀÌÆ®¿¡¼­ PTF U455193À¸·Î½á »ç¿ë°¡´ÉÇϸç IBM ¼ÒºñÀÚ Áö¿ø¿¡¼­ »ç¿ë°¡´ÉÇÏ´Ù.

Binutils does not support AIX 4.3 (at least through release 2.9). GNU as and GNU ld will not work properly and one should not configure GCC to use those GNU utilities. Use the native AIX tools which do interoperate with GCC.

BinutilsÀº (Àû¾îµµ 2.0 release ÀÌÇÏ¿¡¼­) AIX 4.3À» Áö¿øÇÏÁö ¾Ê´Â´Ù. GNU¿Í GNU ld´Â ÀûÀýÈ÷ ÀÛµ¿ÇÏÁö ¾ÊÀ» °ÍÀ̸ç GNU À¯Æ¿µéÀ» »ç¿ëÇϱâ À§ÇØ GCC configure¸¦ ÇÒ¼ö¾ø´Ù. GCC¿Í »óÈ£ÀÛ¿ëÇÏ´Â ³×ÀÌƼºê AIX ÅøµéÀ» »ç¿ëÇÏ¿©¾ß ÇÑ´Ù.

AIX 4.3 utilizes a new "large format" archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during linking such as "not a COFF file". The version of the routines shipped with AIX 4.3.1 should work for a 32-bit environment. The -g option of the archive command may be used to create archives of 32-bit objects using the original "small format". A correct version of the routines is shipped with AIX 4.3.2.

AIX 4.3´Â 32-bit¿Í 64-bit ¿ÀºêÁ§Æ® ¸ðµâÀ» ´Ù Áö¿øÇϱâ À§Çؼ­ »õ·Î¿î "Å« Æ÷¸Ë(large format)"À» ÀÌ¿ëÇÑ´Ù. ¾ÆÄ«ÀÌºê ¶óÀ̺귯¸®¸¦ ÆĽÌÇϱâ À§Çؼ­ AIX 4.3.0°ú AIX 4.3.1¿¡¼­ Á¦°øÇÏ´Â ·çƾÀº ¿Ã¹Ù¸£°Ô »õ·Î¿î Æ÷¸ËÀ» Çڵ鸵Çϱ⠸øÇß´Ù. ÀÌ·¯ÇÑ ·çƾµéÀº GCC¿¡ ÀÇÇØ »ç¿ëµÇ¸ç ¸µÅ·µ¿¾È¿¡ "not a COFF file"¿Í °°Àº ¿¡·¯ ¸Þ¼¼ÁöµéÀ» °á°ú·Î ¾ò°Ô µÈ´Ù. AIX 4.3.1 °ú ÇÔ²² ³ª¿À´Â ¹öÀüÀÇ ·çƾµéÀº 32-bit ȯ°æÀ» À§Çؼ­¸¸ »ç¿ëµÇ¾î¾ßÇÑ´Ù. ¾ÆÄ«À̺ê Ä¿¸ÇµåÁß¿¡ -g¿É¼ÇÀº ¿ø·¡ÀÇ "small format"À» »ç¿ëÇÏ´Â 32-bit ¿ÀºêÁ§Æ®ÀÇ ¾ÆÄ«À̺긦 ¸¸µå´Âµ¥ ÁÖ·Î »ç¿ëµÇ¾îÁø´Ù. ¹Ù¸¥ ¹öÀüÀÇ ·çƾµéÀº AIX 4.3.2¿¡ µé¾îÀÖ´Ù.

The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its service.boulder.ibm.com website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.

AIX 4.3.0¿¡ µé¾îÀÖ´Â ÃʱâÀÇ ¾î¼Àºí·¯´Â À߸øµÈ ¿ÀºêÁ§Æ® È­ÀϵéÀ» ¸¸µé¾î³½´Ù. APAR IX74254¸¦ À§ÇÑ ¼öÁ¤(64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND)Àº IBM °í°´Áö¿øÀ̳ª ±×°ÍÀÇ service.boulder.ibm.com À¥»çÀÌÆ®¿¡¼­ PTF U453956·Î½á ¹ÞÀ» ¼ö ÀÖ´Ù. ÀÌ ¼öÁ¤Àº AIX 4.3.1À̳ª ±× ÀÌ»óÀÇ °Í°ú »óÈ£ÀÛ¿ë(??)µÇ¾î ÁöÁö ¾Ê´Â´Ù.

The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its service.boulder.ibm.com website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.

AIX 4.3.2.1 ¸µÄ¿(bos.rte.bind_cmds Level 4.3.2.1)´Â ¾î¶² ¹öÀüÀÇ GCC¿¡¼­ È£ÃâµÇ¾îÁú¶§ ¼¼±×¸ÕÆ® ¿À·ù¿Í ÇÔ²² ÄÚ¾î´ýÇÁ(core dump)°¡ ÀϾ °ÍÀÌ´Ù. APAR IX87327¸¦ À§ÇÑ ¼öÁ¤Àº IBM °í°´Áö¿øÀ̳ª ±×°ÍÀÇ service.boulder.ibm.com À¥»çÀÌÆ®¿¡¼­ PTF U461879·Î½á ¹ÞÀ» ¼ö ÀÖ´Ù. ÀÌ ¼öÁ¤Àº AIX 4.3.3 À̳ª ±× ÀÌ»óÀÇ °Í°ú »óÈ£ÀÛ¿ëµÇ¾î ÁöÁö ¾Ê´Â´Ù.


m68k-*-nextstep*

You absolutely must use GNU sed and GNU make on this platform.

´ç½ÅÀº ÀÌ Ç÷§Æû¿¡¼­ GNU sed¿Í GNU make¸¦ Àý´ëÀûÀ¸·Î »ç¿ëÇؾ߸¸ ÇÑ´Ù.

On NEXTSTEP 3.x where x < 3 the build of GCC will abort during stage1 with an error message like this:

  _eh
  /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
  /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character  
  valued 95 (_).

NEXTSTEP 3.x À§¿¡¼­ where x < 3 the build of GCC will abort during stage1 with an error message like this:

  
  _eh
  /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
  /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character  
  valued 95 (_).

The reason for this is the fact that NeXT's assembler for these versions of the operating system does not support the .section pseudo op that's needed for full C++ exception functionality.

ÀÌ¿Í °°Àº ÀÌÀ¯´Â À̹öÀüÀÇ ¿î¿µÃ¼°è¸¦ À§ÇÑ NeXTÀÇ ¾î¼Àºí·¯°¡ ÀüüÀÇ C++ ¿¹¿Üó¸® ÇÔ¼öµéÀ» À§ÇØ ÇÊ¿äÇÑ .section pseudo op¸¦ Áö¿øÇÏÁö ¾Ê±â ¶§¹®ÀÌ´Ù.

As NeXT's assembler is a derived work from GNU as, a free replacement that does can be obtained at ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz.

NeXT's ¾î¼Àºí·¯´Â GNU·ÎºÎÅÍ ÆÄ»ýµÈ ÀÛ¾÷À̱⠶§¹®¿¡, »ç¿ëÇÒ¼ö ÀÖ´Â ¹«·á ´ëü(replacement)´Â ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz ·ÎºÎÅÍ ¾òÀ» ¼ö ÀÖ´Ù.

If you try to build the integrated C++ & C++ runtime libraries on this system you will run into trouble with include files. The way to get around this is to use the following sequence. Note you must have write permission to the directory prefix you specified in the configuration process of GCC for this sequence to work.

  cd bld-gcc
  make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
  cd gcc
  make bootstrap
  make install-headers-tar
  cd ..
  make bootstrap3

¸¸¾à ÀÌ ½Ã½ºÅÛ¿¡¼­ ÅëÇÕµÈ C++ & C++ ·±Å¸ÀÓ ¶óÀ̺귯¸®¸¦ ¸¸µé°í ½Í´Ù¸é ÀÎŬ·çµå(include) È­Àϵé°ú ÇÔ²² ¹®Á¦¿¡ ºÀÂøÇÏ°Ô µÉ °ÍÀÌ´Ù. ÀÌ·¯ÇÑ ¹®Á¦¸¦ ÇØ°áÇÏ´Â ¹æ¹ýÀº ´ÙÀ½°ú °°ÀÌ µû¶óÇÏ´Â °ÍÀÌ´Ù. ÀÌ·¯ÇÑ ¼øÂ÷Àû ÀÛ¾÷À» À§Çؼ­ GCC ȯ°æ¼³Á¤(configuration) °úÁ¤¿¡¼­ °¡¸£Å°´Â prefixµð·ºÅ丮¿¡ ´ëÇÑ Æ۹̼ÇÀ» °¡Áö°í ÀÖ¾î¾ßÇÔÀ» ÁÖÀÇÇضó.

  cd bld-gcc
  make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
  cd gcc
  make bootstrap
  make install-headers-tar
  cd ..
  make bootstrap3

m68k-sun-sunos4.1.1

It is reported that you may need the GNU assembler on this platform.

ÀÌ Ç÷§Æû¿¡¼­ÀÇ GNU¾î¼Àºí·¯°¡ ÇÊ¿äÇÏ´Ù°í º¸°íµÇ°í ÀÖ´Ù.


mips*-sgi-irix[45]

You must use GAS on these platforms, as the native assembler can not handle the code for exception handling support. Either of these messages indicates that you are using the MIPS assembler when instead you should be using GAS:

  as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal
  .4byte $LECIE1-$LSCIE1
  as0: Error: ./libgcc2.c, line 1:malformed statement

³×ÀÌƼºê ¾î¼Àºí·¯°¡ ¿¹¿Üó¸® Áö¿øÀ» À§ÇÑ Äڵ带 ´Ù·çÁö ¸øÇϱ⠶§¹®¿¡ ÀÌ Ç÷§Æû¿¡¼­´Â GAS¸¦ ¹Ýµå½Ã »ç¿ëÇؾßÇÑ´Ù. GAS¸¦ »ç¿ëÇÏÁö ¾ÊÀ»¶§ ÀÌ·¯ÇÑ ¸Þ¼¼Áö´Â ´ç½ÅÀÌ MIPS ¾î¼Àºí·¯¸¦ »ç¿ëÇÏ°í ÀÖ´Ù´Â °ÍÀ» ÀǹÌÇÑ´Ù:

  as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal
  .4byte $LECIE1-$LSCIE1
  as0: Error: ./libgcc2.c, line 1:malformed statement

or:

  as0: Error: /src/bld-gcc/gcc/libgcc2.c, line 1:undefined symbol in expression
  .word $LECIE1-$LSCIE1

¶Ç´Â:

  
  as0: Error: /src/bld-gcc/gcc/libgcc2.c, line 1:undefined symbol in expression
  .word $LECIE1-$LSCIE1

These systems don't have ranlib, which various components in GCC need; you should be able to avoid this problem by installing GNU binutils, which includes a functional ranlib for this system.

ÀÌ ½Ã½ºÅÛÀº ranlib¸¦ °¡Áö°í ÀÖÁö ¾Ê´Ù. ranlib´Â GCCÀÇ ¿©·¯°¡Áö ÄÄÆ÷³ÍÆ®µéÀÌ ÇÊ¿ä·Î ÇÏ´Â °ÍÀÌ´Ù: ´ç½ÅÀº ÀÌ ½Ã½ºÅÛÀ» À§ÇÑ ±â´ÉÀûÀÎ ranlib¸¦ Æ÷ÇÔÇÏ°í ÀÖ´Â GNU binutilµéÀ» ¼³Ä¡ÇÔÀ¸·Î½á ÀÌ·¯ÇÑ ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö ÀÖ¾î¾ß ÇÑ´Ù.

You may get the following warning on irix4 platforms, it can be safely ignored.

  warning: foo.o does not have gp tables for all its sections.

irix4 Ç÷§Æû¿¡¼­ ´ç½ÅÀº ¾ÈÀüÇÏ°Ô ¹«½ÃµÉ ¼ö ÀÖ´Â ´ÙÀ½°ú °°Àº °æ°í¸¦ ¹Þ°Ô µÉ °ÍÀÌ´Ù.

  
  warning: foo.o does not have gp tables for all its sections.

When building GCC, the build process loops rebuilding cc1 over and over again. This happens on mips-sgi-irix5.2, and possibly other platforms.
It has been reported that this is a known bug in the make shipped with IRIX 5.2. We recommend you use GNU make instead of the vendor supplied make program; however, you may have success with "smake" on IRIX 5.2 if you do not have GNU make available.

GCC¸¦ ÄÄÆÄÀÏ(building)ÇÒ ¶§, ÄÄÆÄÀÏ °úÁ¤Àº cc1À» ´Ù½Ã ÄÄÆÄÀÏ ÇÏ´Â °ÍÀ» °è¼Ó¹Ýº¹ÇÑ´Ù. GCC, mips-sgi-irix5.2 ½Ã½ºÅÛ¿¡¼­ ÀÌ °úÁ¤Àº ÀϾ¸ç, ´Ù¸¥ Ç÷§Æû¿¡¼­µµ ÀϾ ¼ö ÀÖ´Ù.
À̹ö±×´Â IRIX 5.2¿¡ µé¾îÀÖ´Â ¸ÞÀÌÅ©(make)ÀÇ ¾Ë·ÁÁø ¹ö±×¶ó°í º¸°íµÇ¾î ÀÖ´Ù. ¿ì¸®´Â ´Ù¸¥ ¹ê´õÀÇ make ÇÁ·Î±×·¥À» »ç¿ëÇÏ´Â ´ë½Å GNU make¸¦ »ç¿ëÇϱ⸦ ¿ä±¸ÇÑ´Ù. ±×·¯³ª ¸¸¾à ´ç½ÅÀÌ »ç¿ë°¡´ÉÇÑ GNU make¸¦ °¡Áö°í ÀÖÁö ¾Ê´Ù¸é IRIX 5.2¿¡ ÀÖ´Â "smake"¸¦ »ç¿ëÇÏ¿© ¼º°øÇÒ ¼öµµ ÀÖÀ» °ÍÀÌ´Ù.

See http://reality.sgi.com/ariel/freeware for more information about using GCC on IRIX platforms.

IRIX Ç÷§Æû¿¡¼­ÀÇ GCC »ç¿ë¿¡ ´ëÇÑ ´õ ¸¹Àº Á¤º¸°¡ ÇÊ¿äÇÏ´Ù¸é http://reality.sgi.com/ariel/freeware/À» º¸¸éµÈ´Ù.



mips*-sgi-irix6

You must not use GAS on irix6 platforms; doing so will only cause problems.

´ç½ÅÀº irix6 Ç÷§Æû¿¡¼­ GAS¸¦ »ç¿ëÇؾ߸¸ ÇÏÁö ¾Ê¾Æ¾ßÇÑ´Ù; ±×·¸°Ô ÇÔÀ¸·Î ¹®Á¦¸¦ ÀÏÀ¸Å°°Ô µÉ °ÍÀÌ´Ù.

These systems don't have ranlib, which various components in GCC need; you should be able to avoid this problem by making a dummy script called ranlib which just exits with zero status and placing it in your path.

ÀÌ ½Ã½ºÅÛÀº GCC¿¡¼­ÀÇ ¿©·¯°¡Áö ÄÄÆ÷³ÍÆ®µéÀÌ ÇÊ¿ä·Î ÇÏ´Â ranlib¸¦ °¡Áö°í ÀÖÁö ¾Ê´Ù; ´ç½ÅÀº ¿µ°ú ÇÔ²² Á×´Â(exit) ranlib¸¦ È£ÃâÇÏ´Â ´õ¹Ì ½ºÅ©¸³Æ®¸¦ ¸¸µé°í À̸¦ ´ç½ÅÀÇ path¿¡ À§Ä¡½ÃÅ´À¸·Î½á ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö ÀÖ¾î¾ßÇÑ´Ù.

If you are using Irix cc as your bootstrap compiler, you must ensure that the N32 ABI is in use. To test this, compile a simple C file with cc and then run file on the resulting object file. The output should look like:

test.o: ELF N32 MSB ...
If you see:
test.o: ELF 32-bit MSB
then your version of cc uses the O32 ABI default. You should set the environment variable CC to 'cc -n32' before configuring GCC.

¸¸¾à ´ç½ÅÀÇ ºÎÆ®½ºÆ®·¦ ÄÄÆÄÀÏ·¯·Î½á irix cc¸¦ ¾²°í ÀÖ´Â ÁßÀ̶ó¸é, N32 ABIÀÇ »ç¿ëÀ» º¸ÀåÇؾ߸¸ ÇÑ´Ù. ÀÌ°ÍÀ» Å×½ºÆ® Çغ¸±â À§Çؼ­, cc¸¦ ÀÌ¿ëÇÏ¿© °£´ÜÇÑ C È­ÀÏÀ» ÄÄÆÄÀÏÇÏ°í, °á°ú·Î ³ª¿Â ¿ÀºêÁ§Æ® È­ÀÏÀ» ½ÇÇàÇغ¸¶ó. Ãâ·ÂÀÌ ´ÙÀ½°ú °°¾Æ¾ß ÇÑ´Ù:

test.o: ELF N32 MSB ...
´ÙÀ½°ú °°Àº ¸Þ¼¼Áö¸¦ º¸°Ô µÈ´Ù¸é:
test.o: ELF 32-bit MSB
´ç½ÅÀÇ ccÀÇ ¹öÀüÀÌ ±âº»ÀûÀ¸·Î O32 ABI¸¦ »ç¿ëÇÏ°í ÀÖ´Ù´Â °ÍÀÌ´Ù. ´ç½ÅÀº GCC¸¦ ¼³Á¤Çϱâ Àü¿¡ ȯ°æº¯¼ö CC¸¦ 'cc -n32'·Î ¼³Á¤Çؾ߸¸ ÇÑ´Ù.

GCC does not currently support generating O32 ABI binaries in the mips-sgi-irix6 configurations. It used to be possible to create a GCC with O32 ABI only support by configuring it for the mips-sgi-irix5 target. See the link below for details.

mips-sgi-irix6¼³Á¤¿¡¼­ GCC´Â O32 ABI¸¦ ¸¸µå´Â °ÍÀ» ÇöÀç Áö¿øÇÏÁö ¾Ê°í ÀÖ´Ù. Ÿ°ÙÀ» mips-sgi-irix5·Î ¼³Á¤ÇÔÀ¸·Î½á O32 ABIÁö¿ø°ú ÇÔ²² GCC¸¦ ¸¸µå´Â °ÍÀ» °¡´ÉÇÏ°Ô ÇÒ ¼ö ÀÖ´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº ¾Æ·¡ ¸µÅ©¸¦ ÂüÁ¶Çϼ¼¿ä.

GCC does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very involved and difficult to fix. It affects a number of other targets also, but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte structures are common. The exact problem is that structures are being padded at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes of the register when it should be loaded into the upper 4 bytes of the register.

GCC´Â 16 byteº¸´Ù À۰ųª 8 byte°¡ ¾Æ´Ñ ±¸Á¶Ã¼¸¦ ¿Ã¹Ù¸£°Ô Æнº(pass)Çϰųª ¸®ÅÏ(return)ÇÒ ¼ö ¾ø´Ù. ÀÌ ¹®Á¦´Â ¸Å¿ì º¹ÀâÇϸç ÇØ°áÇϱ⠾î·Æ´Ù. ÀÌ ¹®Á¦´Â ¸¹Àº ´Ù¸¥ Ç÷§Æû¿¡¼­µµ ¿µÇâÀ» ¹ÌÄ£´Ù. IRIX 6¿¡¼­´Â ´ëü·Î ¹®Á¦¸¦ ÀÏÀ¸Å²´Ù. IRIX 6ÀÌ 64bit Ÿ°ÙÀ̸ç, 4 byte ±¸Á¶Ã¼¸¦ »ç¿ëÇϱ⠶§¹®ÀÌ´Ù. Á¤È®ÇÑ ¹®Á¦´Â ±¸Á¶Ã¼¿¡ À߸øµÈ ³¡ºÎºÐ¿¡ Æеù(padding)µÇ¾îÁö±â ¶§¹®ÀÌ´Ù. ¿¹¸¦ µé¸é, 4 byteÀÇ ±¸Á¶Ã¼°¡ ·¹Áö½ºÅÍÀÇ »óÀ§ 4byte¿¡ ·ÎµùµÇ¾î¾ß ÇÒ¶§, ·¹Áö½ºÅÍÀÇ ÇÏÀ§ 4byte¿¡ ·ÎµùÀÌ µÈ´Ù´Â °ÍÀÌ´Ù.

GCC is consistent with itself, but not consistent with the SGI C compiler (and the SGI supplied runtime libraries), so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. I can only recall seeing two of them: inet_ntoa, and semctl.

GCC´Â ½º½º·Î ÀÏ°ü¼ºÀ» °¡ÁöÁö¸¸, SGI C ÄÄÆÄÀÏ·¯(±×¸®°í SGI¸¦ Áö¿øÇÏ´Â ·±Å¸ÀÓ ¶óÀ̺귯¸®µé)°ú ÇÔ²² ÀÏ°ü¼ºÀ» °¡ÁöÁö´Â ¸øÇÑ´Ù. ±×·¡¼­, ±×·± ±¸Á¶Ã¼¸¦ °¡Á®¿À°Å³ª µ¹·Á³õ´Â ¶óÀ̺귯¸® ÇÔ¼öµéÀÌ ÀÖÀ»¶§ ´ÜÁö ÀÌ·± ¹®Á¦°¡ ÀϾ´Ù. ±×·± ¶óÀ̺귯¸®°¡ ¾ÆÁÖ Àû´Ù. ³ª´Â ´ÜÁö ¾Æ·¡ÁßÀÇ µÎ°³¸¸ ºÃ´ø °ÍÀ» ±â¾ïÇÒ ¼ö ÀÖ´Ù: inet_ntoa, and semctl.

See http://reality.sgi.com/ariel/freeware for more information about using GCC on IRIX platforms.

IRIX Ç÷§Æû¿¡¼­ GCC »ç¿ë¿¡ °üÇÑ ´õ ¸¹Àº Á¤º¸´Â http://reality.sgi.com/ariel/freeware/¿¡¼­ ¾òÀ» ¼ö ÀÖ´Ù.


powerpc-*-linux-gnu*

You will need binutils-2.9.4.0.8 or newer for a working GCC. It is strongly recommended to recompile binutils if you initially built it with gcc-2.7.2.x.

GCC ÀÛ¾÷À» À§Çؼ­ binutils-2.9.4.0.8³ª ±× ÀÌ»óÀÇ ¹öÀüÀÌ ÇÊ¿äÇÏ°Ô µÉ °ÍÀÌ´Ù. ¸¸¾à Ãʱ⿡ gcc-2.7.2.x.°ú ÇÔ²² ±×°ÍÀ» ÄÄÆÄÀÏ(build)Çß´Ù¸é, ´Ù½Ã binutilµéÀ» ÀçÄÄÆÄÀÏÇϱ⸦ °­ÇÏ°Ô ±ÇÀåÇÑ´Ù.


*-*-solaris*

Starting with Solaris, Sun does not ship a C compiler any more. To bootstrap and install GCC you first have to install a pre-built compiler, see our binaries page for details.

Solaris·Î ½ÃÀÛÇÒ¶§, SunÀº ´õ ÀÌ»ó C ÄÄÆÄÀÏ·¯¸¦ Æ÷ÇÔÇÏÁö ¾Ê´Â´Ù. GCC¸¦ ºÎÆ®½ºÆ®·¦ÇÏ°í ¼³Ä¡Çϱâ À§Çؼ­ ¸ÕÀú ¿©¹úÄÄÆÄÀÏ(pre-build)µÈ ÄÄÆÄÀÏ·¯¸¦ ¼³Ä¡ Çؾ߸¸ ÇÑ´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº binaries page¸¦ Âü°íÇ϶ó.

Sun as 4.X is broken in that it cannot cope with long symbol names. A typical error message might look similar to the following:

/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: can't compute value of an expression involving an external symbol.

Sun 4.X´Â ±ä ½Éº¼À̸§¿¡ ´ëóÇÒ ¼ö ¾ø°Ô µÇ¾îÀÖ´Ù. ÀüÇüÀûÀÎ ¿¡·¯ ¸Þ¼¼Áö´Â ´ÙÀ½°ú ºñ½ÁÇÒ °ÍÀÌ´Ù:

/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: can't compute value of an expression involving an external symbol.

See the How to work around too long C++ symbol names? FAQ entry for further information.

´õ ¸¹Àº Á¤º¸¸¦ À§ÇØ How to work around too long C++ symbol names? FAQ ¿£Æ®¸®¿¡¼­ º¼ ¼ö ÀÖ´Ù.

Sun make in all known Solaris 1 (SunOS 4) and Solaris 2 releases has a broken VPATH mechanism, which means you must either:

Solaris 1 (SunOS 4) °ú Solaris 2 releases¿¡¼­ÀÇ Sun make´Â ±úÁø VPATH ¸ÅÄ¿´ÏÁòÀ» °¡Áö°í ÀÖ´Ù, ÀÌ°ÍÀº ´ÙÀ½ Áß¿¡ Çϳª¸¦ ÀǹÌÇÑ´Ù:


sparc-sun-solaris*

binutils 2.9.1 has known bugs on this platform. We recommend to use the vendor tools (Sun as, Sun ld) until these have been fixed. Unfortunately, C++ shared libraries, including libstdc++, won't work properly if assembled with Sun as: the linker will complain about relocations in read-only sections, in the definition of virtual tables. Some possible work-arounds: use some development release of binutils, wait for the next stable binutils release or refrain from creating C++ shared libraries.

ÀÌ Ç÷§Æû¿¡¼­ binutils 2.9.1Àº ¹ö±×°¡ ÀÖ´Ù°í ¾Ë·ÁÁ® ÀÖ´Ù. ÀÌ ¹ö±×°¡ °íÃÄÁö±â Àü±îÁö ¹ê´õ Åø(Sun as, Sun ld)µéÀ» »ç¿ëÇϱ⸦ ±ÇÀåÇÑ´Ù. ºÒÇàÇÏ°Ôµµ, Sun¿¡¼­ ¾î¼ÀºíÇÑ´Ù¸é libstdc++¸¦ Æ÷ÇÔÇÑ C++ °øÀ¯ ¶óÀ̺귯¸®°¡ ¹Ù¸£°Ô µ¿ÀÛÇÏÁö ¾ÊÀ» °ÍÀÌ´Ù: ¸µÄ¿´Â ÀбâÀü¿ë °ø°£, °¡»ó Å×À̺í Á¤ÀÇ¿¡¼­ÀÇ ¸®·ÎÄÉÀ̼ǿ¡ °üÇØ ¹®Á¦¸¦ ÀÏÀ¸Å³ °ÍÀÌ´Ù. ¸î¸î °¡´ÉÇÑ ¹æ¹ý: ¸î¸îÀÇ binutilµéÀÇ °³¹ß ¹öÀüÀ» »ç¿ëÇϰųª, ´ÙÀ½ ¾ÈÁ¤ÀûÀÎ binutilÀ» ±â´Ù¸®¸é µÈ´Ù, ¶Ç´Â ¸¸µé¾îÁø C++°øÀ¯ ¶óÀ̺귯¸®µéÀ» »ç¿ëÇÏÁö ¾ÊÀ¸¸é µÈ´Ù.


sparc-sun-solaris2.7

Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 and later, including all EGCS releases. Sun formerly recommended 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to recommend it only for people who use Sun's compilers.

SPARC Solaris 7À» À§ÇÑ Sun patch 107058-01(1999-01-13)´Â µ¿Àû¸µÄ¿¿¡¼­ ¹ö±×¸¦ ÀÏÀ¸Å²´Ù. ÀÌ ¹®Á¦(Sun bug 4210064)´Â GCC 2.8 ³ª ¸ðµç EGCS release¸¦ Æ÷ÇÔÇÏ¿© ±× ÀÌÈÄ¿¡ ¹öÀüÀÇ GCC¿¡ ¿µÇâÀ» ¹ÌÄ£´Ù. SunÀº ¸ðµç Solaris 7 »ç¿ëÀÚµéÀ» À§ÇØ 107058-01¸¦ ±ÇÀåÇÑ´Ù. ±×·¯³ª , 1999-09-01Á¤µµ¿¡ SunÀÇ ÄÄÆÄÀÏ·¯¸¦ »ç¿ëÇÏ°í ÀÖ´Â »ç¶÷µéÀ» À§ÇØ ±ÇÀåµÇ±â ½ÃÀÛÇß´Ù.

Here are some workarounds to this problem:

ÀÌ ¹®Á¦¸¦ ÇØ°áÇÏ´Â ¹æ¹ý¿¡´Â ¸î°¡Áö°¡ ÀÖ´Ù:


Sun V5.0 Compiler Bugs

The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC 2.95.1, which in turn causes GCC to fail its bootstrap comparison test. GCC 2.95.2 has a workaround. Sun V5.0 ÄÄÆÄÀÏ·¯´Â À߸ø ÄÄÆÄÀϵÈ(mis-compile) GCC 2.95 and GCC 2.95.1·Î ¾Ë·ÁÁ® ÀÖ´Ù. ÀÌ´Â GCC°¡ ºÎÆ®½ºÆ®·¦ ºñ±³ Å×½ºÆ®¸¦ ½ÇÆÐÇÏ°Ô ¸¸µç´Ù. GCC 2.95.2¿¡¼­´Â ÇØ°áµÇ¾ú´Ù.

sparc-sun-sunos*

A bug in the SunOS4 linker will cause it to crash when linking -fPIC compiled objects (and will therefore not allow you to build shared libraries).

SunOS4 ¸µÄ¿¿¡¼­ÀÇ ¹ö±×´Â -fPIC·Î ¸µÅ·µÇ¾î ÄÄÆÄÀÏµÈ ¿ÀºêÁ§Æ®¿¡¼­ Ãæµ¹À» ¾ß±â½ÃŲ´Ù (±×¸®°í °øÀ¯¸Þ¸ð¸® ¸¸µå´Â °ÍÀ» Çã¿ëÇÏÁö ¾Ê°ÔµÈ´Ù).

To fix this problem you can either use the most recent version of binutils or get the latest SunOS4 linker patch (patch ID 100170-10) from Sun's patch site.

ÀÌ ¹®Á¦ÀÇ ÇØ°áÀ» À§Çؼ­ ´ç½ÅÀº °¡Àå ÃֽŠ¹öÀüÀÇ binutilµéÀ» »ç¿ëÇϰųª SunÀÇ ÆÐÄ¡ »çÀÌÆ®·ÎºÎÅÍ ÃÖ±ÙÀÇ SunOS4 linker patch (patch ID 100170-10)¸¦ °¡Á®¿Í¼­ »ç¿ëÇØ¾ß ÇÑ´Ù


sparc-unknown-linux-gnulibc1

It has been reported that you might need binutils-2.8.1.0.23 for this platform, too.

ÀÌ Ç÷§Æû¿¡¼­µµ »ç¿ëÇϱâ À§ÇØ binutils-2.8.1.0.23ÀÌ ¿ª½Ã ÇÊ¿äÇÏ´Ù°í º¸°í µÇ¾ú´Ù.


sparc64-*-*

GCC version 2.95 is not able to compile code correctly for sparc64 targets. Users of the Linux kernel, at least, can use the sparc32 program to start up a new shell invocation with an environment that causes configure to recognize (via uname -a) the system as sparc-*-* instead.

GCC ¹öÀü 2.95´Â sparc64 Ÿ°ÙÀ¸·Î ¹Ù¸£°Ô Äڵ带 ÄÄÆÄÀÏ ÇÒ ¼ö ¾ø´Ù. Àû¾îµµ ¸®´ª½º Ä¿³ÎÀÇ »ç¿ëÀÚµéÀº sparc32 ÇÁ·Î±×·¥À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. sparc32 ÇÁ·Î±×·¥Àº (via uname -a) ´ë½Å¿¡ sparc-*-*·Î½á ½Ã½ºÅÛÀ» ÀνĽÃÅ°±â À§ÇØ configure°¡ ÀÛµ¿ÇÏ°Ô Çϴ ȯ°æ°ú »õ·Î¿î ½© È£ÃâÀ» ½ÃÀÛ½ÃÅ°±â À§ÇØ »ç¿ëµÈ´Ù.


GCC with Windows or OS/2

GCC does not currently support Windows, either natively or with the cygwin32 dll, but there are some links on our binaries page.

GCC´Â ÇöÀç Windows»Ó¸¸ ¾Æ´Ï¶ó the cygwin32 dllÀ» Áö¿øÇÏÁö ¾Ê´Â´Ù. ±×·¯³ª, ¸î¸î ¸µÅ©µéÀ» ÀÌ binaries page¿¡¼­ º¼ ¼ö ÀÖ´Ù.

GCC does not currently support OS/2. However, Andrew Zabolotny has been working on a generic os/2 port with pgcc. The current code code can be found at http://www.goof.com/pcg/os2/.

GCC´Â ÇöÀç OS/2¸¦ Áö¿øÇÏÁö ¾Ê´Â´Ù. ±×·¯³ª, Andrew Zabolotny´Â pgcc¸¦ °¡Áø ÀϹÝÀûÀÎ os/2 port¿¡¼­ ÀÛ¾÷ÇÏ°í ÀÖ´Ù. ÇöÀç ÄÚµå´Â http://www.goof.com/pcg/os2/ ¿¡¼­ º¼ ¼ö ÀÖ´Ù.


all ELF targets (SVR4, Solaris, etc.)

C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically.

¸¸¾à GNU¸µÄ¿¸¦ »ç¿ëÇÏ°í ÀÖ´Ù¸é C++ Áö¿øÀº ´Ù¸¥ Ç÷§Æû¿¡¼­ µÎµå·¯Áö°Ô ³ª¾ÆÁö°í ÀÖ´Ù; duplicate copies of inlines, vtables,template instantiations ÀÌ ÀÚµ¿ÀûÀ¸·Î ¾ø¾îÁö°í ÀÖ´Ù.


Return to the GCC Installation page

GCC ¼³Ä¡Çϱâ ÆäÀÌÁö·Î µ¹¾Æ°¡±â