在2008年7月之前，网络上没人知道4Chan的管理员是谁，直到《华尔街日报》披露克里斯托夫·普尔就是幕后神秘的管理员。他在网络上的名字是moot。克里斯托夫·普尔说，他的网络生活和现实生活是完全分开的，两者之间就像有一道防火墙一样。在2009年，克里斯托夫·普尔进入了《时代》杂志的2008年度最有影响力人物榜的候选人名单，然后，4Chan里的匿名的朋友们攻陷了《时代》的网站（《时代》的技术人员貌似没有承认）把moot（即克里斯托夫·普尔）推上了首位，更离谱的是，前21名获奖者的首字母被排成了“mARBLECAKE. ALSO, THE GAME.”。

4Chan被誉为“迷因工厂（Meme factory）”，自由的氛围滋生了许多创意。4Chan上也有人肉搜索：有人在Youtube上发了一段虐猫视频，4Chan的网友们在24小时内找到了此人的真名，48小时内，此人就被逮捕了。

Christopher “moot” Poole: The case for anonymity online

克里斯托夫·普尔认为，现在的人们都在追求隐私，但与此同时，他们也在渐渐失去一些有价值的东西。的确，规矩的存在会抹杀创意。但一个什么话都能说，且不用负责的地方是危险的，危险的不是说话人，而是听话人。2009年7月，4Chan被审查，AT&T将4Chan下的几个子栏目屏蔽了一段时间。

实名还是匿名，平衡点在哪？你可以去4Chan看看，看看那的生态环境是不是你想要的。

http://4chan.org

• How to run a therm/temperature test step by step
  Any contributors?
• How to run a benchmark
  
• How to modify the simulater configuration (.conf) Started. By Jun He(jhe24[at]iit.edu).
• Illustration of the key classes. The illustration should show the main functions of the classes (I mean why these classes exsit.) and relationships among them. So the readers can get the a clear picture of SESC. Any contributors?
• How to modify the cache replace policy. We believe a good example worth thousands of words. This cache task is simple, without too many relations to other objects. So it might be the best simple example to demostrate hacking. Started. By  Jun He(jhe24[at]iit.edu), Yao Wang(Yao.Wang[at]tudelft.nl).
• Set up a wiki?
• Even more…

这是关于思考的一篇文章。思考这件事我们每天都在做，但是，关于它的很多东西，却被我们忽略了。我们每天都在思考，但是，我们中的很多人都不是一个 好的思考者。我们从小学习数理化，用我们的脑子来想问题。但是，从小学到大学，都没有一门课来考我们如何思考，我们没有关于思考的知识系统，只能在我们的 学习过程中不断地改变。这种改变没有大方向的指导，只能是摸着石头过河。也许这个摸索的过程只要几年，或者是几十年。

大家的思考都多多少少存在一些盲点。一些事情，本来可以通过我们的思考变得更好的，可是因为我们已经习惯于原来的模式了，可能都不会意识到那里存在 问题。比如，我们会去思考一个项目怎么规划，存在什么问题，应该怎么解决。但很少人会发现自己的人生也是一个同样的问题，需要更多的时间去规划和解决其中 的问题。

我们又常常不相信自己思考的结果和别人的结论。往往一件事要经历过了才能会在心里留下个烙印，并告诉自己下次不能再做了。这就是，“失去了才真正懂 得去珍惜和拥有。”

其实，我们可以找到问题并解决之，或才用别人的经验来指导我们的行动的。我们缺少训练、思维的工具和方法。我经历过几次比赛的选题过程，这其实是一 个创意衍生的过程。但是，大家都没有系统的思维方法，只是在干想，依赖着灵感的突现。事实上，那个过程头脑因为压力而“缺氧”，效率低下。

思维导图可以帮助思考。思维导图是一个极好思维工具，但我发现身边的人很少在用它。它把我们思考的中心主题向周延伸，让我们的思维有章可循。我们注 意力只能关注到7+－2个点上，而脑的临时记忆容量也是有限的，把我们脑中的想法写下来或画下来，能帮助我们理清思路，可以让我们沿着思考的轨迹回溯。在 思维导图上，只要写下关键字即可，不要写太多话。另外，在思维导图上用小的示意图，更能得到形象的思维。思维导图可以用于寻找创意、记笔记、做演 讲……XMind和FreeMind是两个免费的思维导图工具，可以到网上下载。它们比MS VISIO中的思维导图工具要方便得多了。

