build 1.9.3-p125 build failed

[pdoak]

I am new to ruby and am trying to install 1.9.3 on a mac 10.7.3 with Xcode 4.3.1 and command line tools installed running a network home directory. When I run rbenv install 1.9.3, I obtain the following output:

rbenv install 1.9.3-p125
Downloading http://pyyaml.org/download/libyaml/yaml-0.1.4.tar.gz...
Installing yaml-0.1.4...

BUILD FAILED

Inspect or clean up the working tree at /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878
Results logged to /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878.log

Last 10 log lines:
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... /usr/bin/gcc-4.2
checking whether the C compiler works... no
configure: error: in `/var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4':
configure: error: C compiler cannot create executables
See `config.log' for more details

I have tried changing the script in usr/local/bin/ruby-build as described in another post but that does not make any difference. I have checked that the gcc compiler is installed by typing "which gcc-4.2" and it returns "usr/bin/gcc-4.2".

Please could anyone help me with the installation

[rxbynerd]

Does config.log have anything in it?

[pdoak]

I have not been able to find config.log. Where should the file be saved?

[rxbynerd]

No idea, the idea stemmed from

configure: error: in /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4':
configure: error: C compiler cannot create executables
See config.log' for more details"

[pdoak]

Here is the config.log which was in /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4. Thank you for your help:

This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake.

It was created by yaml configure 0.1.4, which was generated by GNU Autoconf 2.67. Invocation command line was

  $ ./configure --prefix=/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125

## --------- ##
## Platform. ##
## --------- ##

hostname = Paul-Dysons-Mac-Pro.local
uname -m = i386
uname -r = 11.3.0
uname -s = Darwin
uname -v = Darwin Kernel Version 11.3.0: Thu Jan 12 18:48:32 PST 2012; root:xnu-1699.24.23~1/RELEASE_I386

/usr/bin/uname -p = i386
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = Mach kernel version:
     Darwin Kernel Version 11.3.0: Thu Jan 12 18:48:32 PST 2012; root:xnu-1699.24.23~1/RELEASE_I386
Kernel configured for up to 4 processors.
4 processors are physically available.
4 processors are logically available.
Processor type: i486 (Intel 80486)
Processors active: 0 1 2 3
Primary memory available: 12.00 gigabytes
Default processor set: 146 tasks, 824 threads, 4 processors
Load average: 1.53, Mach factor: 2.46
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/libexec
PATH: /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/shims
PATH: /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/sbin
PATH: /sbin
PATH: /usr/local/bin
PATH: /usr/X11/bin
PATH: /usr/local/git/bin

## ----------- ##
## Core tests. ##
## ----------- ##

