'프로그램 사용' 카테고리의 글 목록 (136 Page)

'프로그램 사용'에 해당되는 글 2263건

2014.12.12 distcc 로 valgrind-3.6.1 컴파일 실패?
2014.12.11 VNC web 버전?
2014.12.09 distcc 작동모드
2014.12.08 ccache & distcc
2014.12.08 distcc on ubuntu
2014.12.05 busybox su가 안될 경우
2014.12.03 gimp를 이용하여 RGB 를 BGR로 변경하기
2014.11.24 apache2 2.4.7 문서 경로 수정하기
2014.11.18 pulseaudio / ffmpeg esd protocol
2014.11.17 commit 전 svn add 한 파일 추가 취소하기/삭제하기/되돌리기

distcc 로 valgrind-3.6.1 컴파일 실패?

configure 상으로는 차이가 없으나

$ CC="distcc gcc" ./configure

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking whether to enable maintainer-specific portions of Makefiles... no

checking whether ln -s works... yes

checking for gcc... distcc gcc

checking whether the C compiler works... yes

checking for C compiler default output file name... a.out

checking for suffix of executables...

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether distcc gcc accepts -g... yes

checking for distcc gcc option to accept ISO C89... none needed

checking for style of include used by make... GNU

checking dependency style of distcc gcc... gcc3

checking whether distcc gcc and cc understand -c and -o together... yes

checking how to run the C preprocessor... distcc gcc -E

checking for g++... g++

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking dependency style of g++... gcc3

checking for ranlib... ranlib

checking for a sed that does not truncate output... /bin/sed

checking for ar... /usr/bin/ar

checking for perl... /usr/bin/perl

checking for gdb... /usr/bin/gdb

checking dependency style of distcc gcc... gcc3

$ ./configure

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking whether to enable maintainer-specific portions of Makefiles... no

checking whether ln -s works... yes

checking for gcc... gcc

checking whether the C compiler works... yes

checking for C compiler default output file name... a.out

checking for suffix of executables...

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ISO C89... none needed

checking for style of include used by make... GNU

checking dependency style of gcc... gcc3

checking whether gcc and cc understand -c and -o together... yes

checking how to run the C preprocessor... gcc -E

checking for g++... g++

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking dependency style of g++... gcc3

checking for ranlib... ranlib

checking for a sed that does not truncate output... /bin/sed

checking for ar... /usr/bin/ar

checking for perl... /usr/bin/perl

checking for gdb... /usr/bin/gdb

checking dependency style of gcc... gcc3

distcc 안되는 경우

make[3]: Entering directory `/mnt/disk1/home/minimonk/work/valgrind/valgrind-3.6.1/memcheck'

../coregrind/link_tool_exe_linux 0x38000000 distcc gcc -Wno-long-long -Wno-pointer-sign -fno-stack-protector -o memcheck-x86-linux -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -static -nodefaultlibs -nostartfiles -u _start -Wl,--build-id=none -m32 memcheck_x86_linux-mc_leakcheck.o memcheck_x86_linux-mc_malloc_wrappers.o memcheck_x86_linux-mc_main.o memcheck_x86_linux-mc_translate.o memcheck_x86_linux-mc_machine.o memcheck_x86_linux-mc_errors.o ../coregrind/libcoregrind-x86-linux.a ../VEX/libvex-x86-linux.a -lgcc

cc: gcc: 그런 파일이나 디렉터리가 없습니다

distcc[14875] ERROR: compile (null) on localhost failed

로컬 컴파일 되는 경우

make[3]: Entering directory `/mnt/disk1/home/minimonk/work/valgrind/valgrind-3.6.1/memcheck'

gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_x86_linux-mc_leakcheck.o -MD -MP -MF .deps/memcheck_x86_linux-mc_leakcheck.Tpo -c -o memcheck_x86_linux-mc_leakcheck.o `test -f 'mc_leakcheck.c' || echo './'`mc_leakcheck.c