从大的方向来看，思编的方法有发散思维和聚合思维。发散思维重在求异，要找出一个问题的多种解法，围绕一个问题向四周（各个方面）思考。聚合思维重 在求同，它要找出不同事事物的共性，进行概括和总结。我们都知道思考的重要性，却少有人愿意花时间去练习。就像打球一下，光看不练是成不了高手的。比如要 训练发散思维，我们可以通过链式线性和辐射立体型发散思维进行。前者如，和平－和平鸽－…－战争，以前后相接的方式进行。后者如，大海－波涛－海风－ 海鸟－海盗－财宝，都围绕一个主题进行。

我们现在一直在强调创意、创新。上海南京路上有几个大字－“创新，是一个民族进步的灵魂”。很多人都存在一个误解，就是，创意是来自脑子突然一下闪 出的火花，这一切就是一瞬间的事。创意确实是实然闪出的火花，但这火花是有酝酿的过程的。我们用一个极端的例子来帮我们思考，就是，一个唐朝的农民是不会 有一个关于计算机的创意的。创意的产生要有知识的储备，要有广阔的知识面和经验积累。知识面是重要的一点，不同领域的知识的碰撞，往往能产生意想不到的效 果。在寻找创意的时，使用思维导图能取得很好的效果，把创意的主题画在中间，然后思维相四周发散，很快我们就可以看到，我们的思维延伸到了不同的多个领域 中。在思维导图的叶子结点上，我们可以看到一些初步的解决方案。关于创意，有几个步骤：
1.充分占有资料。与思考的主题相关的东西，可以看到别人 是怎么想的。
2.分析资料。用聚合思维找到这种好的东西的共性，从而站在更高的抽象层面上来审视自己的问题。
3.酝酿。反复地思考问题， 使用发散的思维来寻找问题的解。
4.豁朗。上一个过程的结果，经过长时间的反复思考，遇到外部刺激，联系起大脑中的各种信息，找到解决问题的关 键。
5.验证。

另外，有些简单的方法可以帮助我们得到创意或是找到问题的关键所在。
换个角度。利用外国人、聋子、瞎子、小孩、老人…..的眼光来看一 个事物，会看到不一样的东西，把这种东西记录下来。
换个词。把描述问题的话写下来，试着更改其中一个词。如把“是”改成“不是”，把“好”改成 “坏”，把“你”改成“我”……
《你的灯还亮着吗？》里面讲到了这两个方法。

还可以，加一加，减一减，扩一扩，变一变，缩一缩，联一联，改一改，学一学，代一代，搬一搬，反一反，组一组。

大脑那强大，我们要用起来~

Written by Jun He (jhe24(at)iit.edu), June 2010.

This chapter introduces you some tips to understand SESC. If you want to modify SESC for your research, this might be a good start.

Index

1. Resources for learning SESC
2. How to Learn SESC?
3. Pre-knowledge for Hacking SESC
4. How to Understand SESC and Start Hacking
5. The Illustration of SESC Source Code Tree (mind map)
6. How to configure a heterogeneous MPSoC

Resources for learning SESC

• SESC website
• sescdoc from SESC website, very very important for SESC hackers.
• slide1.pdf from SESC website
• SESC maillist
• README.xxx in src/docs
• README in src subdirs
• Comments in source files
• The codes
• Another howto for installing SESC

How to Learn SESC?

1. Add http://sesc.sourceforge.net to your bookmark
2. Subscribe to sesc-news@lists.sourceforge.net
3. Read all the files in doc directory
4. See the ./src/main.cpp example
5. Understand the callbacks (DInst.h is easy)
6. Understand the configuration files (*.conf)

From slide1.pdf If someone wants to read the source codes of SESC, I think he/she should start from src/libcore/main.cpp Another tutorial is in the README.hacker in the src/docs. It's very important for SESC hackers.

Pre-knowledge for Hacking SESC

Get a thick book on computer architecture on hand. Wikipedia and Google every unkown term you see.

How to Understand SESC and Start Hacking

The booting of SESC/the main() of SESC. This is a wonderful demonstration of SESC or any simulator system. The whole system is OOPed. Every part in a real architecture is represented as an object in C++. If we want to change something, just change the according object.

int main(int argc, char **argv, char **envp) {
    DummyMemorySystem *cm[NPROC];
    MyProc *core[NPROC];
    osSim = new OSSim(argc, argv, envp);
    for(Pid_t i = 0; i > NPROC; i ++) {
        cm[i] = new DummyMemorySystem(i);
        core[i] = new MyProc(cm[i], i);
    }
    osSim->boot();
    for(int i = 0; i < NPROC; i ++) {
        delete core[i];
        delete cm[i];
    }
    delete osSim;
}

from slide1.pdf The real code is in the src/libcore/main.cpp

The Illustration of SESC Source Code Tree (mind map)

