Debian updating rubygems Prettens dancing wep cams

In any case, most of the time, we’ll have a good regression test suite that will validate our application code, which will give us a good feeling when we hit that deployment button.What we haven’t done very well is to have that type of rigid development process for our infrastructure code. Archive: /tmp/luarocks_luarocks-rock-md5-1.1.2-2-4389/md5-1.1.2-2rock inflating: md5-1.1.2-2.rockspec extracting: md5-1.1.2gz gcc -O2 -I/usr/include/lua5.1 -c -o src/md5.o src/md5.c gcc -O2 -I/usr/include/lua5.1 -c -o src/md5lib.o src/md5lib.c export MACOSX_DEPLOYMENT_TARGET="10.3"; gcc -O2 -I/usr/include/lua5.1 -shared -o src/src/md5.o src/md5lib.o /usr/bin/ld: src/md5.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -f PIC src/md5.o: could not read symbols: Bad value collect2: ld returned 1 exit status make: *** [src/core.so] Error 1 Error: Build error: Failed building. 」と怒られてしまう。-f PIC オプションをつけて直接コマンドを叩いてコンパイルし直すと、確かに共有ライブラリが作成される。 このあたりの環境に絡む問題は Lua Rocks が吸収すべきだなぁーと検索すると、debian/ubuntu 系の Lua Rocks ではアーキテクチャが決め打ちで i686 にされているのが原因とわかる。 BUG#923161: Hardcoded i686 architecture breaks x86_64 builds $ grep f PIC /usr/share/lua/5.1/luarocks/if proc == "x86_64" and not defaults.variables. $ uname -m x86_64 $ luarocks build md5 Archive: /tmp/luarocks_luarocks-rock-md5-1.1.2-2-7715/md5-1.1.2-2rock inflating: md5-1.1.2-2.rockspec extracting: md5-1.1.2gz gcc -O2 -f PIC -I/usr/include/lua5.1 -c -o src/md5.o src/md5.c gcc -O2 -f PIC -I/usr/include/lua5.1 -c -o src/md5lib.o src/md5lib.c export MACOSX_DEPLOYMENT_TARGET="10.3"; gcc -O2 -f PIC -I/usr/include/lua5.1 -shared -o src/src/md5.o src/md5lib.o gcc -O2 -f PIC -I/usr/include/lua5.1 -c -o src/des56.o src/des56.c gcc -O2 -f PIC -I/usr/include/lua5.1 -c -o src/ldes56.o src/ldes56.c export MACOSX_DEPLOYMENT_TARGET="10.3"; gcc -O2 -f PIC -I/usr/include/lua5.1 -shared -o src/des56src/des56.o src/ldes56.o mkdir -p /home/user/.luarocks/lib/luarocks/rocks/md5/1.1.2-2/lib/md5 cp src//home/user/.luarocks/lib/luarocks/rocks/md5/1.1.2-2/lib/md5/mkdir -p /home/user/.luarocks/lib/luarocks/rocks/md5/1.1.2-2/lua cp src/md5/home/user/.luarocks/lib/luarocks/rocks/md5/1.1.2-2/lua cp src/des56/home/user/.luarocks/lib/luarocks/rocks/md5/1.1.2-2/lib Updating manifest for /home/user/.luarocks/lib/luarocks/rocks No existing manifest. lua.h not found (looked in /usr/include/lua.h) You may want to use the flag --with-lua-include. $ sudo yum install lua lua-devel $ ./configure Lua interpreter found: /usr/bin/lua... lua found in $PATH: /usr/bin Checking Lua includes... Installation prefix: /usr/local Lua Rocks configuration directory: /usr/local/etc/luarocks Using Lua from: /usr Done. CFLAGS.." -f PIC" $ grep UNAME_M /usr/share/lua/5.1/luarocks/LUAROCKS_UNAME_M=i686 # !!! $ curl -O $ tar zxfv luarocks-2.0.8gz $ cd luarocks-2.0.8 $ ./configure Lua interpreter found: /usr/bin/lua... lua found in $PATH: /usr/bin Checking Lua includes... $ sudo /usr/local/bin/luarocks install md5 Installing switching to 'build' mode Archive: /tmp/luarocks_luarocks-rock-md5-1.1.2-2-474/md5-1.1.2-2rock inflating: md5-1.1.2-2.rockspec extracting: md5-1.1.2gz gcc -O2 -f PIC -I/usr/include -c -o src/md5.o src/md5.c gcc -O2 -f PIC -I/usr/include -c -o src/md5lib.o src/md5lib.c export MACOSX_DEPLOYMENT_TARGET="10.3"; gcc -O2 -f PIC -I/usr/include -shared -o src/src/md5.o src/md5lib.o gcc -O2 -f PIC -I/usr/include -c -o src/des56.o src/des56.c gcc -O2 -f PIC -I/usr/include -c -o src/ldes56.o src/ldes56.c export MACOSX_DEPLOYMENT_TARGET="10.3"; gcc -O2 -f PIC -I/usr/include -shared -o src/des56src/des56.o src/ldes56.o mkdir -p /usr/local/lib/luarocks/rocks/md5/1.1.2-2/lib/md5 cp src//usr/local/lib/luarocks/rocks/md5/1.1.2-2/lib/md5/mkdir -p /usr/local/lib/luarocks/rocks/md5/1.1.2-2/lua cp src/md5/usr/local/lib/luarocks/rocks/md5/1.1.2-2/lua cp src/des56/usr/local/lib/luarocks/rocks/md5/1.1.2-2/lib Updating manifest for /usr/local/lib/luarocks/rocks $ lua -lmd5 -e 'print(md5.sumhexa(""))' lua: module 'md5' not found: no field package.preload['md5'] no file '/usr/share/lua/5.1/:/usr/local/share/lua/5.1/' no file './md5.so' no file '/usr/lib64/lua/5.1/md5.so' no file '/usr/lib64/lua/5.1/loadall.so' stack traceback: [C]: ? $ grep LUA ~/.bashrc export LUA_PATH="/usr/local/lib/lua/5.1/?

