CIA - The World Factbook -- Country Comparison :: Birth rate

CIA - The World Factbook -- Country Comparison :: Birth rate

This entry gives the average annual number of births during a year per 1,000 persons in the population at midyear; also known as crude birth rate. The birth rate is usually the dominant factor in determining the rate of population growth. It depends on both the level of fertility and the age structure of the population. Rank country (births/1,000 population) Date of Information 1 Niger 51.60 2009 est. 2 Uganda 47.84 2009 est. 3 Mali 46.44 2009 est. 4 Burkina Faso 44.33 2009 est. 5 Somalia 43.70 2009 est. 6 Angola 43.69 2009 est. 7 Ethiopia 43.66 2009 est. 8 Congo, Democratic Republic of the 42.63 2009 est. 9 Liberia 42.25 2009 est. 10 Burundi 41.76 2009 est. 11 Malawi 41.68 2009 est. 12 Congo, Republic of the 41.37 2009 est. 13 Chad 40.86 2009 est. 14 Zambia 40.24 2009 est. 15 Western Sahara 39.54 2009 est. 16 Mayotte 39.26 2009 est. 17 Benin 39.22 2009 est. 18 Sierra Leone 39.08 2009 est. 19 Sao Tome and Principe 38.54 2009 est. 20 Afghanistan 38.37 2009 est. 21 Madagascar 38.14 2009 est. 22 Rwanda 38.06 2009 est. 23 Mozambique 37.98 2009 est. 24 Gambia, The 37.80 2009 est. 25 Guinea 37.52 2009 est. 26 Gaza Strip 36.93 2009 est. 27 Senegal 36.84 2009 est. 28 Nigeria 36.65 2009 est. 29 Kenya 36.64 2009 est. 30 Equatorial Guinea 36.52 2009 est. 31 Togo 36.49 2009 est. 32 Guinea-Bissau 35.97 2009 est. 33 Gabon 35.57 2009 est. 34 Yemen 35.32 2009 est. 35 Comoros 35.23 2009 est. 36 Oman 34.79 2009 est. 37 Tanzania 34.29 2009 est. 38 Eritrea 34.20 2009 est. 39 Mauritania 34.11 2009 est. 40 Cameroon 34.10 2009 est. 41 Laos 33.96 2009 est. 42 Sudan 33.74 2009 est. 43 Central African Republic 32.75 2009 est. 44 Cote d'Ivoire 32.11 2009 est. 45 Zimbabwe 31.49 2009 est. 46 Marshall Islands 30.70 2009 est. 47 Kiribati 30.20 2009 est. 48 Iraq 30.09 2009 est. 49 Haiti 29.10 2009 est. 50 Ghana 28.74 2009 est. 51 Saudi Arabia 28.55 2009 est. 52 Paraguay 28.17 2009 est. 53 Swaziland 28.09 2009 est. 54 Samoa 28.06 2009 est. 55 Guatemala 27.98 2009 est. 56 Solomon Islands 27.69 2009 est. 57 Papua New Guinea 27.57 2009 est. 58 Jordan 27.38 2009 est. 59 Belize 27.33 2009 est. 60 Tajikistan 26.90 2009 est. 61 Djibouti 26.34 2009 est. 62 Honduras 26.28 2009 est. 63 Timor-Leste 26.25 2009 est. 64 Philippines 26.01 2009 est. 65 Pakistan 25.89 2009 est. 66 Bolivia 25.82 2009 est. 67 Cambodia 25.73 2009 est. 68 West Bank 25.44 2009 est. 69 Egypt 25.43 2009 est. 70 El Salvador 25.31 2009 est. 71 Libya 25.13 2009 est. 72 Syria 25.00 2009 est. 73 Bangladesh 24.68 2009 est. 74 Lesotho 24.14 2009 est. 75 Nauru 23.90 2009 est. 76 Cape Verde 23.50 2009 est. 77 Kyrgyzstan 23.44 2009 est. 78 American Samoa 23.31 2009 est. 79 Nicaragua 23.25 2009 est. 80 Nepal 23.18 2009 est. 81 Tuvalu 23.11 2009 est. 82 Micronesia, Federated States of 23.10 2009 est. 83 Botswana 22.89 2009 est. 84 Namibia 22.51 2009 est. 85 Dominican Republic 22.39 2009 est. 86 Malaysia 22.24 2009 est. 87 Northern Mariana Islands 21.97 2009 est. 88 Fiji 21.92 2009 est. 89 Kuwait 21.79 2009 est. 90 India 21.72 2009 est. 91 Vanuatu 21.53 2009 est. 92 Grenada 21.32 2009 est. 93 Mongolia 21.05 2009 est. 94 Turks and Caicos Islands 20.79 2009 est. 95 Ecuador 20.77 2009 est. 96 Venezuela 20.61 2009 est. 97 Panama 20.18 2009 est. 98 Bhutan 20.07 2009 est. 99 South Africa 19.93 2009 est. 100 World 19.86 2009 est. 101 Tonga 19.84 2009 est. 102 Israel 19.77 2009 est. 103 Morocco 19.72 2009 est. 104 Mexico 19.71 2009 est. 105 Turkmenistan 19.69 2009 est. 106 Jamaica 19.68 2009 est. 107 Peru 19.38 2009 est. 108 Indonesia 18.84 2009 est. 109 Turkey 18.66 2009 est. 110 Brazil 18.43 2009 est. 111 Guyana 18.31 2009 est. 112 Brunei 18.20 2009 est. 113 Colombia 18.09 2009 est. 114 Argentina 17.94 2009 est. 115 Vietnam 17.73 2009 est. 116 Saint Kitts and Nevis 17.67 2009 est. 117 Azerbaijan 17.62 2009 est. 118 Uzbekistan 17.58 2009 est. 119 Costa Rica 17.43 2009 est. 120 Iran 17.17 2009 est. 121 Lebanon 17.10 2009 est. 122 New Caledonia 17.04 2009 est. 123 Bahrain 17.01 2009 est. 124 Burma 16.97 2009 est. 125 Algeria 16.90 2009 est. 126 Suriname 16.80 2009 est. 127 Kazakhstan 16.60 2009 est. 128 Antigua and Barbuda 16.59 2009 est. 129 Bahamas, The 16.41 2009 est. 130 Sri Lanka 16.26 2009 est. 131 Cook Islands 16.18 2009 est. 132 United Arab Emirates 16.02 2009 est. 133 French Polynesia 15.91 2009 est. 134 Seychelles 15.87 2009 est. 135 Dominica 15.73 2009 est. 136 Qatar 15.61 2009 est. 137 Tunisia 15.42 2009 est. 138 Albania 15.29 2009 est. 139 Saint Vincent and the Grenadines 15.27 2009 est. 140 Saint Lucia 15.10 2009 est. 141 Korea, North 14.82 2009 est. 142 Greenland 14.76 2009 est. 143 Chile 14.64 2009 est. 144 British Virgin Islands 14.62 2009 est. 145 Maldives 14.55 2009 est. 146 Mauritius 14.41 2009 est. 147 Trinidad and Tobago 14.36 2009 est. 148 Ireland 14.23 2009 est. 149 Netherlands Antilles 14.19 2009 est. 150 Gibraltar 14.03 2009 est. 151 China 14.00 2009 est. 152 New Zealand 13.94 2009 est. 153 Uruguay 13.91 2009 est. 154 United States 13.83 2009 est. 155 Iceland 13.43 2009 est. 156 Thailand 13.38 2009 est. 157 Faroe Islands 13.04 2009 est. 158 Anguilla 13.02 2009 est. 159 Aruba 12.79 2009 est. 160 Saint Pierre and Miquelon 12.74 2009 est. 161 Armenia 12.65 2009 est. 162 France 12.57 2009 est. 163 Barbados 12.55 2009 est. 164 Australia 12.47 2009 est. 165 Cayman Islands 12.36 2009 est. 166 Montserrat 12.36 2009 est. 167 Macedonia 11.97 2009 est. 168 Virgin Islands 11.95 2009 est. 169 Luxembourg 11.73 2009 est. 170 Puerto Rico 11.72 2009 est. 171 Bermuda 11.57 2009 est. 172 Cyprus 11.32 2009 est. 173 Palau 11.20 2009 est. 174 Montenegro 11.14 2009 est. 175 Cuba 11.13 2009 est. 176 Saint Helena, Ascension, and Tristan da Cunha 11.13 2009 est. 177 Moldova 11.12 2009 est. 178 Russia 11.10 2009 est. 179 Norway 10.99 2009 est. 180 Isle of Man 10.77 2009 est. 181 Georgia 10.66 2009 est. 182 United Kingdom 10.65 2009 est. 183 Slovakia 10.60 2009 est. 184 Denmark 10.54 2009 est. 185 Romania 10.53 2009 est. 186 Netherlands 10.40 2009 est. 187 Finland 10.38 2009 est. 188 Estonia 10.37 2009 est. 189 Malta 10.36 2009 est. 190 Andorra 10.35 2009 est. 191 Portugal 10.29 2009 est. 192 Canada 10.28 2009 est. 193 Belgium 10.15 2009 est. 194 Sweden 10.13 2009 est. 195 Poland 10.04 2009 est. 196 Latvia 9.78 2009 est. 197 Liechtenstein 9.75 2009 est. 198 Spain 9.72 2009 est. 199 Belarus 9.71 2009 est. 200 San Marino 9.68 2009 est. 201 Croatia 9.64 2009 est. 202 Ukraine 9.60 2009 est. 203 Switzerland 9.59 2009 est. 204 Bulgaria 9.51 2009 est. 205 Hungary 9.51 2009 est. 206 Greece 9.45 2009 est. 207 Serbia 9.19 2009 est. 208 Lithuania 9.11 2009 est. 209 Monaco 9.10 2009 est. 210 Taiwan 8.99 2009 est. 211 Slovenia 8.97 2009 est. 212 Korea, South 8.93 2009 est. 213 Macau 8.88 2009 est. 214 Bosnia and Herzegovina 8.85 2009 est. 215 Czech Republic 8.83 2009 est. 216 Singapore 8.82 2009 est. 217 Austria 8.65 2009 est. 218 Jersey 8.63 2009 est. 219 Guernsey 8.55 2009 est. 220 Germany 8.18 2009 est. 221 Italy 8.18 2009 est. 222 Japan 7.64 2009 est. 223 Hong Kong 7.42 2009 est.