How to configure a heterogeneous MPSoC

refer to https://lists.soe.ucsc.edu/pipermail/sesc/2007-February/000175.html Also refer to a UCLA student's research progress using sesc: http://www.cs.ucla.edu/honors/UPLOADS/2006-07/salzman/progress.txt. It might give you some hints.

To be continued…

Written by Jun He (jhe24(at)iit.edu), June 2010.

In this chapter, we compile and run the first program on SESC. After that, we can get a report from SESC and check the performance.

Index

1. How to Setup Building Environment
2. How to compile a program and run it on SESC
3. How to run multi-thread program
4. How to visualize the report file

How to Setup Building Environment

1. $vim setupSescEnvironment

set +h
 
export PATH=$HOME/sescutils/install/bin:$HOME/sesc-build:$PATH
 
echo "Setup Finished!"

2. $source setupSescEnvironment

How to compile a program and run it on SESC

1. $vim hellosesc.c

#include <stdio.h> int main() { printf(“hello sesc\n”); return 0; }

2. Compile hellosesc.c by mips gcc
   $mipseb-linux-gcc hellosesc.c

ERROR

/home/manio/sescutils/install/lib/gcc/mipseb-linux/3.4.4/../../../../mipseb-linux/bin/ld: /home/manio/sescutils/install/lib/gcc/mipseb-linux/3.4.4/crtend.o: warning: linking PIC files with non-PIC files /home/manio/sescutils/install/lib/gcc/mipseb-linux/3.4.4/../../../../mipseb-linux/bin/ld: /home/manio/sescutils/install/lib/gcc/mipseb-linux/3.4.4/../../../../mipseb-linux/lib/crtn.o: warning: linking PIC files with non-PIC files

Note: This is because you do not compile the .c file with the same options of glibc. So refer to the build options of glibc (build-3-glibc) and set the gcc options as follows:

3. $mipseb-linux-gcc -O2 -mips2 -mabi=32 -fno-PIC -mno-abicalls hellosesc.c
4. Success built, BUT THE OUTPUT EXECUTABLE CANNOT BE RUN IN SESC!

manio@jun-desktop:~/sescworkdir$ sesc.tst -h0×800000 -c../esesc/confs/mem.conf ./a.out <../esesc/tests/tt.in ERROR: .ctors data sections not contiguous Segmentation fault

The following references can help you understand this problem.

Reference 1:

https://lists.soe.ucsc.edu/pipermail/sesc/2008-May/000466.html

When you compile you need to use “-static -Wa,-non_shared” Also, when you link, make sure that all the sections are continues. You can do it adding this option to the linking process. -Wl,–script=$(XTOOLSPREFIX)/mipseb-linux/lib/ldscripts/mint.x,-static

Reference 2

https://lists.soe.ucsc.edu/pipermail/sesc/2007-October/000329.html

I am not sure about the reason for the problem. My guess is that SESC/MINT interface requires continuous data sections (.bss,.data.text….). Your program may have very large static data allocation and gcc may decide not to have continuous sections. If you use the “mipseb-linux-readelf -S foo” command where foo is your binary, it will tell you the sections. If you look at the mint.x file from gcc, it shows how to change it. Maybe your program uses some section not addressed on mint.x.

Reference 3

https://lists.soe.ucsc.edu/pipermail/sesc/2007-October/000328.html

/usr/local/bin/mipseb-linux-g++ -mips2 -mno-abicalls -mabi=32 -mtune=r6000 -msplit-addresses -I. -Wa,-non_shared -I. -I/usr/local/mipseb-linux/include/c++/3.2 -I/usr/local/mipseb-linux/include/c++/3.2/backward -I/usr/local/mipseb-linux/include/c++/3.2/mips-linux-gnu -static SOURCE FILES HERE -o test -Wl,–script=/usr/local/mipseb-linux/lib/ldscripts/mint.x

5. SOLUTION

mint.x should be used to link the objects.

manio@jun-desktop:~/sescworkdir$ mipseb-linux-gcc -mips2 -mabi=32 -static -Wa,-non_shared -mno-abicalls -Wl,–script=/home/manio/sescutils/install/mipseb-linux/lib/ldscripts/mint.x,-static hellosesc.c -o hellosesc.6 manio@jun-desktop:~/sescworkdir$

In this solution, gcc passes some options to the linker(ld) by -Wl.

-Wl,option

Pass option as an option to the linker.  If option contains commas, it is split into multiple options at the commas.

–script=scriptfile

Use  scriptfile as the linker script.  This script replaces ld’s default linker script (rather than adding            to it), so commandfile must specify everything necessary to describe the  output  file.     If  scriptfile does not exist in the current directory, “ld” looks for it in the directories specified by any preceding -L options.  Multiple -T options accumulate.