configure:2409: checking for a BSD-compatible install
configure:2477: result: /usr/bin/install -c
configure:2488: checking whether build environment is sane
configure:2538: result: yes
configure:2679: checking for a thread-safe mkdir -p
configure:2718: result: config/install-sh -c -d
configure:2731: checking for gawk
configure:2761: result: no
configure:2731: checking for mawk
configure:2761: result: no
configure:2731: checking for nawk
configure:2761: result: no
configure:2731: checking for awk
configure:2747: found /usr/bin/awk
configure:2758: result: awk
configure:2769: checking whether make sets $(MAKE)
configure:2791: result: yes
configure:2947: checking for gcc
configure:2974: result: /usr/bin/gcc-4.2
configure:3203: checking for C compiler version
configure:3212: /usr/bin/gcc-4.2 --version >&5
i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3223: $? = 0
configure:3212: /usr/bin/gcc-4.2 -v >&5
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/gcc/gcc-5666.3~278/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)
configure:3223: $? = 0
configure:3212: /usr/bin/gcc-4.2 -V >&5
gcc-4.2: argument to `-V' is missing
configure:3223: $? = 1
configure:3212: /usr/bin/gcc-4.2 -qversion >&5
i686-apple-darwin11-gcc-4.2.1: no input files
configure:3223: $? = 1
configure:3243: checking whether the C compiler works
configure:3265: /usr/bin/gcc-4.2  -I'/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/include'  -L'/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/lib'  conftest.c  >&5
i686-apple-darwin11-gcc-4.2.1: Data/Users: No such file or directory
i686-apple-darwin11-gcc-4.2.1: home/pdd/.rbenv/versions/1.9.3-p125/include': No such file or directory
i686-apple-darwin11-gcc-4.2.1: Data/Users: No such file or directory
i686-apple-darwin11-gcc-4.2.1: home/pdd/.rbenv/versions/1.9.3-p125/lib': No such file or directory
configure:3269: $? = 1
configure:3307: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "yaml"
| #define PACKAGE_TARNAME "yaml"
| #define PACKAGE_VERSION "0.1.4"
| #define PACKAGE_STRING "yaml 0.1.4"
| #define PACKAGE_BUGREPORT "http://pyyaml.org/newticket?component=libyaml"
| #define PACKAGE_URL ""
| #define PACKAGE "yaml"
| #define VERSION "0.1.4"
| #define YAML_VERSION_MAJOR 0
| #define YAML_VERSION_MINOR 1
| #define YAML_VERSION_PATCH 4
| #define YAML_VERSION_STRING "0.1.4"
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:3312: error: in `/var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4':
configure:3314: error: C compiler cannot create executables
See `config.log' for more details

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CC_set=set
ac_cv_env_CC_value=/usr/bin/gcc-4.2
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=set
ac_cv_env_CPPFLAGS_value='-I'\''/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/include'\'' '
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value='-L'\''/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/lib'\'' '
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_AWK=awk
ac_cv_prog_ac_ct_CC=/usr/bin/gcc-4.2
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/missing --run aclocal-1.11'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/missing --run tar'
AR=''
AUTOCONF='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/missing --run autoconf'
AUTOHEADER='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/missing --run autoheader'
AUTOMAKE='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/missing --run automake-1.11'
AWK='awk'
CC='/usr/bin/gcc-4.2'
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS='-I'\''/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/include'\'' '
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
DOXYGEN=''
DOXYGEN_FALSE=''
DOXYGEN_TRUE=''
DSYMUTIL=''
DUMPBIN=''
ECHO_C='\c'
ECHO_N=''
ECHO_T=''
EGREP=''
EXEEXT=''
FGREP=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LD=''
LDFLAGS='-L'\''/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/lib'\'' '
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIPO=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/missing --run makeinfo'
MKDIR_P='config/install-sh -c -d'
NM=''
NMEDIT=''
OBJDUMP=''
OBJEXT=''
OTOOL64=''
OTOOL=''
PACKAGE='yaml'
PACKAGE_BUGREPORT='http://pyyaml.org/newticket?component=libyaml'
PACKAGE_NAME='yaml'
PACKAGE_STRING='yaml 0.1.4'
PACKAGE_TARNAME='yaml'
PACKAGE_URL=''
PACKAGE_VERSION='0.1.4'
PATH_SEPARATOR=':'
RANLIB=''
SED=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='0.1.4'
YAML_LT_AGE='0'
YAML_LT_CURRENT='2'
YAML_LT_RELEASE='0'
YAML_LT_REVISION='2'
ac_ct_CC='/usr/bin/gcc-4.2'
ac_ct_DUMPBIN=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include=''
am__isrc=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
install_sh='${SHELL} /var/folders/mb/y4pkl06167788c4kpgnt9zv0000102/T/ruby-build.20120322182939.42878/yaml-0.1.4/config/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
lt_ECHO='/bin/echo'
mandir='${datarootdir}/man'
mkdir_p='$(top_builddir)/config/install-sh -c -d'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME "yaml"
#define PACKAGE_TARNAME "yaml"
#define PACKAGE_VERSION "0.1.4"
#define PACKAGE_STRING "yaml 0.1.4"
#define PACKAGE_BUGREPORT "http://pyyaml.org/newticket?component=libyaml"
#define PACKAGE_URL ""
#define PACKAGE "yaml"
#define VERSION "0.1.4"
#define YAML_VERSION_MAJOR 0
#define YAML_VERSION_MINOR 1
#define YAML_VERSION_PATCH 4
#define YAML_VERSION_STRING "0.1.4"

configure: exit 77

[rxbynerd]

Hmm, OK, I don't acutually use a Mac, so I'm going to ask a bunch of what seems like stupid questions :sparkles:

Do you have gcc installed? Can you compile a simple C program with it?

[rxbynerd]

It looks to be an issue with what ruby-build is passing into the gcc test thingumy

[pdoak]

I have gcc installed - gcc-4.2. I have never tried to compile a C program but if you tell me how to, I will try and see if it works.

[rxbynerd]

OK, I have no idea if this will work on a Mac

Download this file to a directory, change directory in Terminal, then run

gcc -o lolworld lolworld.c

If it produces a clean output, try running ./lolworld

If it doesn't, paste me the output

[pdoak]

That worked. It compiled and said "Hello, pdoak"

[rxbynerd]

Oh good, it's not gcc

This line does seem very strange, /usr/bin/gcc-4.2 -I'/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/include' -L'/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125/lib' conftest.c >&5

Are you doing anything special with directory layouts?

[pdoak]

Not that I know of but I don't understand what you mean by directory layouts.

[rxbynerd]

OK, that's good enough

It looks like a problem with libyaml's configure script checking that GCC works, and is including the wrong paths for the compiler to look for header files in, meaning the thing breaks

Try downloading and extracting http://pyyaml.org/download/libyaml/yaml-0.1.4.tar.gz and then doing ./configure

If it produces the same output, it's libyaml's issue, if it doesn't, there is something that rbenv is doing to the configure script

[pdoak]

I have downloaded the file and there is now a file called yaml-0.1.4.tar in my downloads folder. I am sorry but I am not familiar with using ./configure so please could you explain how I use this on the downloaded file.

Many thanks

On 22 Mar 2012, at 21:35, Luke Carpenter wrote:

OK, that's good enough

It looks like a problem with libyaml's configure script checking that GCC works, and is including the wrong paths for the compiler to look for header files in, meaning the thing breaks

Try downloading and extracting http://pyyaml.org/download/libyaml/yaml-0.1.4.tar.gz and then doing ./configure

If it produces the same output, it's libyaml's issue, if it doesn't, there is something that rbenv is doing to the configure script

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4648943

[jiripospisil]

$ tar xf yaml-0.1.4.tar.gz
$ cd yaml-0.1.4
$ ./configure

[pdoak]

Thank you. I ran ./configure and this is the output:

./configure
./configure: line 597: test: too many arguments
./configure: line 597: test: too many arguments
./configure: line 597: test: too many arguments
./configure: line 597: test: too many arguments
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... config/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... 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 how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
configure: WARNING: Libtool does not cope well with whitespace in `pwd`
checking build system type... x86_64-apple-darwin11.3.0
checking host system type... x86_64-apple-darwin11.3.0
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm
checking the name lister (/usr/bin/nm) interface... BSD nm
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld option to reload object files... -r
checking for objdump... no
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm output from gcc object... ok
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for lipo... lipo
checking for otool... otool
checking for otool64... no
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fno-common -DPIC
checking if gcc PIC flag -fno-common -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin11.3.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for doxygen... false
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
configure: creating ./config.status
config.status: creating yaml-0.1.pc
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating Makefile
config.status: creating tests/Makefile
config.status: creating win32/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

Thanks

[rxbynerd]

Now make

Then sudo make install

[pdoak]

I am sorry that I am unfamiliar with this but do I just type "make" and then "sudo make install"

[rxbynerd]

Yup :)

Sent via Nyx

On 23 Mar 2012, at 09:41, pdoak reply@reply.github.com wrote:

I am sorry that I am unfamiliar with this but do I just type "make" and then "sudo make install"

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656137

[pdoak]

Thanks. This is the output. It looks like there are a few errors:

make (CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh "/Network/Servers/server.????????.com/Volumes/Network Data/Users home/pdd/Desktop/yaml-0.1.4/config/missing" --run autoheader) aclocal.m4:20: warning: this file was generated for autoconf 2.67. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically autoreconf'. configure.ac:30: error: Autoconf version 2.62 or higher is required aclocal.m4:8484: AM_INIT_AUTOMAKE is expanded from... configure.ac:30: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoheader: '/usr/bin/autom4te' failed with exit status: 63 WARNING:autoheader' is probably too old. You should only need it if you modified acconfig.h' orconfigure.ac'. You might want to install the Autoconf' andGNU m4' packages. Grab them from any GNU archive site. rm -f stamp-h1 touch config.h.in cd . && /bin/sh ./config.status config.h config.status: creating config.h config.status: config.h is unchanged make all-recursive Making all in include make[2]: Nothing to be done for all'. Making all in src /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c -o api.lo api.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c api.c -fno-common -DPIC -o .libs/api.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c api.c -o api.o >/dev/null 2>&1 mv -f .deps/api.Tpo .deps/api.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c -o reader.lo reader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c reader.c -fno-common -DPIC -o .libs/reader.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c reader.c -o reader.o >/dev/null 2>&1 mv -f .deps/reader.Tpo .deps/reader.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c -o scanner.lo scanner.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c scanner.c -fno-common -DPIC -o .libs/scanner.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c scanner.c -o scanner.o >/dev/null 2>&1 mv -f .deps/scanner.Tpo .deps/scanner.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c -o parser.lo parser.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -fno-common -DPIC -o .libs/parser.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -o parser.o >/dev/null 2>&1 mv -f .deps/parser.Tpo .deps/parser.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c -o loader.lo loader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c loader.c -fno-common -DPIC -o .libs/loader.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c loader.c -o loader.o >/dev/null 2>&1 mv -f .deps/loader.Tpo .deps/loader.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c -o writer.lo writer.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c writer.c -fno-common -DPIC -o .libs/writer.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c writer.c -o writer.o >/dev/null 2>&1 mv -f .deps/writer.Tpo .deps/writer.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c -o emitter.lo emitter.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c emitter.c -fno-common -DPIC -o .libs/emitter.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c emitter.c -o emitter.o >/dev/null 2>&1 mv -f .deps/emitter.Tpo .deps/emitter.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c -o dumper.lo dumper.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c dumper.c -fno-common -DPIC -o .libs/dumper.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c dumper.c -o dumper.o >/dev/null 2>&1 mv -f .deps/dumper.Tpo .deps/dumper.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -release 0 -version-info 2:2:0 -o libyaml.la -rpath /usr/local/lib api.lo reader.lo scanner.lo parser.lo loader.lo writer.lo emitter.lo dumper.lo libtool: link: gcc -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o .libs/libyaml-0.2.dylib .libs/api.o .libs/reader.o .libs/scanner.o .libs/parser.o .libs/loader.o .libs/writer.o .libs/emitter.o .libs/dumper.o -install_name /usr/local/lib/libyaml-0.2.dylib -compatibility_version 3 -current_version 3.2 -Wl,-single_module libtool: link: dsymutil .libs/libyaml-0.2.dylib || : libtool: link: (cd ".libs" && rm -f "libyaml.dylib" && ln -s "libyaml-0.2.dylib" "libyaml.dylib") libtool: link: ar cru .libs/libyaml.a api.o reader.o scanner.o parser.o loader.o writer.o emitter.o dumper.o libtool: link: ranlib .libs/libyaml.a libtool: link: ( cd ".libs" && rm -f "libyaml.la" && ln -s "../libyaml.la" "libyaml.la" ) Making all in . Making all in tests gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-scanner.o -MD -MP -MF .deps/run-scanner.Tpo -c -o run-scanner.o run-scanner.c mv -f .deps/run-scanner.Tpo .deps/run-scanner.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-scanner run-scanner.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-scanner run-scanner.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-parser.o -MD -MP -MF .deps/run-parser.Tpo -c -o run-parser.o run-parser.c mv -f .deps/run-parser.Tpo .deps/run-parser.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-parser run-parser.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-parser run-parser.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-loader.o -MD -MP -MF .deps/run-loader.Tpo -c -o run-loader.o run-loader.c mv -f .deps/run-loader.Tpo .deps/run-loader.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-loader run-loader.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-loader run-loader.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-emitter.o -MD -MP -MF .deps/run-emitter.Tpo -c -o run-emitter.o run-emitter.c run-emitter.c: In function ‘print_output’: run-emitter.c:208: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:208: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:209: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-emitter.c:209: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-emitter.c: In function ‘main’: run-emitter.c:322: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:322: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ mv -f .deps/run-emitter.Tpo .deps/run-emitter.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-emitter run-emitter.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-emitter run-emitter.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-dumper.o -MD -MP -MF .deps/run-dumper.Tpo -c -o run-dumper.o run-dumper.c run-dumper.c: In function ‘print_output’: run-dumper.c:182: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:182: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:183: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-dumper.c:183: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-dumper.c: In function ‘main’: run-dumper.c:306: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:306: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ mv -f .deps/run-dumper.Tpo .deps/run-dumper.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-dumper run-dumper.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-dumper run-dumper.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-reformatter.o -MD -MP -MF .deps/example-reformatter.Tpo -c -o example-reformatter.o example-reformatter.c example-reformatter.c: In function ‘main’: example-reformatter.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-reformatter.Tpo .deps/example-reformatter.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-reformatter example-reformatter.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-reformatter example-reformatter.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-reformatter-alt.o -MD -MP -MF .deps/example-reformatter-alt.Tpo -c -o example-reformatter-alt.o example-reformatter-alt.c example-reformatter-alt.c: In function ‘main’: example-reformatter-alt.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-reformatter-alt.Tpo .deps/example-reformatter-alt.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-reformatter-alt example-reformatter-alt.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-reformatter-alt example-reformatter-alt.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-deconstructor.o -MD -MP -MF .deps/example-deconstructor.Tpo -c -o example-deconstructor.o example-deconstructor.c example-deconstructor.c: In function ‘main’: example-deconstructor.c:1037: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1037: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1041: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1041: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-deconstructor.Tpo .deps/example-deconstructor.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-deconstructor example-deconstructor.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-deconstructor example-deconstructor.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-deconstructor-alt.o -MD -MP -MF .deps/example-deconstructor-alt.Tpo -c -o example-deconstructor-alt.o example-deconstructor-alt.c example-deconstructor-alt.c: In function ‘main’: example-deconstructor-alt.c:707: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:707: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:711: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:711: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-deconstructor-alt.Tpo .deps/example-deconstructor-alt.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-deconstructor-alt example-deconstructor-alt.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-deconstructor-alt example-deconstructor-alt.o ../src/.libs/libyaml.dylib Making all in win32 make[2]: Nothing to be done forall'. Paul-Dysons-Mac-Pro:yaml-0.1.4 pdd$ sudo make install Password: Making install in include make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/local/include" || ../config/install-sh -c -d "/usr/local/include" /usr/bin/install -c -m 644 yaml.h '/usr/local/include/.' Making install in src test -z "/usr/local/lib" || ../config/install-sh -c -d "/usr/local/lib" /bin/sh ../libtool --mode=install /usr/bin/install -c libyaml.la '/usr/local/lib' libtool: install: /usr/bin/install -c .libs/libyaml-0.2.dylib /usr/local/lib/libyaml-0.2.dylib libtool: install: (cd /usr/local/lib && { ln -s -f libyaml-0.2.dylib libyaml.dylib || { rm -f libyaml.dylib && ln -s libyaml-0.2.dylib libyaml.dylib; }; }) libtool: install: /usr/bin/install -c .libs/libyaml.lai /usr/local/lib/libyaml.la libtool: install: /usr/bin/install -c .libs/libyaml.a /usr/local/lib/libyaml.a libtool: install: chmod 644 /usr/local/lib/libyaml.a libtool: install: ranlib /usr/local/lib/libyaml.a /bin/sh: /Network/Servers/server.kennedy-dyson.com/Volumes/Network: No such file or directory make[2]: * [install-libLTLIBRARIES] Error 127 make[1]: * [install-am] Error 2 make: *\ [install-recursive] Error 1 On 23 Mar 2012, at 09:42, Luke Carpenter wrote:

Yup :)

Sent via Nyx

On 23 Mar 2012, at 09:41, pdoak reply@reply.github.com wrote:

I am sorry that I am unfamiliar with this but do I just type "make" and then "sudo make install"

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656137

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656149

[rxbynerd]

The plot thickens

It's strange that there are two directory not found errors, one in the configure stage when rbenv attempts to build libyaml, and another when libyaml itself attempts to install itself after successfully building

Do you already have a system ruby installed?

Sent via Nyx

On 23 Mar 2012, at 09:46, pdoak reply@reply.github.com wrote:

Thanks. This is the output. It looks like there are a few errors:

make (CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh "/Network/Servers/server.????????.com/Volumes/Network Data/Users home/pdd/Desktop/yaml-0.1.4/config/missing" --run autoheader) aclocal.m4:20: warning: this file was generated for autoconf 2.67. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically autoreconf'. configure.ac:30: error: Autoconf version 2.62 or higher is required aclocal.m4:8484: AM_INIT_AUTOMAKE is expanded from... configure.ac:30: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoheader: '/usr/bin/autom4te' failed with exit status: 63 WARNING:autoheader' is probably too old. You should only need it if you modified acconfig.h' orconfigure.ac'. You might want to install the Autoconf' andGNU m4' packages. Grab them from any GNU archive site. rm -f stamp-h1 touch config.h.in cd . && /bin/sh ./config.status config.h config.status: creating config.h config.status: config.h is unchanged make all-recursive Making all in include make[2]: Nothing to be done for all'. Making all in src /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c -o api.lo api.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c api.c -fno-common -DPIC -o .libs/api.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c api.c -o api.o >/dev/null 2>&1 mv -f .deps/api.Tpo .deps/api.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c -o reader.lo reader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c reader.c -fno-common -DPIC -o .libs/reader.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c reader.c -o reader.o >/dev/null 2>&1 mv -f .deps/reader.Tpo .deps/reader.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c -o scanner.lo scanner.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c scanner.c -fno-common -DPIC -o .libs/scanner.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c scanner.c -o scanner.o >/dev/null 2>&1 mv -f .deps/scanner.Tpo .deps/scanner.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c -o parser.lo parser.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -fno-common -DPIC -o .libs/parser.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -o parser.o >/dev/null 2>&1 mv -f .deps/parser.Tpo .deps/parser.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c -o loader.lo loader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c loader.c -fno-common -DPIC -o .libs/loader.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c loader.c -o loader.o >/dev/null 2>&1 mv -f .deps/loader.Tpo .deps/loader.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c -o writer.lo writer.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c writer.c -fno-common -DPIC -o .libs/writer.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c writer.c -o writer.o >/dev/null 2>&1 mv -f .deps/writer.Tpo .deps/writer.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c -o emitter.lo emitter.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c emitter.c -fno-common -DPIC -o .libs/emitter.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c emitter.c -o emitter.o >/dev/null 2>&1 mv -f .deps/emitter.Tpo .deps/emitter.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c -o dumper.lo dumper.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c dumper.c -fno-common -DPIC -o .libs/dumper.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c dumper.c -o dumper.o >/dev/null 2>&1 mv -f .deps/dumper.Tpo .deps/dumper.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -release 0 -version-info 2:2:0 -o libyaml.la -rpath /usr/local/lib api.lo reader.lo scanner.lo parser.lo loader.lo writer.lo emitter.lo dumper.lo libtool: link: gcc -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o .libs/libyaml-0.2.dylib .libs/api.o .libs/reader.o .libs/scanner.o .libs/parser.o .libs/loader.o .libs/writer.o .libs/emitter.o .libs/dumper.o -install_name /usr/local/lib/libyaml-0.2.dylib -compatibility_version 3 -current_version 3.2 -Wl,-single_module libtool: link: dsymutil .libs/libyaml-0.2.dylib || : libtool: link: (cd ".libs" && rm -f "libyaml.dylib" && ln -s "libyaml-0.2.dylib" "libyaml.dylib") libtool: link: ar cru .libs/libyaml.a api.o reader.o scanner.o parser.o loader.o writer.o emitter.o dumper.o libtool: link: ranlib .libs/libyaml.a libtool: link: ( cd ".libs" && rm -f "libyaml.la" && ln -s "../libyaml.la" "libyaml.la" ) Making all in . Making all in tests gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-scanner.o -MD -MP -MF .deps/run-scanner.Tpo -c -o run-scanner.o run-scanner.c mv -f .deps/run-scanner.Tpo .deps/run-scanner.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-scanner run-scanner.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-scanner run-scanner.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-parser.o -MD -MP -MF .deps/run-parser.Tpo -c -o run-parser.o run-parser.c mv -f .deps/run-parser.Tpo .deps/run-parser.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-parser run-parser.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-parser run-parser.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-loader.o -MD -MP -MF .deps/run-loader.Tpo -c -o run-loader.o run-loader.c mv -f .deps/run-loader.Tpo .deps/run-loader.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-loader run-loader.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-loader run-loader.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-emitter.o -MD -MP -MF .deps/run-emitter.Tpo -c -o run-emitter.o run-emitter.c run-emitter.c: In function ‘print_output’: run-emitter.c:208: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:208: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:209: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-emitter.c:209: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-emitter.c: In function ‘main’: run-emitter.c:322: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:322: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ mv -f .deps/run-emitter.Tpo .deps/run-emitter.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-emitter run-emitter.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-emitter run-emitter.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-dumper.o -MD -MP -MF .deps/run-dumper.Tpo -c -o run-dumper.o run-dumper.c run-dumper.c: In function ‘print_output’: run-dumper.c:182: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:182: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:183: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-dumper.c:183: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-dumper.c: In function ‘main’: run-dumper.c:306: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:306: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ mv -f .deps/run-dumper.Tpo .deps/run-dumper.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-dumper run-dumper.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-dumper run-dumper.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-reformatter.o -MD -MP -MF .deps/example-reformatter.Tpo -c -o example-reformatter.o example-reformatter.c example-reformatter.c: In function ‘main’: example-reformatter.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-reformatter.Tpo .deps/example-reformatter.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-reformatter example-reformatter.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-reformatter example-reformatter.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-reformatter-alt.o -MD -MP -MF .deps/example-reformatter-alt.Tpo -c -o example-reformatter-alt.o example-reformatter-alt.c example-reformatter-alt.c: In function ‘main’: example-reformatter-alt.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-reformatter-alt.Tpo .deps/example-reformatter-alt.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-reformatter-alt example-reformatter-alt.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-reformatter-alt example-reformatter-alt.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-deconstructor.o -MD -MP -MF .deps/example-deconstructor.Tpo -c -o example-deconstructor.o example-deconstructor.c example-deconstructor.c: In function ‘main’: example-deconstructor.c:1037: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1037: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1041: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1041: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-deconstructor.Tpo .deps/example-deconstructor.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-deconstructor example-deconstructor.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-deconstructor example-deconstructor.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-deconstructor-alt.o -MD -MP -MF .deps/example-deconstructor-alt.Tpo -c -o example-deconstructor-alt.o example-deconstructor-alt.c example-deconstructor-alt.c: In function ‘main’: example-deconstructor-alt.c:707: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:707: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:711: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:711: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-deconstructor-alt.Tpo .deps/example-deconstructor-alt.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-deconstructor-alt example-deconstructor-alt.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-deconstructor-alt example-deconstructor-alt.o ../src/.libs/libyaml.dylib Making all in win32 make[2]: Nothing to be done forall'. Paul-Dysons-Mac-Pro:yaml-0.1.4 pdd$ sudo make install Password: Making install in include make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/local/include" || ../config/install-sh -c -d "/usr/local/include" /usr/bin/install -c -m 644 yaml.h '/usr/local/include/.' Making install in src test -z "/usr/local/lib" || ../config/install-sh -c -d "/usr/local/lib" /bin/sh ../libtool --mode=install /usr/bin/install -c libyaml.la '/usr/local/lib' libtool: install: /usr/bin/install -c .libs/libyaml-0.2.dylib /usr/local/lib/libyaml-0.2.dylib libtool: install: (cd /usr/local/lib && { ln -s -f libyaml-0.2.dylib libyaml.dylib || { rm -f libyaml.dylib && ln -s libyaml-0.2.dylib libyaml.dylib; }; }) libtool: install: /usr/bin/install -c .libs/libyaml.lai /usr/local/lib/libyaml.la libtool: install: /usr/bin/install -c .libs/libyaml.a /usr/local/lib/libyaml.a libtool: install: chmod 644 /usr/local/lib/libyaml.a libtool: install: ranlib /usr/local/lib/libyaml.a /bin/sh: /Network/Servers/server.kennedy-dyson.com/Volumes/Network: No such file or directory make[2]: * [install-libLTLIBRARIES] Error 127 make[1]: * [install-am] Error 2 make: *\ [install-recursive] Error 1 On 23 Mar 2012, at 09:42, Luke Carpenter wrote:

Yup :)

Sent via Nyx

On 23 Mar 2012, at 09:41, pdoak reply@reply.github.com wrote:

I am sorry that I am unfamiliar with this but do I just type "make" and then "sudo make install"

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656137

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656149

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656186

[pdoak]

Yes. I have ruby 1.8.7 that comes with OS X Lion. I didn't install it.

On 23 Mar 2012, at 09:55, Luke Carpenter wrote:

The plot thickens

It's strange that there are two directory not found errors, one in the configure stage when rbenv attempts to build libyaml, and another when libyaml itself attempts to install itself after successfully building

Do you already have a system ruby installed? xoxo

Sent via Nyx

On 23 Mar 2012, at 09:46, pdoak reply@reply.github.com wrote:

Thanks. This is the output. It looks like there are a few errors:

make (CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh "/Network/Servers/server.????????.com/Volumes/Network Data/Users home/pdd/Desktop/yaml-0.1.4/config/missing" --run autoheader) aclocal.m4:20: warning: this file was generated for autoconf 2.67. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically autoreconf'. configure.ac:30: error: Autoconf version 2.62 or higher is required aclocal.m4:8484: AM_INIT_AUTOMAKE is expanded from... configure.ac:30: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoheader: '/usr/bin/autom4te' failed with exit status: 63 WARNING:autoheader' is probably too old. You should only need it if you modified acconfig.h' orconfigure.ac'. You might want to install the Autoconf' andGNU m4' packages. Grab them from any GNU archive site. rm -f stamp-h1 touch config.h.in cd . && /bin/sh ./config.status config.h config.status: creating config.h config.status: config.h is unchanged make all-recursive Making all in include make[2]: Nothing to be done for all'. Making all in src /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c -o api.lo api.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c api.c -fno-common -DPIC -o .libs/api.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT api.lo -MD -MP -MF .deps/api.Tpo -c api.c -o api.o >/dev/null 2>&1 mv -f .deps/api.Tpo .deps/api.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c -o reader.lo reader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c reader.c -fno-common -DPIC -o .libs/reader.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT reader.lo -MD -MP -MF .deps/reader.Tpo -c reader.c -o reader.o >/dev/null 2>&1 mv -f .deps/reader.Tpo .deps/reader.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c -o scanner.lo scanner.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c scanner.c -fno-common -DPIC -o .libs/scanner.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT scanner.lo -MD -MP -MF .deps/scanner.Tpo -c scanner.c -o scanner.o >/dev/null 2>&1 mv -f .deps/scanner.Tpo .deps/scanner.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c -o parser.lo parser.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -fno-common -DPIC -o .libs/parser.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -o parser.o >/dev/null 2>&1 mv -f .deps/parser.Tpo .deps/parser.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c -o loader.lo loader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c loader.c -fno-common -DPIC -o .libs/loader.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT loader.lo -MD -MP -MF .deps/loader.Tpo -c loader.c -o loader.o >/dev/null 2>&1 mv -f .deps/loader.Tpo .deps/loader.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c -o writer.lo writer.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c writer.c -fno-common -DPIC -o .libs/writer.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT writer.lo -MD -MP -MF .deps/writer.Tpo -c writer.c -o writer.o >/dev/null 2>&1 mv -f .deps/writer.Tpo .deps/writer.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c -o emitter.lo emitter.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c emitter.c -fno-common -DPIC -o .libs/emitter.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT emitter.lo -MD -MP -MF .deps/emitter.Tpo -c emitter.c -o emitter.o >/dev/null 2>&1 mv -f .deps/emitter.Tpo .deps/emitter.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c -o dumper.lo dumper.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c dumper.c -fno-common -DPIC -o .libs/dumper.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT dumper.lo -MD -MP -MF .deps/dumper.Tpo -c dumper.c -o dumper.o >/dev/null 2>&1 mv -f .deps/dumper.Tpo .deps/dumper.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -release 0 -version-info 2:2:0 -o libyaml.la -rpath /usr/local/lib api.lo reader.lo scanner.lo parser.lo loader.lo writer.lo emitter.lo dumper.lo libtool: link: gcc -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o .libs/libyaml-0.2.dylib .libs/api.o .libs/reader.o .libs/scanner.o .libs/parser.o .libs/loader.o .libs/writer.o .libs/emitter.o .libs/dumper.o -install_name /usr/local/lib/libyaml-0.2.dylib -compatibility_version 3 -current_version 3.2 -Wl,-single_module libtool: link: dsymutil .libs/libyaml-0.2.dylib || : libtool: link: (cd ".libs" && rm -f "libyaml.dylib" && ln -s "libyaml-0.2.dylib" "libyaml.dylib") libtool: link: ar cru .libs/libyaml.a api.o reader.o scanner.o parser.o loader.o writer.o emitter.o dumper.o libtool: link: ranlib .libs/libyaml.a libtool: link: ( cd ".libs" && rm -f "libyaml.la" && ln -s "../libyaml.la" "libyaml.la" ) Making all in . Making all in tests gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-scanner.o -MD -MP -MF .deps/run-scanner.Tpo -c -o run-scanner.o run-scanner.c mv -f .deps/run-scanner.Tpo .deps/run-scanner.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-scanner run-scanner.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-scanner run-scanner.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-parser.o -MD -MP -MF .deps/run-parser.Tpo -c -o run-parser.o run-parser.c mv -f .deps/run-parser.Tpo .deps/run-parser.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-parser run-parser.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-parser run-parser.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-loader.o -MD -MP -MF .deps/run-loader.Tpo -c -o run-loader.o run-loader.c mv -f .deps/run-loader.Tpo .deps/run-loader.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-loader run-loader.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-loader run-loader.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-emitter.o -MD -MP -MF .deps/run-emitter.Tpo -c -o run-emitter.o run-emitter.c run-emitter.c: In function ‘print_output’: run-emitter.c:208: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:208: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:209: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-emitter.c:209: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-emitter.c: In function ‘main’: run-emitter.c:322: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-emitter.c:322: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ mv -f .deps/run-emitter.Tpo .deps/run-emitter.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-emitter run-emitter.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-emitter run-emitter.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT run-dumper.o -MD -MP -MF .deps/run-dumper.Tpo -c -o run-dumper.o run-dumper.c run-dumper.c: In function ‘print_output’: run-dumper.c:182: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:182: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:183: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-dumper.c:183: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’ run-dumper.c: In function ‘main’: run-dumper.c:306: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ run-dumper.c:306: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’ mv -f .deps/run-dumper.Tpo .deps/run-dumper.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o run-dumper run-dumper.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/run-dumper run-dumper.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-reformatter.o -MD -MP -MF .deps/example-reformatter.Tpo -c -o example-reformatter.o example-reformatter.c example-reformatter.c: In function ‘main’: example-reformatter.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-reformatter.Tpo .deps/example-reformatter.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-reformatter example-reformatter.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-reformatter example-reformatter.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-reformatter-alt.o -MD -MP -MF .deps/example-reformatter-alt.Tpo -c -o example-reformatter-alt.o example-reformatter-alt.c example-reformatter-alt.c: In function ‘main’: example-reformatter-alt.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:124: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:128: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:138: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:143: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:153: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:158: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-reformatter-alt.c:168: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-reformatter-alt.c:173: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-reformatter-alt.Tpo .deps/example-reformatter-alt.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-reformatter-alt example-reformatter-alt.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-reformatter-alt example-reformatter-alt.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-deconstructor.o -MD -MP -MF .deps/example-deconstructor.Tpo -c -o example-deconstructor.o example-deconstructor.c example-deconstructor.c: In function ‘main’: example-deconstructor.c:1037: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1037: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1041: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1041: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1051: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1056: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor.c:1066: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor.c:1071: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-deconstructor.Tpo .deps/example-deconstructor.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-deconstructor example-deconstructor.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-deconstructor example-deconstructor.o ../src/.libs/libyaml.dylib gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT example-deconstructor-alt.o -MD -MP -MF .deps/example-deconstructor-alt.Tpo -c -o example-deconstructor-alt.o example-deconstructor-alt.c example-deconstructor-alt.c: In function ‘main’: example-deconstructor-alt.c:707: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:707: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:711: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:711: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:721: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:726: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 7 has type ‘size_t’ example-deconstructor-alt.c:736: warning: format ‘%d’ expects type ‘int’, but argument 8 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘size_t’ example-deconstructor-alt.c:741: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’ mv -f .deps/example-deconstructor-alt.Tpo .deps/example-deconstructor-alt.Po /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o example-deconstructor-alt example-deconstructor-alt.o ../src/libyaml.la libtool: link: gcc -g -O2 -o .libs/example-deconstructor-alt example-deconstructor-alt.o ../src/.libs/libyaml.dylib Making all in win32 make[2]: Nothing to be done forall'. Paul-Dysons-Mac-Pro:yaml-0.1.4 pdd$ sudo make install Password: Making install in include make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/local/include" || ../config/install-sh -c -d "/usr/local/include" /usr/bin/install -c -m 644 yaml.h '/usr/local/include/.' Making install in src test -z "/usr/local/lib" || ../config/install-sh -c -d "/usr/local/lib" /bin/sh ../libtool --mode=install /usr/bin/install -c libyaml.la '/usr/local/lib' libtool: install: /usr/bin/install -c .libs/libyaml-0.2.dylib /usr/local/lib/libyaml-0.2.dylib libtool: install: (cd /usr/local/lib && { ln -s -f libyaml-0.2.dylib libyaml.dylib || { rm -f libyaml.dylib && ln -s libyaml-0.2.dylib libyaml.dylib; }; }) libtool: install: /usr/bin/install -c .libs/libyaml.lai /usr/local/lib/libyaml.la libtool: install: /usr/bin/install -c .libs/libyaml.a /usr/local/lib/libyaml.a libtool: install: chmod 644 /usr/local/lib/libyaml.a libtool: install: ranlib /usr/local/lib/libyaml.a /bin/sh: /Network/Servers/server.kennedy-dyson.com/Volumes/Network: No such file or directory make[2]: * [install-libLTLIBRARIES] Error 127 make[1]: * [install-am] Error 2 make: *\ [install-recursive] Error 1 On 23 Mar 2012, at 09:42, Luke Carpenter wrote:

Yup :)

Sent via Nyx

On 23 Mar 2012, at 09:41, pdoak reply@reply.github.com wrote:

I am sorry that I am unfamiliar with this but do I just type "make" and then "sudo make install"

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656137

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656149

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656186

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656271

[jiripospisil]

I am sorry that I am unfamiliar with this but do I just type "make" and then "sudo make install"

I don't think you should do that if you want to use rbenv. The ./configure step was just to verify that you have all the dependencies. As a result, configure outputs a Makefile but you didn't provide any prefix location, so when you do make install it will install to the default system location, not to ~/.rbenv/versions...

I don't remember the correct prefix setup but it should be something like ./configure --prefix ~/.rbenv/versions/1.9.3-p125 or similar, maybe others will know.

[rxbynerd]

@mekishizufu I was checking that libyaml would build correctly, to see if it was an issue with ruby-build or libyaml

Those instructions were for libyaml, not Ruby

[jiripospisil]

I am aware of that but the same applies for libyaml as well - it is ruby version specific and needs to be make installed with proper prefix path.

[pdoak]

Do I need to undo what I have done. If so could you explain how I do this. Thank you. On 23 Mar 2012, at 10:49, Jiri Pospisil wrote:

I am aware of that but the same applies for libyaml as well - it is ruby version specific and needs to be make installed with proper prefix path.

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4656934

[rxbynerd]

@mekishizufu The linker is not going to care where libyaml is, or what version it is, it just cares that it's there

It cares that it exposes the functions that Ruby needs, the last version of libyaml released is 0.1.4, released on 2011-05-30

Ruby 1.9.3-p125 was released on 2012-02-17

So that's the correct libyaml version

If it is compiled with a "proper prefix path", if anything, that "proper prefix path" is passed into Ruby's ./configure script so it knows where to link libyaml

@pdoak No you don't need to undo anything, the system is fine as it is

I wanted you to build libyaml because the definition for ruby-1.9.3-p125 first installs libyaml, then installs ruby

If you would like me to explain anything else, don't hesitate to ask. I did have a reply typed out on my phone, but it looks like it's eaten it

[pdoak]

poptart Thank you.

How can I now get 1.9.3 installed though

[rxbynerd]

It looks like ruby-build maintains a variable throughout the script called 'PREFIX_PATH', which is passed into both the linker and the compiler for libyaml

And for some reason, it's being set to /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125

That's set by https://github.com/sstephenson/ruby-build/blob/cacc406e04c7fd51bec76dffd72a0c7b5b278608/bin/ruby-build#L366

And I have no idea what $2 is, so I have no idea why your $PREFIX_PATH is set to that

[pdoak]

poptart, I don't know whether this helps but the .rbenv.versions directory exists in my home directory which is the directory specified in the path:

/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions

However, there is nothing in the versions folder.

On 23 Mar 2012, at 11:23, Luke Carpenter wrote:

It looks like ruby-build maintains a variable throughout the script called 'PREFIX_PATH', which is passed into both the linker and the compiler for libyaml

And for some reason, it's being set to /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125

That's set by https://github.com/sstephenson/ruby-build/blob/cacc406e04c7fd51bec76dffd72a0c7b5b278608/bin/ruby-build#L366

And I have no idea what $2 is, so I have no idea why your $PREFIX_PATH is set to that

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4657363

[jiripospisil]

@poptart

The linker is not going to care where libyaml is, or what version it is, it just cares that it's there

I guess it's just a matter of personal taste.. I like to keep everything related to one specific ruby version in one directory, separated from everything else. That's also the rbenv way.

If it is compiled with a "proper prefix path", if anything, that "proper prefix path" is passed into Ruby's ./configure script so it knows where to link libyaml

Yes, I was referring to the manual way of calling the ./configure, not through ruby-build.

[rxbynerd]

Yea, gcc isn't liking that path because of the 'Users home' bit

Is there any way to change that?

Sent via Nyx

On 23 Mar 2012, at 11:45, pdoak reply@reply.github.com wrote:

poptart, I don't know whether this helps but the .rbenv.versions directory exists in my home directory which is the directory specified in the path:

/Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions

However, there is nothing in the versions folder.

On 23 Mar 2012, at 11:23, Luke Carpenter wrote:

It looks like ruby-build maintains a variable throughout the script called 'PREFIX_PATH', which is passed into both the linker and the compiler for libyaml

And for some reason, it's being set to /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd/.rbenv/versions/1.9.3-p125

That's set by https://github.com/sstephenson/ruby-build/blob/cacc406e04c7fd51bec76dffd72a0c7b5b278608/bin/ruby-build#L366

And I have no idea what $2 is, so I have no idea why your $PREFIX_PATH is set to that

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4657363

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4657593

[pdoak]

Do you mean can I change the directory name to "UsersHome" without the space. What about "Network Data" - is that a problem also.

On 23 Mar 2012, at 11:58, Jiri Pospisil wrote:

@poptart

The linker is not going to care where libyaml is, or what version it is, it just cares that it's there

I guess it's just a matter of personal taste.. I like to keep everything related to one specific ruby version in one directory, separated from everything else. That's also the rbenv way.

If it is compiled with a "proper prefix path", if anything, that "proper prefix path" is passed into Ruby's ./configure script so it knows where to link libyaml

Yes, I was referring to the manual way of calling the ./configure, not through ruby-build.

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4657743

[rxbynerd]

Yes, /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd does seem like a very strange home directory, is your home folder on a server?

[pdoak]

Yes

On 23 Mar 2012, at 13:37, Luke Carpenter wrote:

Yes, /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd does seem like a very strange home directory, is your home folder on a server?

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4659037

[rxbynerd]

That explains everything

I have no idea how to proceed here, it's up to you what you want to do now

[pdoak]

Thank you for trying to help. Can you suggest anywhere where I could go for advice on resolving the issue.

On 23 Mar 2012, at 13:37, Luke Carpenter wrote:

Yes, /Network/Servers/server.server-server.com/Volumes/Network Data/Users home/pdd does seem like a very strange home directory, is your home folder on a server?

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4659037

[pdoak]

I solved the problem.

rbenv install 1.9.3-p125 does not work with a network home directory - I don't know why but here is the work around to install ruby 1.9.3-p125 on a network home.

download and unpack 1.9.3-p125 In terminal navigate to the directory which holds the unpacked "ruby 1.9.3-p125" folder ./configure --prefix=="insert full path to /.rbenv/versions/1.9.3-p125
In my case, it looked something like ./configure/ --prefix=/Network/Servers/server.your_domain.com/Volumes/Network\ Data/Users\ home/pdd/.rbenv/versions/1.9.3-p125 when this has finished type "make" when this has finished type "make install"

ruby 1.9.3-p125 should now be installed and ready to use.

On 23 Mar 2012, at 13:52, Luke Carpenter wrote:

That explains everything

I have no idea how to proceed here, it's up to you what you want to do now

---

Reply to this email directly or view it on GitHub: https://github.com/sstephenson/ruby-build/issues/145#issuecomment-4659283

[sstephenson]

Update: The C compiler cannot create executables error appears to be limited to 1.9.3-p125.

1.9.3-p194 builds cleanly with Xcode 4.3, so if we want to fix this issue we can scope it just to the p125 definition.