mv -f .deps/memcheck_x86_linux-mc_leakcheck.Tpo .deps/memcheck_x86_linux-mc_leakcheck.Po

gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_x86_linux-mc_malloc_wrappers.o -MD -MP -MF .deps/memcheck_x86_linux-mc_malloc_wrappers.Tpo -c -o memcheck_x86_linux-mc_malloc_wrappers.o `test -f 'mc_malloc_wrappers.c' || echo './'`mc_malloc_wrappers.c

mv -f .deps/memcheck_x86_linux-mc_malloc_wrappers.Tpo .deps/memcheck_x86_linux-mc_malloc_wrappers.Po

gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_x86_linux-mc_main.o -MD -MP -MF .deps/memcheck_x86_linux-mc_main.Tpo -c -o memcheck_x86_linux-mc_main.o `test -f 'mc_main.c' || echo './'`mc_main.c

mv -f .deps/memcheck_x86_linux-mc_main.Tpo .deps/memcheck_x86_linux-mc_main.Po

gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_x86_linux-mc_translate.o -MD -MP -MF .deps/memcheck_x86_linux-mc_translate.Tpo -c -o memcheck_x86_linux-mc_translate.o `test -f 'mc_translate.c' || echo './'`mc_translate.c

mv -f .deps/memcheck_x86_linux-mc_translate.Tpo .deps/memcheck_x86_linux-mc_translate.Po

gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_x86_linux-mc_machine.o -MD -MP -MF .deps/memcheck_x86_linux-mc_machine.Tpo -c -o memcheck_x86_linux-mc_machine.o `test -f 'mc_machine.c' || echo './'`mc_machine.c

mv -f .deps/memcheck_x86_linux-mc_machine.Tpo .deps/memcheck_x86_linux-mc_machine.Po

gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_x86_linux-mc_errors.o -MD -MP -MF .deps/memcheck_x86_linux-mc_errors.Tpo -c -o memcheck_x86_linux-mc_errors.o `test -f 'mc_errors.c' || echo './'`mc_errors.c

mv -f .deps/memcheck_x86_linux-mc_errors.Tpo .deps/memcheck_x86_linux-mc_errors.Po

../coregrind/link_tool_exe_linux 0x38000000 gcc -Wno-long-long -Wno-pointer-sign -fno-stack-protector -o memcheck-x86-linux -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -static -nodefaultlibs -nostartfiles -u _start -Wl,--build-id=none -m32 memcheck_x86_linux-mc_leakcheck.o memcheck_x86_linux-mc_malloc_wrappers.o memcheck_x86_linux-mc_main.o memcheck_x86_linux-mc_translate.o memcheck_x86_linux-mc_machine.o memcheck_x86_linux-mc_errors.o ../coregrind/libcoregrind-x86-linux.a ../VEX/libvex-x86-linux.a -lgcc

머가 문제인지 모르겠으나..
아마도..(?) -lgcc로 gcc.a라던가 이런게 전송이 안되서 그런게 아닐까 추측이 된다.