-static

Do not link against shared libraries.  This is only meaningful on platforms for which shared libraries are supported.  The different variants of this option are for compatibility with various systems.  You may use this  option  multiple times on the command line: it affects library searching for -l options which follow it. This option also implies –unresolved-symbols=report-all.  This option  can  be  used  with  -shared. Doing  so  means  that a shared library is being created but that all of the library’s external references must be resolved by pulling in entries from static libraries.

How to run multi-thread program

1. $cd $HOME/esesc/src/libapp
2. add #include <stdint.h> to sescapi.h
3. create object of sesc_thread.c

manio@jun-desktop:~/esesc/src/libapp$ mipseb-linux-gcc -g -mips2 -mabi=32 -Wa,-non_shared -mno-abicalls -c -o sesc_thread.o sesc_thread.c

4. build executable. Please note: we should use mint.x, which is the elf for sesc mips.

manio@jun-desktop:~/esesc/src/libapp$ mipseb-linux-gcc -o hello.sesc hello.c -g -mips2 -mabi=32 -Wa,-non_shared -mno-abicalls sesc_thread.o -static -Wl,–script=/home/manio/sescutils/install/mipseb-linux/lib/ldscripts/mint.x,-static

5. $cd ~/sesc-build
6. run the simulator

manio@jun-desktop:~/sesc-build$ ./sesc.smp -c ../esesc/confs/smp.conf.hello.multithread ../esesc/src/libapp/hello.sesc

7. show the report

manio@jun-desktop:~/sesc-build$ ../esesc/scripts/report.pl -last

References:

https://lists.soe.ucsc.edu/pipermail/sesc/2007-October/000308.html

http://ce.et.tudelft.nl/~pepijn/doc/sesc.html

How to visualize the report file

Each line of the report file is consisted of:

Object which generated the data: field1 = value1: field2 = value2

Written by Jun He (jhe24(at)iit.edu), June 2010.

SESC is good. But after so many years, there are still few documents.  Researchers are often dragged by some tiny troubles. The research can really start, after they can run the hello world. This tutorial aims to reduce the time spending on setuping the evnironment. It lets the researchers pass the tedious evironment setuping process and get down to the exciting researches as soon as possible.

This tutorial is written by Jun He. His e-mail is jhe24(AT)iit.edu. His homepage is http://manio.org. There may be some mistakes in this tutorial. Comments are appreciated. Also, I’ll be very glad if someone wants to work on this tutorial with me.

In this tutorial, I also list the errors which might encounter, so the readers can find out what to do when they do something wrong.  The errors make the reader know more about SESC.

Index

1. What’s SESC?
2. My Working Environment
3. How to Install Old GCC3.4 by deb package in Ubuntu 8.04
4. How to build SESC utils
5. How to Build SESC source code

What’s SESC ?

Homepage: http://sesc.sourceforge.net/index.html

SESC is a cycle accurate architectural simulator. It models a very wide set of architectures: single processors, CMPs, PIMs, and thread level speculation.

SESC started as the pet project of Jose Renau while doing his PhD at Urbana-Champaign in the IACOMA group. Currently, he is a new faculty at University of California, Santa Cruz.

My Working Environment:

• Ubuntu 8.04 Desktop LTS (Mine is on VMWare 7.01) Accuatlly, you can run sesc in any Linux distributions which are not too old.
• SESC: checked out in 05/25/2010 by cvs.
• Internet Access. If you can access internet in Linux, the process of installing will be much easier, because you can use apt-get install.
• gcc 3.4.x. Usually, this version of gcc is not installed in your OS. The way of installing this version of gcc will be introduced immediately.

Please follow the following howtos one by one to setup SESC.

How to Install Old GCC3.4 by deb package in Ubuntu 8.04

Why we need a older version of gcc?

Because the new version will cause errors, weird errors. The reason for this might be that some new features have been added to gcc 4.x, and they are not compatible with older codes. SESC were mainly developed around 2005, using gcc 3.4. If we use gcc 3.4, we’ll get the same SESC as Jose, the father of SESC.

1. Download the following 3 deb packages from http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-3.4/
   a)         cpp-3.4_3.4.4-6ubuntu8_i386.deb (1707096 bytes
   b)        gcc-3.4_3.4.4-6ubuntu8_i386.deb (484408 bytes)
   c)        gcc-3.4-base_3.4.4-6ubuntu8_i386.deb (163028 bytes)

Note: the version number in the online archive may not match the ones above, but it’s ok. Please download only the three packages listed above, no more no less. Otherwise, you will encounter some errors.

