Cbcb - User contributions [en]

Gpertea gcc

2011-01-10T17:26:33Z

Gpertea: /* Compiling gcc/g++ 4.5.x */

=GCC/G++ notes=
=== Linking tips ===
When statically linking with g++, the linker expects -l arguments (libraries) to come after the files containing references to them, so '''the .o and .a files must appear before the -l flags''' in the g++ command line.
=== Compiling gcc/g++ 4.5.x ===
I prefer to prepare the GCC compiler such that it will statically link the C/C++ runtime libraries into the executables generated by the compiler. This way the portability of the precompiled binaries is maximized.
In order to compile GCC/G++ this way:
*Make sure gmp, mpfr and mpc source trees are under the main gcc-*/ source dir
For some mpfr versions, the configure script may need to be patched:
<pre>extra_mpfr_configure_flags='--with-gmp-build=$$r/$(HOST_SUBDIR)/gmp' </pre>
.. replace the above line with:
<pre>extra_mpfr_configure_flags='--with-gmp-include=$$r/$(HOST_SUBDIR)/gmp --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/'"$lt_cv_objdir" </pre>

Assuming tcsh, and that the gcc and g++ source were unpacked under the gcc-4.5.1 subdirectory:
<pre>
cd ..
mkdir gcc45obj
setenv CFLAGS '-O2'
setenv CXXFLAGS '-O2 -fno-implicit-templates'

../gcc-4.5.1/configure --prefix=/fs/sz-user-supported/Linux-x86_64/packages/gcc-4.5.1 \
--enable-threads=posix --disable-shared --disable-multilib --enable-__cxa_atexit \
--disable-libunwind-exceptions --disable-checking --build=x86_64-redhat-linux --disable-dssi \
--enable-plugin --disable-nls --with-cpu=generic --enable-languages=c,c++

make CFLAGS='-O2' BOOT_CFLAGS='-O2' BOOT_FLAGS='-O2' STAGE1_CFLAGS='-O2' LIBCFLAGS='-O2' \
LIBCXXFLAGS='-O2 -fno-implicit-templates' CXXFLAGS='-O2' bootstrap-lean

</pre>
Building may take a long time. After it is done, installing it is simply a matter of running <pre>make install</pre>

Gpertea gcc

2011-01-10T16:33:13Z

Gpertea:

=GCC/G++ notes=
=== Linking tips ===
When statically linking with g++, the linker expects -l arguments (libraries) to come after the files containing references to them, so '''the .o and .a files must appear before the -l flags''' in the g++ command line.
=== Compiling gcc/g++ 4.5.x ===
I prefer to prepare the GCC compiler such that it will statically link the core system and C++ runtime libraries in the executables generated by the compiler. This way the portability of the precompiled binaries is maximized.
In order to compile GCC/G++ this way:
*Make sure gmp, mpfr and mpc source trees are under the main gcc-*/ source dir
For some mpfr versions, the configure script may need to be patched:
<pre>extra_mpfr_configure_flags='--with-gmp-build=$$r/$(HOST_SUBDIR)/gmp' </pre>
.. replace the above line with:
<pre>extra_mpfr_configure_flags='--with-gmp-include=$$r/$(HOST_SUBDIR)/gmp --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/'"$lt_cv_objdir" </pre>

Assuming tcsh, and that the gcc and g++ source were unpacked under the gcc-4.5.1 subdirectory:
<pre>
cd ..
mkdir gcc45obj
setenv CFLAGS '-O2'
setenv CXXFLAGS '-O2 -fno-implicit-templates'

../gcc-4.5.1/configure --prefix=/fs/sz-user-supported/Linux-x86_64/packages/gcc-4.5.1 \
--enable-threads=posix --disable-shared --disable-multilib --enable-__cxa_atexit \
--disable-libunwind-exceptions --disable-checking --build=x86_64-redhat-linux --disable-dssi \
--enable-plugin --disable-nls --with-cpu=generic --enable-languages=c,c++

