If you look at the path of the file that failed compilation, it is in subversion/svn/. On Mac OS X there is no need to compile it twice as there is no real supported concept of PIC - it's a no-op for the compiler. Linking the libraries statically or dynamically is different of course. -- justin On Jan 3, 2013 2:18 AM, "Peter Samuelson" <pe...@p12n.org> wrote:
> > [Justin Erenkrantz] > > Because GNU libtool always compiles code twice on Mac OS X (insert rant > > against GNU libtool here) > ... > > But, then again, I always like reminding devs how evil libtool is and > > that it's double-compiling everything. =P > > Well, you asked it to build both static and shared libraries. What's > it supposed to do? With most ABIs, you want to build shared library > code in PIC mode and all other code in non-PIC mode. So yes, that > means double-compiling. You'll notice it does _not_ do this for > non-library code such as subversion/svn/ or subversion/svnadmin/. (At > least on Linux it doesn't. I actually have no idea what it does on Mac > OS.) > > Frankly, if you think double-compiling is "evil", you should be > suggesting that we make either '--disable-static' or '--disable-shared' > the default - see configure.ac, line 238 or so. Not blaming libtool. >