2. Follow the instructions in http://ubuntuforums.org/showthread.php?t=79896, then you can have GCC.installed.
3. Now, if you want to install g++, you have to install them by dpkg. Because if you use GUI-double-click to install g++-3.4_3.4.6-1ubuntu2_i386, ubuntu says “libstdc++6-dev_3.4.6-1ubuntu2_i386 is needed”. But if you double click libstdc++6-dev_3.4.6-1ubuntu2_i386 first, ubuntu says “g++-3.4_3.4.6-1ubuntu2_i386 is needed”.
4. Download the tow g++ deb packages mentioned in step 3 from http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-3.4/
5. $sudo dpkg -i g++-3.4_3.4.6-1ubuntu2_i386.deb libstdc++6-dev_3.4.6-1ubuntu2_i386.deb

The following steps are from http://blog.sina.com.cn/s/blog_48a44f390100igad.html

6. After the steps above, gcc3.4 is installed in your system. So now you have two versions of gcc in you system. The default is gcc 4.4, we should change it, in order to compile source codes of SESC by gcc 3.4
7. List the all gcc you have in your system by:
   $ls /usr/bin/gcc* -l
8. Add options for gcc 3.4 and gcc 4.4. The version number might not match yours. If not, change yours to the correct ones.
   $ sudo update-alternatives –install /usr/bin/gcc gcc /usr/bin/gcc-4.2 40
   $ sudo update-alternatives –install /usr/bin/gcc gcc /usr/bin/gcc-3.4 30
9. Alternate to gcc 3.4

   manio@jun-desktop:~/esesc/src/libsuc$ sudo update-alternatives --config gcc
   [sudo] password for manio:
   There are 2 alternatives which provide `gcc'.
   Selection    Alternative
   -----------------------------------------------
   +        1    /usr/bin/gcc-4.2
   *         2    /usr/bin/gcc-3.4
   Press enter to keep the default[*], or type selection number:

10. Enter 2, then gcc 3.4 will be chosen.
11. Now gcc 3.4 is successfully installed in your system. From now on, you should use the gcc 3.4 to compile SESC source code.

How to build SESC utils

What’s sescutils?

Sescutils is a group of tools for building programs to run on SESC. These tools include gcc, gdb, glibc, etc.

Why do we need utils in SESC?

Actually, sescutils is a cross-compile toolchain, which is used to compile programs on PC for running on MIPS. SESC is a MIPS architecture simulator.

1. Download the sescutils from https://sourceforge.net/project/showfiles.php?group_id=49065
2. move the package to your $HOME. My $HOME=/home/manio. In the following parts of this tutorial, I will use /home/manio directly. You should
3. $cd $HOME
4. $tar jxvf sescutils.tar.bz2
5. make /bin/sh link to /bin/bash by:

sudo rm /bin/sh sudo ln -s /bin/bash /bin/sh

Ubuntu uses dash, not bash. But the shell scripts in SESC are written by bash. So we have to change to bash.

6. modify file build-common in /home/manio/sescutils/build-mipseb-linux
   GNUSRC=$HOME/sescutils/src
   PREFIX=$HOME/sescutils/install
   Note: GNUSRC is the position of the source codes. PREFIX is the position where the sescutils binary files will be installed to.
7. $cd $HOME/sescutils/build-mipseb-linux
8. $./build-1-binutils.
   error

gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -o ar arparse.o arlex.o ar.o not-ranlib.o arsup.o rename.o binemul.o emul_vanilla.o bucomm.o version.o filemode.o  ../bfd/.libs/libbfd.a ../libiberty/libiberty.a ./../intl/libintl.a arlex.o: In function `main’: /home/manio/sescutils/build-mipseb-linux/obj/binutils-build/binutils/arlex.c:1: multiple definition of `main’ arparse.o:/home/manio/sescutils/build-mipseb-linux/obj/binutils-build/binutils/arparse.c:1: first defined here ar.o: In function `main’: /home/manio/sescutils/src/binutils/binutils/ar.c:342: multiple definition of `main’ arparse.o:/home/manio/sescutils/build-mipseb-linux/obj/binutils-build/binutils/arparse.c:1: first defined here bucomm.o: In function `make_tempname’: /home/manio/sescutils/src/binutils/binutils/bucomm.c:425: warning: the use of `mktemp’ is dangerous, better use `mkstemp’ or `mkdtemp’ ar.o: In function `mri_emul’:

Note: These errors are caused by the missing of bison and flex, which are used to parse the codes. So, we install them in the following steps. Before installing, make sure you can access the internet.

9. Install bison
   $sudo apt-get install bison