make CFLAGS='-O2' BOOT_CFLAGS='-O2' BOOT_FLAGS='-O2' STAGE1_CFLAGS='-O2' LIBCFLAGS='-O2' \
LIBCXXFLAGS='-O2 -fno-implicit-templates' CXXFLAGS='-O2' bootstrap-lean

</pre>
Building may take a long time. After it is done, installing it is simply a matter of running <pre>make install</pre>

Help:Contents

2011-01-10T16:09:18Z

Gpertea:

==Editing==
* [[Help:Editing|Editing pages]]
* [[Help:Formatting|Formatting]]
* [[Help:Links|Links]]

Help:Links

2011-01-10T16:08:28Z

Gpertea:

There are four sorts of links in MediaWiki:
# internal links to other pages in the wiki
# external links to websites
# [[Help:Interwiki linking|inter-wiki links]] (links to other wikis)
# inter-language links to other language versions of the same wiki

To add an internal link, enclose the name of the page you want to link to in double square brackets. When you save the page, you'll see the new link pointing to your page. If the page exists already, it is displayed in blue, empty pages are displayed in red. Selflinks to the current page are not transformed in URLs but displayed in bold.

The first letter of the target page is automatically capitalized and spaces are represented as underscores (typing an underscore in the link will have a similar effect as typing a space, but is not recommended, since the underscore will also be shown in the text).

