svn 1.3.0 and Apache 2.2, does that work?

["R. Welz" <we...@fixe-post.de>]

Hello.
Does svn 1.3.0 work with Apache 2.2 ?

Thanks a lot.

Robert


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn 1.3.0 and Apache 2.2, does that work? statically linking doesn't.

[Robert Welz <we...@fixe-post.de>]

Am 09.01.2006 um 21:07 schrieb David Waite:

>> /usr/bin/ld: can't locate file for: -lcrt0.o
>
> You are on a macintosh, aren't you? static compilation will not work;
> Apple leaves out that compiler runtime file on purpose to prevent it.

Just for the records: I found this on the darwin-development list.

Apple sais this is for compatibiliy. So kernel upgrades won't break  
the application.
Its a bit weak for a chroot environment but for the rest I agree.

Robert

> Subject: 	darwin-development digest, Vol 3 #1134 - 12 msgs
> 	From: 	  darwin-development-request@lists.apple.com
> 	Date: 	26. März 2004 23:27:04 MEZ


> to quote Jim Magee (@apple) yesterday on the unix-porting list :

> You will absolutely NEVER get a single statically linked executable to
> work on both Jaguar and Panther.  Using static linking of the system
> libraries into your application makes your binary compatibility
> situation worse - not better.  You will potentially have to ship a
> separate version of your application to work with each and every
> distinct software update of Panther and Jaguar.
>
> Why?
>
> It has been said before, but is worth repeating:  We strive to keep
> (backward) binary compatibility at the interface to the system shared
> libraries.  The internal interfaces/protocols/mechanisms that these
> libraries use to talk to the kernel (and other system-wide-servers) is
> free to change in order to fix bugs, get better performance, or  
> provide
> additional features from the kernel/servers.  But as long as you just
> use the interfaces provided by the dynamic libraries that match those
> modified kernel/servers, you're fine.
>
> The result:  Programs that use the dynamic library interface to the
> system provided by Jaguar continue to work when executed against  
> future
> (compatible at the interface-level) versions of those libraries (that
> may talk a modified version of their internal protocols to the new
> kernel/servers on that version of the system).
>
> Now, compile up static versions of those same libraries (we cannot
> technically stop you with the source being open) and statically link
> your program against that, and it will be speaking those internal
> protocols to the kernel/servers directly.  It has no dylib buffer. But
> it only speaks one very specific dialect of those internal protocols.
>
> The result: You just have effectively tied your application to only
> working with one particular kernel and one particular set of servers.
> You are -- in effect -- locked to executing correctly only against one
> very specific software update.  Not at all what you had in mind!
>
> I think what you are missing is that the development environment  
> allows
> you to build against and link against older versions (like the Jaguar
> versions) of those interfaces even though you are actually running
> Panther.  The development environment ships with multiple versions of
> the SDKs.  You pick the oldest version you want to support - specify
> that version to XCode (or manually through environment variables for
> non-XCode builds) build away, and you should work on that version and
> beyond.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn 1.3.0 and Apache 2.2, does that work?

[Robert Welz <we...@fixe-post.de>]

Robert Welz wrote:
> 
> Am 09.01.2006 um 21:07 schrieb David Waite:
> 
>>> /usr/bin/ld: can't locate file for: -lcrt0.o
>>
>> You are on a macintosh, aren't you? static compilation will not work;
>> Apple leaves out that compiler runtime file on purpose to prevent it.
> 
> Huh.
> I need to have a chroot.
> 
> So there is only the hard way, to copy all those needed libraries  into 
> the chroot jail.
> 
> But thanks for pointing that out, it saves a lot of compile time on a  
> G4/866.
> 
> Greetings,
> Robert Welz
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>


My chroot jail works now with mod_chroot on the Mac OS X Tiger. Apache 2.2, svn 1.3.0, 
dynamically linked. Was quite easy.

Greetings,
Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn 1.3.0 and Apache 2.2, does that work?

[Ben Collins-Sussman <su...@red-bean.com>]

Yes, any version of subversion 1.x works with any version of apache 2.y.

Just be careful about APR.  apache 2.0 ships with apr 0.9, and apache
2.2 ships with apr 1.2.  apr 0.9 and apr 1.2 are *not* binary
compatible.  So if you upgrade from apache 2.0 to 2.2, make sure you
rebuild subversion to use the new apr 1.2 libraries as well.  What you
don't want to happen is have apache use apr 1.2 and subversion use apr
0.9... that causes things to break.  As long as subversion is always
compiled against the same apr that apache is, you're fine.


On 1/8/06, R. Welz <we...@fixe-post.de> wrote:
> Hello.
> Does svn 1.3.0 work with Apache 2.2 ?
>
> Thanks a lot.
>
> Robert
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn 1.3.0 and Apache 2.2, does that work?

[John Szakmeister <jo...@szakmeister.net>]

On Monday 09 January 2006 15:07, David Waite wrote:
> > /usr/bin/ld: can't locate file for: -lcrt0.o
>
> You are on a macintosh, aren't you? static compilation will not work;
> Apple leaves out that compiler runtime file on purpose to prevent it.

I wonder if we should just flag an error in the configure script when trying 
to build a static binary on Mac OS X?

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org