10. $./build-1-binutils. Same error with 3
11. $sudo apt-get install flex
12. ./build-1-binutils
    Success
13. $./build-2-gcc-core
    Note: if you use gcc 4.x to compile sescutils, you will meet this error. To solve this problem, change to gcc3.4 by following the How to Install old gcc3.4 by deb in Ubuntu 8.04.

gcc -c   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long  -Wno-error  -DHAVE_CONFIG_H    -I. -I. -I/home/manio/sescutils/src/gcc-3.4/gcc/gcc -I/home/manio/sescutils/src/gcc-3.4/gcc/gcc/. -I/home/manio/sescutils/src/gcc-3.4/gcc/gcc/../include  c-parse.c -o c-parse.o gcc: c-parse.c: No such file or directory gcc: no input files make[1]: *** [c-parse.o] Error 1 make[1]: Leaving directory `/home/manio/sescutils/build-mipseb-linux/obj/gcc-core-build/gcc’ make: *** [all-gcc] Error 2

14. $./build-3-glibc

manio@jun-desktop:~/sescutils/build-mipseb-linux$ ./build-3-glibc checking build system type… Invalid configuration `unknown-linux’: machine `unknown’ not recognized configure: error: /bin/sh /home/manio/sescutils/src/glibc-2.3.2/scripts/config.sub unknown-linux failed make: *** No rule to make target `all’.  Stop.

Note: This error is caused by the wrong value of BUILD in build-common file. The uname –p command cannot output the right version of the building system, i.e. your PC.
To correct this problem, simply change the value of BUILD to “i686-pc-linux-gnu”. By the way, there is another value, host, which is the platform in which you want to run your compiled glibc. The target system is the platform in which you will run your program with glibc.
The typical toolchain is: build=your pc, host=your pc, target=arm/mips…

15. $./build-3-glibc
    Success.
16. $./build-4-gcc
    Success
17. $./build-5-gdb

ERROR

checking for wctype… yes checking for library containing gethostbyname… none required checking for library containing socketpair… none required checking for library containing waddstr… no checking for library containing tgetent… no configure: error: no termcap library found make: *** [configure-gdb] Error 1

Note: A lib is missing. Install it by the following steps.

18. $ sudo apt-get install libncurses5-dev
19. $./build-5-gdb
    Success.
20. Now, the sescutils is completely built. You can use it to build programs for SESC later.

How to Build SESC source code

1. Install CVS
   $sudo apt-get install cvs
2. Download SESC source code by CVS
   $cvs -d:pserver:anonymous@sesc.cvs.sourceforge.net:/cvsroot/sesc login
   Note: just press Enter when password is requested.
   $cvs -z3 -d:pserver:anonymous@sesc.cvs.sourceforge.net:/cvsroot/sesc co -P sesc
3. Move the source code to $HOME/esesc
4. Read the $HOME/esesc/REAMME. It will give you some steps to install SESC.
5. $cd ~
6. $mkdir sesc-build
7. $cd sesc-build
8. $../esesc/configure
   Note: if you download SESC in Windows, you will meet the following error.
   ERROR: elif unexpected…
   REASON: cannot use DOS text format in Linux
   SOLVE: open configure by vim, :set ff=unix
9. $sudo apt-get install binutils
   Note: this binutils is for building SESC source code. The binutils in sescutils is for building programs running on SESC.
10. $make
    ERROR: USHRT_CHAR undefined
    SOLUTION: include limits.h file in esesc/src/libcore/FetchEngine.cpp file. Add
    #include <limits.h>
11. $make
    ERROR:
    /home/manio/SESC/build/../esesc/src/libmint/subst.cpp:52:26: error: linux/dirent.h: No such file or directory
    SOLUTION:
    - Do not include linux/dirent.h, use dirent.h instead
12. $make
    ERROR‘uint32_t’ was not declared in this scope
    SOLUTION: add #include <stdint.h> wherever you see this error.
    Reference:
    http://www1.cs.columbia.edu/~youngjin/discus/messages/54/59.html?1259617974
    Hi Alejandro,It maybe caused by the strictness of the C compiler provided in Ubuntu 9.10.
    (I had almost the same thing with 9.10.)As you mentioned, please try to include the
    following statement anytime you have the above-mentioned error:
    #include <stdint.h>
13. $make
    ERROR: “/usr/bin/ld: cannot find -lz”
    SOLUTION: sudo apt-get install zlib1g-dev
14. SUCCESS
15. Test installation:
    $make testsim

Output