== How to link ==
{| border="1" class="wikitable"
|-
| |'''Description'''
||'''You type'''
||'''You get'''
|-
|Internal link
|<tt><nowiki>[[Main Page]]</nowiki></tt>
|[[Main Page]]
|-
|Category link
|<tt><nowiki>[[:Category:Help]]</nowiki></tt>
|[[:Category:Help]]
|-
|Piped link
|<tt><nowiki>[[Main Page|different text]]</nowiki></tt>
|[[Main Page|different text]]
|-
|Anchor link
|<tt><nowiki>[[#External links|Anchor link]]</nowiki></tt>
|[[#External links|Anchor link]]
|-
|External link
|<tt><nowiki>http://mediawiki.org</nowiki></tt>
|http://mediawiki.org
|-
|Internal link to image file
|<tt><nowiki>[[media:example.jpg]]</nowiki></tt>
|[[media:example.jpg]]
|-
|External link, 
different title
|<tt><nowiki>[http://mediawiki.org MediaWiki]</nowiki></tt>
|[http://mediawiki.org MediaWiki]
|-
|External link, 
unnamed
|<tt><nowiki>[http://mediawiki.org]</nowiki></tt>
|[http://mediawiki.org]
|-
|External link, 
same host unnamed
|<tt><nowiki>[http://{{SERVERNAME}}/pagename]</nowiki></tt>
|[http://{{SERVERNAME}}/pagename]
|-
|Interwiki link
|<tt><nowiki>[[Wikipedia:MediaWiki]]</nowiki></tt>
|[[Wikipedia:MediaWiki]]
|-
|mailto
|<tt><nowiki>mailto:info@example.org</nowiki></tt>
|mailto:info@example.org
|-
|mailto unnamed
|<tt><nowiki>[mailto:info@example.org]</nowiki></tt>
|[mailto:info@example.org]
|-
|mailto named
|<tt><nowiki>[mailto:info@example.org info]</nowiki></tt>
|[mailto:info@example.org info]
|-
|redirect
|<tt><nowiki>#REDIRECT [[Main Page]]</nowiki></tt>
| → [[Main Page]]
|}

''Admin tip'':
Which protocols (like http:) are allowed for links is controlled by the [[Manual:$wgUrlProtocols|$wgUrlProtocols]] setting.

''Admin tip'':
To remove the 'external link image' from next to each of the external links, add the following to the page located at <code>MediaWiki:Monobook.css</code> on your wiki.

<pre>
#bodyContent a.external,
#bodyContent a[href ^="gopher://"] {
background: none;
padding-right: 0;
}
</pre>

Help:Formatting

2011-01-10T16:07:39Z

Gpertea:

You can format your text using wiki markup. This consists of normal characters like asterisks, single quotes or equation marks which have a special function in the wiki, sometimes depending on their position. For example, to format a word in ''italic'', you include it in two single quotes like <tt><nowiki>''this''</nowiki></tt>

== Text formatting markup ==

{| align="center" border="1" class="wikitable"
|-
|width="30%" |'''Description'''
| |'''You type'''
| |'''You get'''
|-
| colspan="3" align="center" | ''applies anywhere''
|-
|Italic text
|<tt><nowiki>''italic''</nowiki></tt>
|''italic''
|-
| Bold text
|<tt><nowiki>'''bold'''</nowiki></tt>
|'''bold'''
|-
| Bold and italic
|<tt><nowiki>'''''bold & italic'''''</nowiki></tt>
|'''''bold & italic'''''
|-
|Escape wiki markup
|<tt><nowiki><nowiki>no ''markup''</nowiki></nowiki></tt>
|<nowiki>no ''markup''</nowiki>
|-
| colspan="3" align="center" | ''only at the beginning of the line''
|-
|Headings of different levels Use of a heading created by single equal signs is discouraged as it appears with the same formatting and size as the page title, which can be confusing. An article with four or more headings will automatically create a [http://en.wikipedia.org/wiki/Wikipedia:Section#Table_of_contents_.28TOC.29 table of contents].
|
<tt><nowiki>==level 1==</nowiki></tt> 
<tt><nowiki>===level 2===</nowiki></tt> 
<tt><nowiki>====level 3====</nowiki></tt> 
<tt><nowiki>=====level 4=====</nowiki></tt>
|

==Level 1==
===Level 2===
====Level 3====
=====Level 4=====
|-
|Horizontal rule
|
<tt><nowiki>----</nowiki></tt>
|
----
|-
|Bullet list
|
* one 
* two 
* three 
** three and one-third 
** three and two-thirds 
|
* one
* two
* three
** three and one-third
** three and two-thirds
|-
|Numbered list
|
# one 
# two<nowiki> </nowiki>spanning several lines<nowiki> </nowiki>without breaking the numbering 
# three 
## three point one 
## three point two 
|
# one
# two spanning several lines without breaking the numbering
# three
## three point one
## three point two
|-
| Mixture of bulleted and numbered lists
|
# one 
# two 
#* two point one 
#* two point two 
|
# one
# two
#* two point one
#* two point two
|-
|Definition list
|
;Definition 
:item 1 
:item 2 
|
;Definition
:item 1
:item 2
|-
|Preformatted text
|
  preformatted text is done with 
  a space at the 
  beginning of the line 
|
preformatted text is done with
a space at the
beginning of the line
|}

Notes: <references/>

== Paragraphs ==

MediaWiki ignores normal line breaks. To start a new paragraph, leave an empty line. You can also start a new line with the HTML tags <tt><nowiki> or </nowiki></tt>.

== HTML ==

Some [[w:HTML|HTML]] tags are allowed in MediaWiki, for example <tt><nowiki><code></nowiki></tt>, <tt><nowiki><div></nowiki></tt>, <tt><nowiki></nowiki></tt> and <tt><nowiki></nowiki></tt>.

''Admin tip'' : If you trust your users you can allow full HTML by setting <code>[[Manual:$wgRawHtml|$wgRawHtml]] = true;</code> in [[Manual:LocalSettings.php|LocalSettings.php]].

== Other formatting ==
[http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_Page_Help/Do-It-Yourself/Formatting_Text#Underlining More Formatting from Wikipedia]

Help:Contents

2011-01-10T16:06:30Z

Gpertea:

==Editing==
* [[Help:Editing|Editing pages]]
* [[Help:Formatting|Formatting]]
* [[Help:Links|Links]]

===Customizing===
* [[Help:Preferences|Preferences]]

Help:Editing

2011-01-10T16:04:45Z

Gpertea:

__NOEDITSECTION__
To edit a page, click on the '''edit''' or '''edit this page''' links at the top of the page. To edit an individual section, click on any of the floating '''<nowiki>[edit]</nowiki>''' links next to a section heading.

Once you've made a change, please click on preview to scan for any misspellings, punctuation errors, or other problems before saving the page.

== Wiki markup ==
The wiki markup is exceedingly simple once you get a firm grasp on it. Below you'll see a list of common effects, and how to do them.

=== Basic text formatting ===

{| border="1" cellpadding="2"
!width="1000"|What it looks like
!width="500"|What you type
|-
|
You can ''italicize text'' by putting 2
apostrophes on each side.

3 apostrophes will bold '''the text'''.

5 apostrophes will bold and italicize
'''''the text'''''.

(Using 4 apostrophes doesn't do anything special -- there are just '''' left over ones'''' that are included as part of the text.)
|<pre>
You can ''italicize text'' by putting 2
apostrophes on each side.

3 apostrophes will bold '''the text'''.

5 apostrophes will bold and italicize
'''''the text'''''.

(Using 4 apostrophes doesn't do anything
special -- there are just '''' left
over ones'''' that are included as part of the text.)
</pre>
|-
|
A single new line
generally has no effect on the layout.
These can be used to separate
sentences within a paragraph.
Some editors find that this aids editing
and improves the ''diff'' function
(used internally to compare
different versions of a page).

But an empty line
starts a new paragraph.

When used in a list, a newline ''does'' affect the layout ([[#lists|see below]]).
|<pre>
A single new line
generally has no effect on the layout.
These can be used to separate
sentences within a paragraph.
Some editors find that this aids editing
and improves the ''diff'' function
(used internally to compare
different versions of a page).

But an empty line
starts a new paragraph.

When used in a list, a newline ''does''
affect the layout ([[#lists|see below]]).
</pre>
|-
|
You can break lines 
without a new paragraph. 
Please use this sparingly.

Please do not start a link or ''italics'' or '''bold''' on one line and close it on the next.
|<pre>
You can break lines 
without a new paragraph. 
Please use this sparingly.

Please do not start a link or
''italics'' or '''bold''' on one line
and close it on the next.
</pre>
|-
|
You should "sign" your comments on talk pages: 
- Three tildes gives your user name: [[User:Fyren|Fyren]] 
- Four tildes give your user name plus date/time: [[User:Fyren|Fyren]] 10:06, 30 September 2006 (CDT) 
- Five tildes gives the date/time alone: 10:06, 30 September 2006 (CDT) 
|<pre>
You should "sign" your comments
on talk pages: 
- Three tildes gives your user
name: ~~~ 
- Four tildes give your user
name plus date/time: ~~~~ 
- Five tildes gives the
date/time alone: ~~~~~ 
</pre>
|}

=== HTML tags ===
You can use some '''HTML tags''' too. However, you should avoid HTML in favor of Wiki markup whenever possible. The following HTML tags are allowed by MediaWiki 1.7.1 (but not all may be supported by your browser):
*b, i, u, font, big, small, sub, sup, em, s, strike, strong, del, ins
*br, hr
*h1, h2, h3, h4, h5, h6
*cite, div, center, caption, span, p, tt, pre, code, var, blockquote
*ol, ul, li, dl, dt, dd
*table, tr, td, th
*ruby, rt, rb, rp
*!--, --

{| border="1" cellpadding="2"
!width="1000"|What it looks like
!width="500"|What you type
|-
|
Put text in a <tt>typewriter
font</tt>. The same font is
generally used for <code>
computer code</code>.
|<pre>
Put text in a <tt>typewriter
font</tt>. The same font is
generally used for <code>
computer code</code>.
</pre>
|-
|
<strike>Strike out</strike>
or underline text,
or write it 
in small caps.
|<pre>
<strike>Strike out</strike>
or underline text,
or write it 
in small caps.
</pre>
|-
|
Superscripts and subscripts:
X2, H2O
|<pre>
Superscripts and subscripts:
X2, H2O
</pre>
|-
|
<center>Centered text</center>
* Please note the American spelling of "center".
|<pre>
<center>Centered text</center>
</pre>
|-
|
<blockquote>
The '''blockquote''' command will indent
both margins when needed instead of the
left margin only as the colon does.
</blockquote>
|<pre>
<blockquote>
The '''blockquote''' command will indent
both margins when needed instead of the
left margin only as the colon does.
</blockquote>
</pre>
|-
|
Invisible comments to editors ()
only appear while editing the page.


* If you wish to make comments to the public, you should usually use the article's talk page.
|<pre>
Invisible comments to editors (&lt;!-- --&gt;)
only appear while editing the page.

</pre>
|}

=== Organizing your writing ===
{| border="1" cellpadding="2"
!width="1000"|What it looks like
!width="500"|What you type
|-
|
<div style="font-size:150%;border-bottom:1px solid #000000;">Section headings</div>

''Headings'' organize your writing into
sections. The wiki software can automatically
generate a table of contents from them.

<div style="font-size:132%;font-weight:bold;">Subsection</div>
Using more equals signs creates a subsection.

<div style="font-size:116%;font-weight:bold;">A smaller subsection</div>

Don't skip levels, like from two to four equals signs.

Start with 2 equals signs not 1 because 1 creates H1 tags which should be reserved for page title.
|<pre>
== Section headings ==

''Headings'' organize your writing into
sections. The Wiki software can automatically
generate a table of contents from them.

=== Subsection ===

Using more equals signs creates a subsection.

==== A smaller subsection ====

Don't skip levels,
like from two to four equals signs.

Start with 2 equals signs not 1
because 1 creates H1 tags
which should be reserved for page title.
</pre>
|- id="lists"
|
* ''Unordered lists'' are easy to do:
** Start every line with a star.
*** More stars indicate a deeper level.
*: Previous item continues.
** A newline
* in a list
marks the end of the list.
*Of course you can start again.
|<pre>
* ''Unordered lists'' are easy to do:
** Start every line with a star.
*** More stars indicate a deeper level.
*: Previous item continues.
** A newline
* in a list
marks the end of the list.
* Of course you can start again.
</pre>
|-
|
# ''Numbered lists'' are:
## Very organized
## Easy to follow
A newline marks the end of the list.
# New numbering starts with 1.

|<pre>
# ''Numbered lists'' are:
## Very organized
## Easy to follow
A newline marks the end of the list.
# New numbering starts with 1.
</pre>
|-
|
Here's a ''definition list'':
; Word : Definition of the word
; A longer phrase needing definition
: Phrase defined
; A word : Which has a definition
: Also a second one
: And even a third

Begin with a semicolon. One item per line;
a newline can appear before the colon, but
using a space before the colon improves
parsing.
|<pre>
Here's a ''definition list'':
; Word : Definition of the word
; A longer phrase needing definition
: Phrase defined
; A word : Which has a definition
: Also a second one
: And even a third

Begin with a semicolon. One item per line;
a newline can appear before the colon, but
using a space before the colon improves
parsing.
</pre>
|-
|
* You can even do mixed lists
*# and nest them
*# inside each other
*#* or break lines in lists.
*#; definition lists
*#: can be
*#:; nested : too
|<pre>
* You can even do mixed lists
*# and nest them
*# inside each other
*#* or break lines in lists.
*#; definition lists
*#: can be
*#:; nested : too
</pre>
|-
|
: A colon (:) indents a line or paragraph.
A newline starts a new paragraph. 
Often used for discussion on talk pages to 
show the flow of a conversation.
: We use 1 colon to indent once.
:: We use 2 colons to indent twice.
::: 3 colons to indent 3 times, and so on.
|<pre>
: A colon (:) indents a line or paragraph.
A newline starts a new paragraph. 
Often used for discussion on talk pages to 
show the flow of a conversation.

: We use 1 colon to indent once.
:: We use 2 colons to indent twice.
::: 3 colons to indent 3 times, and so on.
</pre>
|-
|
You can make horizontal dividing lines (----)
to separate text.
----
But you should usually use sections instead,
so that they go in the table of contents.
|<pre>
You can make horizontal dividing lines (----)
to separate text.
----
But you should usually use sections instead,
so that they go in the table of contents.
</pre>
|}

=== Links ===

You will often want to make clickable ''links'' to other pages.

{| border="1" cellpadding="2"
!width="1000"|What it looks like
!width="500"|What you type
|-
|
Here's a link to a page named [[program]].
You can even say [[program]]s
and the link will show up correctly.
|<pre>
Here's a link to a page named [[program]].
You can even say [[program]]s
and the link will show up correctly.
</pre>
|-
|
You can put formatting around a link.
Example: ''[[CBCBWiki]]''.
|<pre>
You can put formatting around a link.
Example: ''[[CBCBWiki]]''.
</pre>
|-
|
The ''first letter'' of articles is automatically
capitalized, so [[software]] goes to the same place
as [[Software]]. Capitalization matters after the
first letter.
|<pre>
The ''first letter'' of articles is automatically
capitalized, so [[software]] goes to the same place
as [[Software]]. Capitalization matters after the
first letter.
</pre>
|-
|
[[Software bugs]] is a page that doesn't exist
yet. You could create it by clicking on the link.
|<pre>
[[Software bugs]] is a page that doesn't exist
yet. You could create it by clicking on the link.
</pre>
|-
|
You can link to a page section by its title:

*[[Software#Notes]].

If multiple sections have the same title, add
a number. [[#Example section 3]] goes to the
third section named "Example section".
|<pre>
You can link to a page section by its title:

*[[Software#Notes]].

If multiple sections have the same title, add
a number. [[#Example section 3]] goes to the
third section named "Example section".
</pre>
|-
|
You can make a link point to a different place
with a piped link. Put the link
target first, then the pipe character "|", then
the link text.

*[[Software|Our software article]]
*[[Program#Notes|Program notes]]

Or you can use the "pipe trick" so that text in
parentheses does not appear.

*[[Notes (Software Tips)|Notes]]
|<pre>
You can make a link point to a different place
with a piped link. Put the link
target first, then the pipe character "|", then
the link text.

*[[Software|Our software article]]
*[[Program#Notes|Program notes]]

Or you can use the "pipe trick" so that text in
parentheses does not appear.

*[[Notes (Software Tips)|Notes]]
</pre>
|-
|
You can make an external link just by typing a URL:
http://www.cbcb.umd.edu

You can give it a title:
[http://www.cbcb.umd.edu CBCB Home Page]

Or leave the title blank:
[http://www.cbcb.umd.edu]
|
<pre>
You can make an external link just by typing a URL:
http://www.cbcb.umd.edu

You can give it a title:
[http://www.cbcb.umd.edu CBCB Page]

Or leave the title blank:
[http://www.cbcb.umd.edu]
</pre>
|-
|
Linking to an e-mail address works the same way:
mailto:someone@domain.com or
[mailto:someone@domain.com someone]
|
<pre>
Linking to an e-mail address works the same way:
mailto:someone@domain.com or
[mailto:someone@domain.com someone]
</pre>
|-
|
You can redirect the user to another page.
|<pre>
#REDIRECT [[Software]]
</pre>
|-
|
Category links do not show up in line
but instead at page bottom ''and cause the page to be
listed in the category.''
[[Category:Helping out]]

Add an extra colon to ''link'' to a category in line
without causing the page to be listed in the category:
[[:Category:Helping out]]
|<pre>
Category links do not show up in line
but instead at page bottom ''and cause the page to be
listed in the category.''
[[Category:Helping out]]

Add an extra colon to ''link'' to a category in line
without causing the page to be listed in the category:
[[:Category:Helping out]]
</pre>
|-
|
You can insert links to other specific wikis with an Interwiki link.
These will appear similar to regular wiki-links, but will direct the
browser to another wiki and display it's page on the provided topic.

A link to Wikipedia's [[Wikipedia:Indiana Jones|Indiana Jones]] article.

|<pre>
Links to Wikipedia, the WWW encyclopedia:
[[Wikipedia:Indiana Jones|Indiana Jones]]

</pre>
|}

===Just show what I typed===

A few different kinds of formatting will tell the wiki to display things as you typed them.

{| border="1" cellpadding="2"
!width="1000"|What it looks like
!width="500"|What you type
|-
|
<nowiki>
The nowiki tag ignores
[[wiki]] ''markup''.
It reformats text by
removing
newlines and multiple
spaces.
It still interprets special
characters: →
</nowiki>
|<pre>
<nowiki>
The nowiki tag ignores
[[wiki]] ''markup''.
It reformats text by
removing
newlines and multiple
spaces.
It still interprets special
characters: &rarr;
</nowiki>
</pre>
|-
|
<pre>
The pre tag ignores [[wiki]]
''markup''.
It also doesn't reformat
text.
It still interprets special
characters: →
</pre>
|<pre>
<pre>
The pre tag ignores [[wiki]]
''markup''.
It also doesn't reformat
text.
It still interprets special
characters: &rarr;
</pre>
</pre>
|-
|
Leading spaces are another way to preserve formatting.

Putting a space at the
beginning of each
line stops the text
from being
reformatted. It still
interprets [[wiki]]
''markup'' and special
characters: →
|<pre>
Leading spaces are another way
to preserve formatting.

Putting a space at the
beginning of each
line stops the text
from being
reformatted. It still
interprets [[wiki]]
''markup'' and special
characters: &rarr;
</pre>
|}

===Images and tables===

After uploading, just enter the filename, highlight it and press the "embedded image"-button of the edit toolbar.

This syntax will embed an image: '''<nowiki>[[Image:filename.png]]</nowiki>'''

See [[wikipedia:help:tables|Wikipedia's table help page]] for more information about table syntax.

{| border="1" cellpadding="2"
!width="1000"|What it looks like
!width="500"|What you type
|-
|
A picture, including alternate text:

[[Image:button_math.png|Square root button]]

You can put the image in a frame with a caption:
[[Image:button_math.png|frame|Square root button]]
|<pre>
A picture, including alternate text:

[[Image:button_math.png|Square root button]]

The image in a frame with a caption:
[[Image:button_math.png|frame|Square root button]]
</pre>
|-
|
A link to this Wiki's page for the image:
[[:Image:button_math.png]]

Or a link directly to the image itself:
[[Media:button_math.png]]
|<pre>
A link to this Wiki's page for the image:
[[:Image:button_math.png]]

Or a link directly to the image itself:
[[Media:button_math.png]]
</pre>
|-
|
{| border="1" cellspacing="0" cellpadding="5" align="center"
! This
! is
|-
| a
| table
|-
|}
|<pre>
{| border="1" cellspacing="0"
cellpadding="5" align="center"
! This
! is
|-
| a
| table
|-
|}

</pre>
|}

===Templates===

'''Templates''' are segments of wiki markup that are meant to be copied automatically ("transcluded"/"included") into a page.
You add them by putting the template's name in <nowiki>{{double braces}}</nowiki>.

Some templates take ''parameters'', as well, which you separate with the pipe character.

See [http://en.wikipedia.org/wiki/Help:Template Wikipedia's template help page] for more information.

== Saving Changes ==
Once you've edited in your changes to a page, make sure to use the "show preview" button to view your changes. Try to read through your changes as it helps you notice any typos or accidental mistakes. Preferably, also double check any wiki links you've added in, in case they are pointing to either non-existent pages (unless intentional) or pointing to the wrong page.

Once you have verified your changes, fill in the "summary" text field. It is used to briefly explain the changes you have made. If there is already a bit of text inside it enclosed within /* and */, it means you're editing a section on the page. Simply add your explanation after that text to mark the section you added your changes to.

Before saving, there are two checkboxes that you can use. The first is to mark an edit as a minor edit. A minor edit is loosely defined as a change that does not really add new content to a page, such as fixing typos, rewriting sentences, or small formatting changes. Changes like non-trivial notes that identify behavior or adding tips are not minor edits. As a rule of thumb, if it's an edit that a user who re-reads the page doesn't really gain any new useful information, then it's a minor edit.

The second checkbox is for registered users who want to "watch" the page. If checked, the page will be added to that user's watch list, and any further changes will be bolded if the user views his or her own list.

Finally, click on "save page" to commit and save the changes.

User:Gpertea

2011-01-10T15:37:13Z

Gpertea:

Communal Software

2010-12-01T21:23:00Z

Gpertea: /* Core Software */

== Introduction ==
CBCB users do not have root access on their machines or the communal servers. Communal CBCB software is therefore typically installed in
/fs/sz-user-supported/
There are two primary subdirectories which differ by architecture. For the most part, 32bit software is installed in
/fs/sz-user-supported/Linux-i686/
while 64bit software is installed in
/fs/sz-user-supported/Linux-x86_64/
The appropriate subdirectory is typically dynamically chosen by embedding
/fs/sz-user-supported/`uname`-`uname -m`
in a user's path variables in their bashrc/tcshrc file.

Installing software to these directories and updating a user's path can be tricky. For this reason, many users choose to maintain specialty software in personal directories.

== Core Software ==

The latest versions of the most frequently used CBCB software is installed under
/fs/szdevel/core-cbcb-software/
and follows a directory structure similar to
/fs/sz-user-supported/
The software is installed and maintained by the cbcb-staff group.

Software list:
'''Name version'''
Bio::Perl
Biopython
Bowtie 0.12.7
Celera Assembler 6.1
gcc 4.5.1
GMap,GSnap 2010-07-27
Java (JRE only) 1.6.0_22
NCBI blast
Newbler 2.5
R
Samtools 0.1.9
SOAPdeNovo 1.04
Velvet 1.0.13

== Carl's World ==
In an attempt to solve many software installation related headaches for his lab members, Carl Kingsford has created an alternate environment called "Carl's World" which contains many programs and modules frequently used by his lab members. Little else is known about Carl's World, but rumor has it that if you ask nicely, he will let you in. It is important to note that Carl's World is designed and maintained specifically for use by Carl's lab members, and there are therefore many common and useful software packages not included in Carl's World. It may therefore be necessary to modify YOUR OWN bashrc file once you have joined, but be warned that attempting to modify Carl's World itself is a sure way to lose your membership.

== Planned Maintenance (Summer 2010) ==
The Pop lab is currently planning to update much of the communal software installed in sz-user-supported over the Summer of 2010. So far this list includes:
* [http://sourceforge.net/apps/mediawiki/amos/index.php?title=AMOS AMOS] -- Already installed
* [http://www.ncbi.nlm.nih.gov/staff/tao/URLAPI/blastall/index.html blastall 2.2.23] -- May not be worth upgrading from 2.2.18. Will look at release notes.
* [http://hmmer.janelia.org/ HMMer3] -- Installed.
** [http://pfam.sanger.ac.uk/ Pfam 24.0]
* PERL -- May attempt to standardize default version across servers.
** [http://www.bioperl.org/wiki/Main_Page BioPERL]
* Python -- May attempt to standardize default version across servers.
** [http://biopython.org/wiki/Main_Page BioPython]
*** [http://numpy.scipy.org/ NumPy]
*** [http://www.reportlab.com/software/opensource/ ReportLab]
Please feel free to contact Ted Gibbons at tgibbons@umd.edu to make suggestions or express concerns about tampering with the communal software installations and the corresponding paths in the communal CBCB bashrc file.