ubuntu 12.04 기준
/usr/lib/gcc/i686-linux-gnu/4.6.3/libgcc.a 가 존재한다.
[링크 : http://askubuntu.com/questions/346377/cannot-find-lgcc-s]

아마도.. 두개의 시스템 gcc 버전이 상이하거나 아키텍쳐 상의 차이로
디렉토리가 달라 libgcc.a 의 경로를 찾지 못해 에러가 난 것으로 보인다.
즉.. distcc를 구성할때는 동일한 배포판, 동일한 버전으로 설치해야 사용이 용이할 것으로 보인다.

--

임시 파일은 /tmp에 생성된다.

/tmp$ ll

합계 804

drwxrwxrwt 8 root root 245760 12월 12 13:36 ./

drwxr-xr-x 23 root root 4096 6월 11 2014 ../

drwxrwxrwt 2 root root 4096 12월 12 10:38 .ICE-unix/

-r--r--r-- 1 root root 11 12월 12 10:37 .X0-lock

drwxrwxrwt 2 root root 4096 12월 12 10:37 .X11-unix/

-rw------- 1 distccd nogroup 315392 12월 12 13:36 ccIxjVed.s

-rw------- 1 distccd nogroup 0 12월 12 13:35 distcc_d37970ab.stderr

-rw-r--r-- 1 distccd nogroup 0 12월 12 13:35 distcc_d41570ab.stdout

-rw------- 1 distccd nogroup 225936 12월 12 13:35 distccd_c84770ab.i

-rw------- 1 distccd nogroup 0 12월 12 13:35 distccd_d70770ab.o

drwx------ 2 minimonk minimonk 4096 12월 12 10:38 keyring-ZMR3zZ/

drwx------ 2 minimonk minimonk 4096 12월 12 10:38 pulse-Gj2NwjL3C0so/

drwx------ 2 root root 4096 12월 12 10:37 pulse-PKdhtXMmr18n/

drwx------ 2 minimonk minimonk 4096 12월 12 10:38 ssh-vFvOqnIn1567/

-rw-rw-r-- 1 minimonk minimonk 0 12월 12 10:37 unity_support_test.0

[링크 : http://manpages.ubuntu.com/manpages/maverick/man1/distccd.1.html]

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

distcc-pump error (0)	2016.09.25
distcc 크로스 컴파일/커널 빌드 관련 (0)	2016.09.13
distcc 작동모드 (0)	2014.12.09
ccache & distcc (0)	2014.12.08
distcc on ubuntu (0)	2014.12.08

Posted by 구차니

VNC web 버전?

HTML5 / websocket을 이용한다는데
쓸만한지 클라이언트측 부하는 얼마나 걸릴지 체크할 필요는 있어보인다.

[링크 : http://stackoverflow.com/questions/3240633/web-based-vnc-client]
[링크 : http://kanaka.github.io/noVNC/]
[링크 : http://guac-dev.org/]
[링크 : https://chrome.google.com/webstore/detail/vnc%C2%AE-viewer-for-google-ch/...a] 크롬 확장

'프로그램 사용 > VNC' 카테고리의 다른 글

rfb(remote framebuffer) protocol (0)	2022.01.26
gconf-editor / ubuntu 14.04 LTS vino + VNC 접속불가 (0)	2015.03.22
VNC 5.0.5 (0)	2013.09.04
tsclient에 VNC 추가하기 (0)	2011.12.31
UVNC - Ultra VNC (2)	2010.11.26

Posted by 구차니

distcc 작동모드

gss-api (Generic Security Services Application Program Interface)
안전하게 소스코드를 공유해서 분산빌드 하는데 필요한 API

distcc 의 모드
plain - distcc를 구동하는 쪽(client)에서 pre-processor를 처리후 원격지에서 컴파일 / 어셈블리
결과물만 돌려받고 로컬에서 링킹
pump - 원격지(distcc 서버)에서 pre-processor / 컴파일 / 어셈블리까지 처리

ccache 와 pump동시 사용불가

구성방법은
distcc
ccache + distcc
pump + distcc 이나
include path 등의 문제로 인해 distcc 단독으로 사용하거나 ccache + distcc 정도가 무난할 것으로 생각된다.

HOW PLAIN (NON-PUMP) DISTCC WORKS

distcc only ever runs the compiler and assembler remotely. With plain distcc, the preprocessor must always run locally because it needs to access various header files on the local machine which may not be present, or may not be the same, on the volunteer. The linker similarly needs to examine libraries and object files, and so must run locally.

The compiler and assembler take only a single input file (the preprocessed source) and produce a single output (the object file). distcc ships these two files across the network and can therefore run the compiler/assembler remotely.

Fortunately, for most programs running the preprocessor is relatively cheap, and the linker is called relatively infrequent, so most of the work can be distributed.

distcc examines its command line to determine which of these phases are being invoked, and whether the job can be distributed.

HOW DISTCC-PUMP MODE WORKS

In pump mode, distcc runs the preprocessor remotely too. To do so, the preprocessor must have access to all the files that it would have accessed if had been running locally. In pump mode, therefore, distcc gathers all of the recursively included headers, except the ones that are default system headers, and sends them along with the source file to the compilation server.

In distcc-pump mode, the server unpacks the set of all source files in a temporary directory, which contains a directory tree that mirrors the part of the file system that is relevant to preprocessing, including symbolic links.

The compiler is then run from the path in the temporary directory that corresponds to the current working directory on the client. To find and transmit the many hundreds of files that are often part of a single compilation, pump mode uses an incremental include analysis algorithm. The include server is a Python program that implements this algorithm. The pump command starts the include server so that throughout the build it can answer include queries by distcc commands.

The include server uses static analysis of the macro language to deal with conditional compilation and computed includes. It uses the property that when a given header file has already been analyzed for includes, it is not necessary to do so again if all the include options (-I's) are unchanged (along with other conditions).

For large builds, header files are included, on average, hundreds of times each. With distcc-pump mode each such file is analyzed only a few times, perhaps just once, instead of being preprocessed hundreds of times. Also, each source or header file is now compressed only once, because the include server memoizes the compressed files. As a result, the time used for preparing compilations may drop by up to an order of magnitude over the preprocessing of plain distcc.

Because distcc in pump mode is able to push out files up to about ten times faster, build speed may increase 3X or more for large builds compared to plain distcc mode.

RESTRICTIONS FOR PUMP MODE

Using pump mode requires both client and servers to use release 3.0 or later of distcc and distccd (respectively).

The incremental include analysis of distc-pump mode rests on the fundamental assumption that source and header files do not change during the build process. A few complex build systems, such as that for Linux kernel 2.6, do not quite satisfy this requirement. To overcome such issues, and other corner cases such as absolute filepaths in includes, see the include_server(1) man page.

Another important assumption is that the include configuration of all machines must be identical. Thus the headers under the default system path must be the same on all servers and all clients. If a standard GNU compiler installation is used, then this requirement applies to all libraries whose header files are installed under /usr/include or /usr/local/include/. Note that installing software packages often lead to additional headers files being placed in subdirectories of either.

If this assumption does not hold, then it is possible to break builds with distcc-pump mode, or worse, to get wrong results without warning. Presently this condition is not verified, and it is on our TODO list to address this issue.

An easy way to guarantee that the include configurations are identical is to use a cross-compiler that defines a default system search path restricted to directories of the compiler installation.

See the include_server(1) manual for more information on symptoms and causes of violations of distcc-pump mode assumptions.

USING DISTCC WITH CCACHE

ccache is a program that speeds software builds by caching the results of compilations. ccache is normally called before distcc, so that results are retrieved from a normal cache. Some experimentation may be required for idiosyncratic makefiles to make everything work together.

The most reliable method is to set

CCACHE_PREFIX="distcc"

This tells ccache to run distcc as a wrapper around the real compiler. ccache still uses the real compiler to detect compiler upgrades.

ccache can then be run using either a masquerade directory or by setting

CC="ccache gcc"

As of version 2.2, ccache does not cache compilation from preprocessed source and so will never get a cache hit if it is run from distccd or distcc. It must be run only on the client side and before distcc to be any use.

distcc's pump mode is not compatible with ccache.

[링크 : http://distcc.googlecode.com/svn/trunk/doc/web/man/distcc_1.html]

[링크 : http://www.rasplay.org/?p=8567]
[링크 : http://en.m.wikipedia.org/wiki/Generic_Security_Services_Application_Program_Interface]

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

distcc 크로스 컴파일/커널 빌드 관련 (0)	2016.09.13
distcc 로 valgrind-3.6.1 컴파일 실패? (0)	2014.12.12
ccache & distcc (0)	2014.12.08
distcc on ubuntu (0)	2014.12.08
distcc - 네트워크 분산 컴파일 (2)	2010.03.04

Posted by 구차니

ccache & distcc

distcc는 단순하게(?) 분산 컴파일을 하는 녀석이고
ccache은 distcc시 컴파일 된 것을 캐싱해서 중복컴파일 하지 않도록 해준다는데.
아무튼 두개를 같이 쓰지 하나만 독립적으로 쓰는건 드물다고 한다.

그런데.. ccache -C와 같이 캐싱된걸 지우는게 가끔 필요한 것으로 봐서는
캐싱하고 문제가 생길 바에는 조금 느려도 매번 distcc만 사용해서 쌩으로 컴파일 하는게 나을지도 모르겠다.

[링크 : http://whatwant.tistory.com/421]
[링크 : https://ccache.samba.org/]

distcc pump mode
[링크 : http://distcc.googlecode.com/svn/trunk/doc/web/man/distcc_1.html]

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

distcc 크로스 컴파일/커널 빌드 관련 (0)	2016.09.13
distcc 로 valgrind-3.6.1 컴파일 실패? (0)	2014.12.12
distcc 작동모드 (0)	2014.12.09
distcc on ubuntu (0)	2014.12.08
distcc - 네트워크 분산 컴파일 (2)	2010.03.04

Posted by 구차니

distcc on ubuntu

서버측

$ sudo apt-get install distcc distccmon-gnome

$ sudo vi /etc/default/distcc

STARTDISTCC="true"

ALLOWEDNETS="192.168.1.5/24 127.0.0.1"

LISTENER="192.168.1.5 127.0.0.1"

NICE="10"

JOBS=""

ZEROCONF="false"

$ sudo service distcc start

* Starting Distributed Compiler Daemon: distccd [ OK ]

$ ps -ef | grep dist

distccd 18285 1 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

distccd 18286 18285 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

distccd 18289 18285 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

distccd 18290 18285 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

distccd 18291 18285 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

distccd 18292 18285 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

distccd 18293 18285 0 22:10 ? 00:00:00 /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 192.168.1.0/24 --allow 127.0.0.1 --listen 192.168.1.5 127.0.0.1 --nice 0

minimonk 18297 17675 0 22:10 pts/1 00:00:00 grep --color=auto dist

클라이언트 측

$ sudo apt-get install distcc
$ export DISTCC_HOSTS='192.168.1.5 localhost'
$ CC="distcc gcc" ./configure
$ make -j 8

[링크 : http://distcc.googlecode.com/svn/trunk/doc/web/man/distcc_1.html#TOC_22]

클라이언트에서 make -j 8 하니 서버에서 이렇게 cpu가 올라간다!! 우오오?!

valgrind를 컴파일 하는데 흐음..
네트워크 를 생각외로 많이 사용해 지는거 같기도 하고? (일단은.. 1MB/s 정도?)

gnome으로 된 distcc 모니터는 설정에 관련된 부분은 존재하지 않는다 -_-

$ sudo apt-cache search distcc

ccontrol - Compilation controller

distcc - Simple distributed compiler client and server

distcc-pump - pump mode for distcc a distributed compiler client and server

distccmon-gnome - GTK+ monitor for distcc a distributed client and server

dmucs - distributed compilation system for use with distcc

ubuntu-orchestra-modules-distcc - Modules mainly used by orchestra-management-server

$ distccmon-gnome

아무런 내용이 나오지 않는건.. 호스트 파일이 존재하지 않아서 이려나?

$ sudo distcc --show-hosts

distcc[18944] (dcc_parse_hosts) Warning: /home/minimonk/.distcc/zeroconf/hosts contained no hosts; can't distribute work

distcc[18944] (dcc_zeroconf_add_hosts) CRITICAL! failed to parse host file.

distcc[18944] (dcc_show_hosts) CRITICAL! Failed to get host list

$ distcc

distcc 3.1 i686-pc-linux-gnu

(protocols 1, 2 and 3) (default port 3632)

built Jul 17 2011 15:03:13

distcc comes with ABSOLUTELY NO WARRANTY. distcc is free software, and

you may use, modify and redistribute it under the terms of the GNU

General Public License version 2 or later.

Built with Zeroconf support.

Please report bugs to distcc@lists.samba.org

Usage:

distcc [COMPILER] [compile options] -o OBJECT -c SOURCE

distcc --help

Options:

COMPILER defaults to "cc"

--help explain usage and exit

--version show version and exit

--show-hosts show host list and exit

-j calculate the concurrency level from the host list.

Environment variables:

See the manual page for a complete list.

DISTCC_VERBOSE=1 give debug messages

DISTCC_LOG send messages to file, not stderr

DISTCC_SSH command to run to open SSH connections

DISTCC_DIR directory for host list and locks

Server specification:

A list of servers is taken from the environment variable $DISTCC_HOSTS, or

$DISTCC_DIR/hosts, or ~/.distcc/hosts, or /etc/distcc/hosts.

Each host can be given in any of these forms, see the manual for details:

localhost run in place

HOST TCP connection, port 3632

HOST:PORT TCP connection, specified port

@HOST SSH connection

USER@HOST SSH connection to specified host

--randomize Randomize the server list before execution

distcc distributes compilation jobs across volunteer machines running

distccd. Jobs that cannot be distributed, such as linking or

preprocessing are run locally. distcc should be used with make's -jN

option to execute in parallel on several machines.

$ vi /etc/default/distcc

# Defaults for distcc initscript

# sourced by /etc/init.d/distcc

#

# should distcc be started on boot?

#

# STARTDISTCC="true"

STARTDISTCC="false"

#

# Which networks/hosts should be allowed to connect to the daemon?

# You can list multiple hosts/networks separated by spaces.

# Networks have to be in CIDR notation, f.e. 192.168.1.0/24

# Hosts are represented by a single IP Adress

#

# ALLOWEDNETS="127.0.0.1"

ALLOWEDNETS="127.0.0.1"

#

# Which interface should distccd listen on?

# You can specify a single interface, identified by it's IP address, here.

#

# LISTENER="127.0.0.1"

LISTENER="127.0.0.1"

#

# You can specify a (positive) nice level for the distcc process here

#

# NICE="10"

NICE="10"

#

# You can specify a maximum number of jobs, the server will accept concurrently

#

# JOBS=""

JOBS=""

#

# Enable Zeroconf support?

# If enabled, distccd will register via mDNS/DNS-SD.

# It can then automatically be found by zeroconf enabled distcc clients

# without the need of a manually configured host list.

#

# ZEROCONF="true"

ZEROCONF="false"

$ vi /etc/distcc/hosts

# As described in the distcc manpage, this file can be used for a global

# list of available distcc hosts.

#

# The list from this file will only be used, if neither the

# environment variable DISTCC_HOSTS, nor the file $HOME/.distcc/hosts

# contains a valid list of hosts.

#

# Add a list of hostnames in one line, seperated by spaces, here.

+zeroconf

[링크 : https://wiki.debian.org/Distcc]
[링크 : http://whatwant.tistory.com/423]
[링크 : http://askubuntu.com/questions/107008/how-to-speed-up-compilation-of-ubuntu-apps-make-cmake-gcc]

[링크 : http://pointclouds.org/documentation/advanced/distcc.php]

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

distcc 크로스 컴파일/커널 빌드 관련 (0)	2016.09.13
distcc 로 valgrind-3.6.1 컴파일 실패? (0)	2014.12.12
distcc 작동모드 (0)	2014.12.09
ccache & distcc (0)	2014.12.08
distcc - 네트워크 분산 컴파일 (2)	2010.03.04

Posted by 구차니

busybox su가 안될 경우

su -c 해서 명령어를 실행시 아래와 같은 에러가 발생하는데

setresgid: Operation not permitted

해결책은..

$ chmod +s /bin/busybox

su는 SUID 명령으로 다른 사람의 퍼미션으로 변경이 가능해야 하는데
rwsr-sr-s가 아닌
rwxr-xr-x 이면 다른 사람으로 퍼미션으로 변경이 불가능 하므로
위와 같은 에러가 발생한다.

[링크 : https://forum.openwrt.org/viewtopic.php?id=30690]

'프로그램 사용 > busybox' 카테고리의 다른 글

sh: line 1: kill: root: no such pid (0)	2015.01.05
busybox tftp (0)	2013.06.18
busybox - setconsole (0)	2011.10.21
busybox ash "cannot open /dev/ttyAS1: no such device" (0)	2010.04.20
busybox ps는 BSD 스타일? (0)	2010.01.12

Posted by 구차니

gimp를 이용하여 RGB 를 BGR로 변경하기

채널 믹서로 해보려는데 잘 안되서

일단 BGR 이미지를 받아
Decompose 하고
다시
Compose 해서 채널을 Red -> Blue / Blue -> Red로 바꾸어 주면 된다.

Step 1. 색상 - 구성 - 분해

Step 2. 걍 귀찮으니 확인

Step 3. 색상 - 구성 - 구성

Step 4. 채널 표시에서 빨강 - 빨강 / 초록 - 초록 / 파랑 - 파랑을

Step 5. 채널 표시에서 빨강 - 파랑 / 초록 - 초록 / 파랑 - 빨강으로

Step 6. 쨔잔~

[링크 : http://docs.gimp.org/en/plug-in-decompose-registered.html]
[링크 : http://docs.gimp.org/en/plug-in-compose.html]

'프로그램 사용 > GIMP' 카테고리의 다른 글

gimp fisheye correction (0)	2015.10.20
gimp을 이용하여 색온도 바꾸기 (0)	2012.10.11
gimp 로고가 바꼈어요 (2.6.12 -> 2.8.0) (0)	2012.07.14
GIMP 창 모두 닫기 기능이 있었다니! (0)	2011.04.28
gimp 메뉴 언어 바꾸기(Windows) (0)	2011.04.18

Posted by 구차니

apache2 2.4.7 문서 경로 수정하기

Ubuntu 14.10 LTS ? 같은데

기본설정상 우분투에서 아파치의 htdocs는 /var/www 이지만
이 녀석을 다른 곳에서 사용하기 위해서는 다른 파일을 수정해야 한다.

/etc/apache2/apache2.conf <<
/etc/apache2/sites-enabled/000-default

기존의 2.2.22 (10.04 LTS) 에서는 site-enabled/000-default에 설정하면 되었으나
2.4.7 부터는 설정이 바뀌어서 apache2.conf 에서
허용되는 경로 부터 바꾸어 주어야 하는 듯 하다.

아래는 index.html의 도움말. 역시 써놓은건 잘 읽어야해 -_-

Document Roots

By default, Ubuntu does not allow access through the web browser to any file apart of those located in/var/www, public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv) you may need to whitelist your document root directory in /etc/apache2/apache2.conf.

The default Ubuntu document root is /var/www/html. You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box.

'프로그램 사용 > apache' 카테고리의 다른 글

starssl 인증서로 https / ssl 서버 적용하기 (3)	2017.01.05
사설 https 서버 만들기 (0)	2016.12.29
ab - apache HTTP server benchmarking tool (0)	2014.10.10
apache 특정 디렉토리만 인증하기 (0)	2013.04.09
500 internal server error - mediawiki 이전시 (0)	2011.12.18

Posted by 구차니

pulseaudio / ffmpeg esd protocol

MPLAYER 쪽에서는 ESD, PULSE, JACK을 켜주면 가능할 것 같다

Audio output:

--disable-alsa disable ALSA audio output [autodetect]

--disable-ossaudio disable OSS audio output [autodetect]

--disable-arts disable aRts audio output [autodetect]

--disable-esd disable esd audio output [autodetect]

--disable-pulse disable Pulseaudio audio output [autodetect]

--disable-jack disable JACK audio output [autodetect]

--disable-openal disable OpenAL audio output [autodetect]

--disable-nas disable NAS audio output [autodetect]

--disable-sgiaudio disable SGI audio output [autodetect]

--disable-sunaudio disable Sun audio output [autodetect]

--disable-kai disable KAI audio output [autodetect]

--disable-dart disable DART audio output [autodetect]

--disable-win32waveout disable Windows waveout audio output [autodetect]

--disable-coreaudio disable CoreAudio audio output [autodetect]

--disable-select disable using select() on the audio device [enable]

[링크 : http://blog.wonderwall.me/?p=272]
[링크 : http://mpd.wikia.com/wiki/PulseAudio]

'프로그램 사용 > ffmpeg & ffserver' 카테고리의 다른 글

mplayer status line (0)	2015.01.26
FAAD / FAAC (0)	2015.01.23
ffserver.conf 설정법 (0)	2014.11.06
Mplayer 캐시 설정 (0)	2014.11.06
Mplayer 1.1 / ffmpeg 0.10.2 git (0)	2014.10.22

Posted by 구차니

commit 전 svn add 한 파일 추가 취소하기/삭제하기/되돌리기

해당 파일을 남겨야 한다면
1. 파일 이름 변경
2. svn del 파일이름
3. 파일 이름 복구

해당 파일을 남길 필요가 없다면
1. svn del 파일이름

[링크 : https://kldp.org/node/52211]

+ 혹시나 해서 테스트 한 내용 백업파일을 만들어 두길 잘했지 ㅋㅋ
아무튼 svn del을 하면 해당 파일을 삭제하게 되니 주의요망!

$ svn st

? libliveMedia.a.bak

A libliveMedia.a

$ ll libliveMedia.a*

-rw-r--r-- 1 minimonk minimonk 1489620 2014-11-17 09:13 libliveMedia.a

-rw-r--r-- 1 minimonk minimonk 1489620 2014-11-17 09:14 libliveMedia.a.bak

$ svn del --force libliveMedia.a

D libliveMedia.a

$ ll libliveMedia.a*

-rw-r--r-- 1 minimonk minimonk 1489620 2014-11-17 09:14 libliveMedia.a.bak

$ svn st

? libliveMedia.a.bak

'프로그램 사용 > Version Control' 카테고리의 다른 글

svn add *.so ignored / --no-ignore (0)	2015.01.06
svn externals 를 이용한 외부 프로젝트 자동으로 불러오기(?) (0)	2014.12.29
svn 워킹 카피를 export 하기 (0)	2014.11.06
리눅스 svn status를 컬러풀하게 하기 (2)	2014.09.05
git for windows (0)	2014.06.27

Posted by 구차니

구차니의 잡동사니 모음

'프로그램 사용'에 해당되는 글 2263건

distcc 로 valgrind-3.6.1 컴파일 실패?

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

VNC web 버전?

'프로그램 사용 > VNC' 카테고리의 다른 글

distcc 작동모드

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

ccache & distcc

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

distcc on ubuntu

'프로그램 사용 > distcc & ccache' 카테고리의 다른 글

busybox su가 안될 경우

'프로그램 사용 > busybox' 카테고리의 다른 글

gimp를 이용하여 RGB 를 BGR로 변경하기

'프로그램 사용 > GIMP' 카테고리의 다른 글

apache2 2.4.7 문서 경로 수정하기

'프로그램 사용 > apache' 카테고리의 다른 글

pulseaudio / ffmpeg esd protocol

'프로그램 사용 > ffmpeg & ffserver' 카테고리의 다른 글

commit 전 svn add 한 파일 추가 취소하기/삭제하기/되돌리기

'프로그램 사용 > Version Control' 카테고리의 다른 글

카테고리

공지사항

태그목록

최근에 올라온 글

최근에 달린 댓글

티스토리툴바