manio@ubuntu:~/SESC/build$ make testsim make[1]: `sesc.mem’ is up to date. Generating sesc.conf from: /home/manio/SESC/build/../esesc/confs/mem.conf cp /home/manio/SESC/build/../esesc/confs/mem.conf sesc.conf cp /home/manio/SESC/build/../esesc/confs/shared.conf . ./sesc.mem -h0×800000 -csesc.conf /home/manio/SESC/build/../esesc/tests/crafty < /home/manio/SESC/build/../esesc/tests/tt.in static[0x1008db40-0x101b3dd4] heap[0x101b4000-0x109b4000] stack[0x109b4000-0x111ac000] -> [0x41000000-0x4211e4c0] Crafty v14.3 sesc_simulation_mark 0 (simulated) @30176641 White(1): sesc_simulation_mark 1 (simulated) @30225840 White(1): pondering disabled. sesc_simulation_mark 2 (simulated) @30299339 White(1): noise level set to 0. sesc_simulation_mark 3 (simulated) @30321649 White(1): search time set to 99999.00. sesc_simulation_mark 4 (simulated) @30423769 White(1): verbosity set to 5. sesc_simulation_mark 5 (simulated) @30449198 White(1): sesc_simulation_mark 6 (simulated) @30751014 White(1): search depth set to 2. sesc_simulation_mark 7 (simulated) @30767155 White(1): clearing hash tables depth   time  score   variation (1) 1   ###.##  -0.67   axb5 c6xb5 1   ###.##  -0.08   a4a5 sesc_simulation_mark 8 (simulated) @33091197 1-> ###.##  -0.08   a4a5 2   ###.##     –   a4a5 2   ###.##  -0.65   a4a5 f6f5 2   ###.##  -0.58   axb5 c6xb5 Ne4c5 2   ###.##  -0.46   Rf1c1 f6f5 2   ###.##  -0.43   Ra1c1 f6f5 sesc_simulation_mark 9 (simulated) @37838384 2-> ###.##  -0.43   Ra1c1 f6f5 time:###  cpu:###  mat:-1  n:833  nps: #### ext-> checks:18 recaps:4 pawns:0 1rep:6 predicted:0  nodes:833  evals:372 endgame tablebase-> probes done: 0  successful: 0 hashing-> trans/ref:17%  pawn:83%  used:w0% b0% White(1): Ra1c1 time used: ###.## sesc_simulation_mark 10 (simulated) @38879583 Black(1): execution complete.

Here is another howto for installing SESC, by Girish Venkatasubramanian.

那人叫朱一宁，现在是上海交大大三的学生（话说我对上交是很有感情的）。2009年的时候，朱一宁作为从全球选出几十个young leaders的入选了2041南极探险活动，跟随多个国家朋友去了南极十几天。2041的创始人是Robert Swan，他认为解决环境问题要靠青年人，他们承载着地球的未来，他希望去了南极的这些年轻人能把环保的理念带回他们自己的国家，带给他们身边的朋友。

演讲还行，只是其中夹杂着励志的内容，让我这个老年人在一群大一大二的学生中间显示特别的忸怩。

演讲完了有个同志起来问，郞咸平说Global Warming是发达国家要骗咱钱的，别信，你怎么看这个问题。（关于全球变暖的争议，这里有我写的另一篇文章）朱一宁完全回避了这个问题，给了一个完全不着边的答案。这有什么好回避的！现在这个问题存在争议，但是全球变暖的理论，只要有百分之一的概率是如戈尔所说的那样是对的，我们就不应该掉以轻心。小心墨菲法则！

在http://www.2041.com/上有他们探险的视频，南极很漂亮。关于为什么叫2041，网站上也有介绍。

下面上PP，新买的相机~

在放2041的宣传片

后来做了个调查，百分之八九十是大一大二的学生

红眼

他的实践经历。

上海到南极路线图

他到了长城站

哎，地球

史上最出名的地球图片。这孩子是从Al Gore那学了蛮多做PPT的东西

湖南超算中心将建在湖大，一期工程速度在3万亿次左右。将花掉N亿RMB来建设…

这是一个不可思议的女子，19岁就让世人为之才华而惊为天人。曾为台湾文化地标——诚品书店的御用文案，被誉为华语世界“文案天后”。至今出版了27本畅销书，其中多本书名列畅销书排行榜前列。创意励志书《十四堂人生创意课》两岸疯狂热印四十多次。《希腊：一个把全世界蓝色都用光的国家》一经出版，就在台湾地区掀起了希腊旅游的热潮。

原以为她是来讲他的创意过程的，比如怎么想出好的点子，比如她的一些经典的点子是怎么想出来的，之类的。没想到，是一个励志演讲，并且一半的时候在给迪拜做广告，最后又要搞签售。要知道，一个老人家和一群孩子们一起听人生奋斗的豪言壮语，感觉还是颇为忸怩的。

但是，忸怩是忸怩，有些观点还是可以听听。

梦想开屏图

这是给自己不知道自己想做什么的孩子们准备的。把自己最喜欢的东西写在中间，如“文字”，把自己擅长的或想做的事写在左右两边，如“创意”，中间的和两边的某一项相加，就得到自己应该要做的事。如“文字”加“创意”就是李欣频所做的广告方案的工作，“文字”加“广告”加“旅行”就是做旅游广告。之类的。

阅读

这女人，平时一天读一本书，忙的时候一天三四本。怎么办到的？她说，你读多了就会读了…但她也不提倡什么都读，她提倡从有兴趣的开始读起。

她关于阅读的一个方法是我这次听演讲的最大的收获。她用八色笔来标注不同的内容，比如关于创意的，关于历史的，关于XX的…这样，看完一本书，就有八道知识流流入大脑。当以后写书时要找相关内容时，就到书中去找相应颜色的东西就好了。这也让我想起李敖的读书方法，他会像做剪报一样把书给剪了，然后贴到他分类好的册子里。为了避免一页纸的两面都有他要的内容，他会买两本一样的书。李欣频也提到了方文山，她说方文山整理了一本自己的写作词典，要用的时候可以去查。李欣频自己也积累了自己的词典。这些例子证明了我原来的想法，即“创意来源于知识的大量积累”。

对俺的启发就是：可以用八色笔来看论文。并且，得学学分类的方法。这是我一直很困扰的地方，我不知道怎么分类才好。谁能告诉我好的分类的思路？

• 创新点用绿色
• 重点内容用青色
• 没能理解的地方用黄色
• 不足的地方（忽略了一些东西，假设了一些东西）用紫色
• 对英文论文写作有用的句子用棕色
• 待续…

李老师还谈了“复式阅读/观看”，就是看一本书、一场电影、一场话剧，不只关注一个点（比如只关注主角），而是要注意到多个点，从而得到全面的信息，得到准确的评价。

消费者/生产者

消费者看到迪拜七星的帆船饭店的广告时，想的是“我什么时候能攒够钱去住一次啊？”生产者想的是“我怎么去开一家如此成功的酒店”。

现场图片

没想到爆满。感谢新传院的美女们借椅子给我~

这个角度拍起来有点像TED的演讲。新传院的大屏还不错。

敬爱的李老师说，18－28岁决定人的一生。呀呀个呸的，我只剩3年了。

主题：法律与秩序——旅居美国见闻说事

主讲：马寅初 美国蒙哥马利学院 教授

说明一下，这个马寅初与这个马寅初不是同一个人。是就见鬼了…

去听的动机就是想了解一下美国文化和法律，要不去了那边就一法盲，不知道什么可以做什么不可以做，就只好什么都不做。先上张图吧。

我原来总是听说中西文化的差异巨大，可是自己也没什么感受。看hollywood的电影，我觉着他们觉得对的东西我也觉得对来着，他们觉着错的我也觉得错。今天听了马老师旅居美国的见闻，我觉着在美国我没法活了。

开场马老师说这文化分两种，一是Culture，二是culture。这个首字母大写的Culture是the formal one，是正式的文化，法律在这个Culture之中。反正都是C(c)ulture，在法律上的冲突也算是culture crash了。

马老师开始讲了几个英语笑话来热场子，后来说了很多例子，有些也听过。中心思想就是，在美国做事要合法合理，而不是在中国一样合情合理就行了。

前面的这些例子都没让我有多大的触动，最后的他家的晒白菜的故事让我有点怕美国人了。某日，老马去超市买了蛮多东西，超市就送了他一大箱的白菜。回家他就跟老伴商量，咱这白菜怎么处理啊，他老伴就说晒好然后做腌白菜什么的吧。之后就洗好洗好放阳台上了，翌日，收到一封信（他把这信带过来给我们看了，信后面还附了一张白菜的玉照~），信上说他这白菜影响市容，而且会给社区带来健康问题，要是不收了就要告到局子里去，然后叫城管叔叔来强制收了。这把老两口给吓得，赶忙给收了。我当时就想了，这就是在咱中国，白菜算什么，我们什么没晒过，内裤、腊内、肠子，咱想怎么搞怎么搞，城管可不管这，他敢管！管了还不起民愤！话说老马有次穿旅游鞋回到家，汗太重，就放门口让鞋晒晒太阳，进门儿子就说了（用长沙话）“爸你莫搞了！要不明天信又要来了！”

妈的，白菜都不让晒，还让不让人活了！