The online Factbook is updated bi-weekly. ISSN 1553-8133 For additional information on government leaders in selected foreign countries, go to World Leaders.

小P：出生率最低的是香港，不是台灣或德國…

中油汽柴油明起漲1毛-Yahoo!奇摩新聞

中油汽柴油明起漲1毛-Yahoo!奇摩新聞

更新日期:2010/01/10 13:35

中油今天宣布，國內汽、柴油價格從明天凌晨零點開始，各調漲0.1元。調漲後，98無鉛汽油每公升為32.3元，95每公升30.8元，92為30.1元，至於超級柴油部分，調漲後為每公升27.7元。
中油公司依照浮動油價機制調價，這個星期改成在星期天中午公布。中油表示，由於國際油價走升，依照浮動油價調整機制公式計算後，汽、柴油每公升原本應該分別調漲0.3和0.4元，不過，由於在調漲後的稅前批售價比亞鄰最低價日本還要高，因此，為維持亞鄰競爭國最低價的原則，這星期中油汽、柴油只調漲0.1元，還沒反映的金額將由中油先行吸收，日後再回補。
中油表示，汽、柴油從星期一凌晨零點開始，每公升調漲0.1元，調漲後，98、95和92無鉛汽油每公升分別是32.3元、30.8元和30.1元，至於，超級柴油，調漲後為每公升27.7元。
(責任編輯:陶泰山)