Copy iso file /Applications/Virtual Box.app/Contents/Mac OS/VBox Guest into the box /tmp/VBox Guest stdin: is not a tty mount: block device /tmp/VBox Guest is write-protected, mounting Linux............ Removing existing Virtual Box DKMS kernel modules .. Converging =x86_64 to file /tmp/1611/trying wget... url https://opscode-omnibus-packages.s3.amazonaws.com/mac_os_x/10.7/x86_64/chef-11.10.4_1.mac_os_x.10.7.2md5 b318c6e42de19e7984f01bcf26fa53eb sha256 b460c1944857ba7e56f7f0e528d8f3909b4948ab1f9555f521bac3a4bce8be1b downloaded metadata file looks valid...

Virtual Box Guest Additions installer Removing installed version 4.3.8 of Virtual Box Guest Additions... Removing existing Virtual Box non-DKMS kernel modules .. downloading https://opscode-omnibus-packages.s3.amazonaws.com/mac_os_x/10.7/x86_64/chef-11.10.4_1.mac_os_x.10.7.2to file /tmp/1611/chef-11.10.4_1.mac_os_x.10.7.2trying wget...

]]

You’ll need: First, we need to set up our dependencies and build tasks with Bundler and Rake respectively. /init.lua; $ lua -e 'print(package.path)' /usr/local/lib/lua/5.1/? よっしゃー。ログインできたー。 Discover Vagrant Boxes | Atlas by Hashi Corpにはvagrant cloudでどんなことが出来るのかがざっくり書かれてる。 これまでboxの追加はgithubとかにあがってたりA list of base boxes for Vagrant - Vagrantbox.esのあがってたりするboxをよしなに引っ張ってくる感じでやってたけど、それをもう少し共有しやすくしたイメージ。 実際にboxを追加してみる。 not upgraded. Starting Chef Client, version 11.10.4 Compiling Cookbooks... mixlib-config, mixlib-cli, mixlib-log, mixlib-authentication, mixlib-shellout, systemu, yajl-ruby, ipaddress, ohai, mime-types, rest-client, net-ssh, net-ssh-gateway, net-ssh-multi, highline, erubis, diff-lcs, hashie, moneta, rack, chef-zero, puma, coderay, slop, method_source, pry, chef, knife-solo after $ gem cleanup Cleaning up installed gems...Let’s do a quick recap of the main Repose cookbook.Firstly, this cookbook is meant to be wrapped by an application-specific cookbook, which we will write.

Leave a Reply