[高速!!官網!!原版!!]中英文版Office 2007下載及破解方法(頁 1) - 電腦軟件交流 - 香港討論區 - Powered by Discuz! Archiver

[高速!!官網!!原版!!]中英文版Office 2007下載及破解方法(頁 1) - 電腦軟件交流 - 香港討論區 - Powered by Discuz! Archiver

運行登錄檔編輯器(按開始->執行，然後輪入 regedit)


11.依次到以下登錄檔項

HKEY_LOCAL_MACHINE\Software\Microsoft\Office\12.0\Registration\{91120000-0031-0000-0000-0000000FF1CE}

或

HKEY_LOCAL_MACHINE\Software\Microsoft\Office\12.0\Registration\{91120000-0014-0000-0000-0000000FF1CE}
(視乎下一步的DigitalProductID在什麼位置)


刪除以下值： DigitalProductID


關閉登錄檔編輯器


打開以下資料夾

C:\Program Files\Common Files\microsoft shared\OFFICE12\Office Setup Controller\Proof.zh-TW
(英文版是Proof.en）

用記事本打開proof.xml文件，

下拉到底層的proof.xml位置如下：


儲存.(如果無權限儲存的話，先複製到桌面修改，完成後取代原來的proof.xml)


你可以到微軟官網驗證

How to Find Which Version of Microsoft Windows You Have | eHow.com

How to Find Which Version of Microsoft Windows You Have | eHow.com

How to Find Which Version of Microsoft Windows You Have

Member

By 17of26
User-Submitted Article

Article Rating: (6 Ratings)

Windows Vista logo

Sometimes it is necessary to figure out which version of Microsoft Windows your computer is running. Even if you know that your computer is running Vista, you might not remember which of the four editions of Vista you have. You also might need to find out which Service Pack you have in order to figure out if you can use an application that requires a particular Service Pack to be installed. Fortunately, Microsoft supplies a tool that will allow you to find which version of Microsoft Windows you have.

• Email
• Print Article
• Add to Favorites
• Flag Article
• 

Difficulty: Easy

Instructions

Things You'll Need:

• Microsoft Windows

1. 
   
   Step 1
   
   Run dialog box" alt="Start->Run dialog box" src="http://i.ehow.com/images/GlobalPhoto/Articles/5058733/emptystartrun_Thumb.jpg">
   
   
   
   Start->Run dialog box
   
   
   Bring up the "Run" dialog box by clicking on Start, then Run. Alternatively, you can bring up the dialog box using a keyboard shortcut by holding down the Window key and pressing R.
   
   
2. 
   
   Step 2
   
   
   
   
   
   Running winver
   
   
   In the edit box next to "Open:" type "winver" without the quotes and then hit enter.
   
   
3. 
   
   Step 3
   
   
   
   
   
   About Windows
   
   
   Read the information in the dialog box that comes up. At the very top of the dialog box is which specific edition of Windows you have. For example, the image for this step shows "Windows Vista Ultimate". Below that is a version number. In the sample image you can see "Version 6.0". It's worth noting that this doesn't mean Version 6.0 of Vista, it's actually Version 6.0 of Microsoft Windows. Vista is just the name that's used to refer to Version 6 (Windows XP was Microsoft Windows Version 5.1). Next to the version number is a build number, which you almost never need to know. Finally there is the Service Pack number which can be important from time to time. Service Pack numbers are inclusive, so if you have Service Pack 3 that means you also have the Service Packs that were released before it.
   
   

Pragma once - 維基百科，自由的百科全書

Pragma once - 維基百科，自由的百科全書

Pragma once

維基百科，自由的百科全書

跳轉到: 導航, 搜尋

在 C 和 C++ 程式語言中，#pragma once 是一個非標準但是被廣泛支援的前置處理符號，會讓所在的檔案在一個單獨的編譯中被include防範一次。以此方式，#pragma once 提供類似include防範的目的，但是擁有較少的程式碼且能避免名稱的碰撞。
請參考include防範裡其中一種狀況的範例或其他的使用方法。如下：

檔案「grandfather.h」

#pragma once

struct foo {
int member;
};

檔案「father.h」

#include "grandfather.h"

檔案「child.c」

#include "grandfather.h"
#include "father.h"

[編輯] 優缺點

使用#pragma once 代替 include 防範將加快編譯速度，因為這是一種高階的機制；編譯器會自動比對檔案名稱或inode而不需要在標頭檔去判斷 #ifndef 和 #endif。
另一方面，部份編譯器，例如GCC，也包含特別的程式碼來識別和有效率的管理 include 防範。[1]
此外，因為編譯器自己必須承擔管理 #pragma once，它不必定義新的指令名稱，例如在 include防範文章範例的 H_GRANDFATHER。這能排除名稱碰撞的風險，意思就是包含一個以上相同的標頭檔不會再有錯誤。
然而，這種高階的管理有好也有壞；設計者必須依賴編譯器正確的管理 #pragma once。編譯器如果犯錯，例如沒有辨認出在相同檔案中的兩個不同符號連結名稱指標，此時編譯會錯誤。編譯器對於 #pragma once 可能包含相關的臭蟲 LCC-Win32 2004年 [2][3] 和 GCC 1998年。[4] 2005年，GCC 文件中將 #pragma once 列為「已淘汰」的特性。[5]

[編輯] 外部連結

• http://msdn.microsoft.com/library/en-us/vclang/html/_predir_pragma_directives.asp

取自"http://zh.wikipedia.org/zh-tw/Pragma_once"

2個分類: C語言 | C++

Include防範 - 維基百科，自由的百科全書

Include防範 - 維基百科，自由的百科全書

Include防範

維基百科，自由的百科全書

跳轉到: 導航, 搜尋

在 C 和 C++ 程式語言中，#include 防範，有時被稱作巨集防範，用於處理 #include 指令時，可避免重複引入的問題。在標頭檔加入 #include 防範是一種讓檔案等冪的方法。

目錄 [隱藏] 1 重複引入 2 使用 #include 防範 3 困難 4 外部連結

[編輯] 重複引入

以下的C語言程式展示了缺少 #include 防範時會出現的問題：

檔案「grandfather.h」

struct foo {
int member;
};

檔案「father.h」

#include "grandfather.h"

檔案「child.c」

#include "grandfather.h"
#include "father.h"

此處 child.c間接引入了兩份grandfather.h標頭檔中的內容。明顯可以看出， foo 結構被定義兩次，因此會造成編譯錯誤。

[編輯] 使用 #include 防範

檔案「grandfather.h」

#ifndef H_GRANDFATHER
#define H_GRANDFATHER

struct foo {
int member;
};

#endif

檔案「father.h」

#include "grandfather.h"

檔案「child.c」

#include "grandfather.h"
#include "father.h"

此處grandfather.h第一次被引入時會定義巨集H_GRANDFATHER。當child.h再次引入grandfather.h時，#ifndef測試失敗，編譯器會直接跳到#endif的部分，也避免了第二次定義foo結構。程式也就能夠正常編譯。

[編輯] 困難

為了讓#include 防範正確運作，每個防範都必須檢驗並且有條件地設定不同的前置處理巨集。因此，使用了 #include 防範的方案必須制訂一致性的命名方法，並確定這個方法不會和其他的標頭檔或任何可見的全域變數衝突。
為了解決這個問題，許多 C 和 C++ 程式開發工具提供非標準的指令 #pragma once。在標頭檔中加入這個指令，能夠保證這個檔案只會被引入一次。不過這個方法會被潛在性顯著的困難阻撓，無論 #include 指令是否在不同的地方，但實際上起源於相同的開頭（舉例，請參考 符號連結）。同樣的，因為 #pragma once 不是一個標準的指令，它的語意在不同的程式開發工具中也許會有微妙的不同。

[編輯] 外部連結

• 引入防範的最佳化
• 多餘的引入防範
• 引入防範生成器

取自"http://zh.wikipedia.org/zh-tw/Include%E9%98%B2%E7%AF%84"

1個分類: C語言

Stickies

Stickies
類似ATnotes，不過仍在開發，且有中文化。

Link Options - Using the GNU Compiler Collection (GCC)

Link Options - Using the GNU Compiler Collection (GCC)

3.13 Options for Linking

These options come into play when the compiler links object files into an executable output file. They are meaningless if the compiler is not doing a link step.

object-file-name

A file name that does not end in a special recognized suffix is considered to name an object file or library. (Object files are distinguished from libraries by the linker according to the file contents.) If linking is done, these object files are used as input to the linker.

-c

-S

-E

If any of these options is used, then the linker is not run, and object file names should not be used as arguments. See Overall Options.

-llibrary

-l library

Search the library named library when linking. (The second alternative with the library as a separate argument is only for POSIX compliance and is not recommended.)

It makes a difference where in the command you write this option; the linker searches and processes libraries and object files in the order they are specified. Thus, `foo.o -lz bar.o' searches library `z' after file foo.o but before bar.o. If bar.o refers to functions in `z', those functions may not be loaded.

The linker searches a standard list of directories for the library, which is actually a file named liblibrary.a. The linker then uses this file as if it had been specified precisely by name.

The directories searched include several standard system directories plus any that you specify with -L.

Normally the files found this way are library files—archive files whose members are object files. The linker handles an archive file by scanning through it for members which define symbols that have so far been referenced but not defined. But if the file that is found is an ordinary object file, it is linked in the usual fashion. The only difference between using an -l option and specifying a file name is that -l surrounds library with `lib' and `.a' and searches several directories.

-lobjc

You need this special case of the -l option in order to link an Objective-C or Objective-C++ program.

-nostartfiles

Do not use the standard system startup files when linking. The standard system libraries are used normally, unless -nostdlib or -nodefaultlibs is used.

-nodefaultlibs

Do not use the standard system libraries when linking. Only the libraries you specify will be passed to the linker, options specifying linkage of the system libraries, such as -static-libgcc or -shared-libgcc, will be ignored. The standard startup files are used normally, unless -nostartfiles is used. The compiler may generate calls to memcmp, memset, memcpy and memmove. These entries are usually resolved by entries in libc. These entry points should be supplied through some other mechanism when this option is specified.

-nostdlib

Do not use the standard system startup files or libraries when linking. No startup files and only the libraries you specify will be passed to the linker, options specifying linkage of the system libraries, such as -static-libgcc or -shared-libgcc, will be ignored. The compiler may generate calls to memcmp, memset, memcpy and memmove. These entries are usually resolved by entries in libc. These entry points should be supplied through some other mechanism when this option is specified. One of the standard libraries bypassed by -nostdlib and -nodefaultlibs is libgcc.a, a library of internal subroutines that GCC uses to overcome shortcomings of particular machines, or special needs for some languages. (See Interfacing to GCC Output, for more discussion of libgcc.a.) In most cases, you need libgcc.a even when you want to avoid other standard libraries. In other words, when you specify -nostdlib or -nodefaultlibs you should usually specify -lgcc as well. This ensures that you have no unresolved references to internal GCC library subroutines. (For example, `__main', used to ensure C++ constructors will be called; see collect2.)

-pie

Produce a position independent executable on targets which support it. For predictable results, you must also specify the same set of options that were used to generate code (-fpie, -fPIE, or model suboptions) when you specify this option.

-rdynamic

Pass the flag -export-dynamic to the ELF linker, on targets that support it. This instructs the linker to add all symbols, not only used ones, to the dynamic symbol table. This option is needed for some uses of dlopen or to allow obtaining backtraces from within a program.

-s

Remove all symbol table and relocation information from the executable.

-static

On systems that support dynamic linking, this prevents linking with the shared libraries. On other systems, this option has no effect.

-shared

Produce a shared object which can then be linked with other objects to form an executable. Not all systems support this option. For predictable results, you must also specify the same set of options that were used to generate code (-fpic, -fPIC, or model suboptions) when you specify this option.¹

-shared-libgcc

-static-libgcc

On systems that provide libgcc as a shared library, these options force the use of either the shared or static version respectively. If no shared version of libgcc was built when the compiler was configured, these options have no effect. There are several situations in which an application should use the shared libgcc instead of the static version. The most common of these is when the application wishes to throw and catch exceptions across different shared libraries. In that case, each of the libraries as well as the application itself should use the shared libgcc. Therefore, the G++ and GCJ drivers automatically add -shared-libgcc whenever you build a shared library or a main executable, because C++ and Java programs typically use exceptions, so this is the right thing to do. If, instead, you use the GCC driver to create shared libraries, you may find that they will not always be linked with the shared libgcc. If GCC finds, at its configuration time, that you have a non-GNU linker or a GNU linker that does not support option --eh-frame-hdr, it will link the shared version of libgcc into shared libraries by default. Otherwise, it will take advantage of the linker and optimize away the linking with the shared version of libgcc, linking with the static version of libgcc by default. This allows exceptions to propagate through such shared libraries, without incurring relocation costs at library load time. However, if a library or main executable is supposed to throw or catch exceptions, you must link it using the G++ or GCJ driver, as appropriate for the languages used in the program, or using the option -shared-libgcc, such that it is linked with the shared libgcc.

-static-libstdc++

When the g++ program is used to link a C++ program, it will normally automatically link against libstdc++. If libstdc++ is available as a shared library, and the -static option is not used, then this will link against the shared version of libstdc++. That is normally fine. However, it is sometimes useful to freeze the version of libstdc++ used by the program without going all the way to a fully static link. The -static-libstdc++ option directs the g++ driver to link libstdc++ statically, without necessarily linking other libraries statically.

-symbolic

Bind references to global symbols when building a shared object. Warn about any unresolved references (unless overridden by the link editor option `-Xlinker -z -Xlinker defs'). Only a few systems support this option.

-T script

Use script as the linker script. This option is supported by most systems using the GNU linker. On some targets, such as bare-board targets without an operating system, the -T option may be required when linking to avoid references to undefined symbols.

-Xlinker option

Pass option as an option to the linker. You can use this to supply system-specific linker options which GCC does not know how to recognize. If you want to pass an option that takes a separate argument, you must use -Xlinker twice, once for the option and once for the argument. For example, to pass -assert definitions, you must write `-Xlinker -assert -Xlinker definitions'. It does not work to write -Xlinker "-assert definitions", because this passes the entire string as a single argument, which is not what the linker expects. When using the GNU linker, it is usually more convenient to pass arguments to linker options using the option=value syntax than as separate arguments. For example, you can specify `-Xlinker -Map=output.map' rather than `-Xlinker -Map -Xlinker output.map'. Other linkers may not support this syntax for command-line options.

-Wl,option

Pass option as an option to the linker. If option contains commas, it is split into multiple options at the commas. You can use this syntax to pass an argument to the option. For example, `-Wl,-Map,output.map' passes `-Map output.map' to the linker. When using the GNU linker, you can also get the same effect with `-Wl,-Map=output.map'.

-u symbol

Pretend the symbol symbol is undefined, to force linking of library modules to define it. You can use -u multiple times with different symbols to force loading of additional library modules.

---

Footnotes

[1] On some systems, `gcc -shared' needs to build supplementary stub code for constructors to work. On multi-libbed systems, `gcc -shared' must select the correct support libraries to link against. Failing to supply the correct flags may lead to subtle defects. Supplying them in cases where they are not necessary is innocuous.