Re: Mac OS X: OpenSSL again

2007-06-06 Thread Anders F Björklund
Ralf S. Engelschall wrote: Oh, I see. Ok, I've now improved the wrapper scripts. Please manually remove /libexec/openpkg/override/{cc,gcc} and upgrade to the latest bootstrap version as of today. Then if "-c" or "-E" is present on the compiler command line the -Wl,-search_paths_first should be n

Re: Mac OS X: OpenSSL again

2007-06-06 Thread Anders F Björklund
Ralf S. Engelschall wrote: However, this still did not work because OpenPKG will fail to locate the real compiler e.g. i686-apple-darwin8-gcc-4.0.1 (from /usr/bin), but only find the "gcc-4.0" driver front-end... (symlinked from cc) So either I need to bring some more symlinks in, or do it

Re: Mac OS X: OpenSSL again

2007-06-06 Thread Ralf S. Engelschall
On Wed, Jun 06, 2007, Anders F Björklund wrote: > >> This can be provided by "openpkg-import". > > > > Will do that, then: use openpkg-import to replace "binutils" and "gcc". > > > > One little problem is that the binutils and cctools differ in content, so > > the following programs are missing: a

Re: Mac OS X: OpenSSL again

2007-06-06 Thread Anders F Björklund
This can be provided by "openpkg-import". Will do that, then: use openpkg-import to replace "binutils" and "gcc". One little problem is that the binutils and cctools differ in content, so the following programs are missing: addr2line, objcopy, objdump, readelf I fixed the missing symlink ta

Re: Mac OS X: OpenSSL again

2007-06-06 Thread Anders F Björklund
Ralf S. Engelschall wrote: And need to provide "fake" binutils/gcc packages, with /usr symlinks. (so that dependencies and such work, otherwise it'll try to install) /openpkg/bin/cc -> /usr/bin/cc /openpkg/bin/gcc -> /usr/bin/gcc This can be provided by "openpkg-import". Will do that, t

Re: Mac OS X: OpenSSL again

2007-06-06 Thread Ralf S. Engelschall
On Wed, Jun 06, 2007, Anders F Björklund wrote: > Ralf S. Engelschall wrote: > > >> So appending "-Wl,-search_paths_first" to the LDFLAGS should work too. > > > > Cool, that's it! If we now override the cc, gcc and ld commands under > > Mac OS X and enfore this option, the various linking proble

Re: Mac OS X: OpenSSL again

2007-06-06 Thread Anders F Björklund
Ralf S. Engelschall wrote: So appending "-Wl,-search_paths_first" to the LDFLAGS should work too. Cool, that's it! If we now override the cc, gcc and ld commands under Mac OS X and enfore this option, the various linking problems you have observed should be gone. What about the following (unt

Re: Mac OS X: OpenSSL again

2007-06-03 Thread Anders F Björklund
Ralf S. Engelschall wrote: Cool, that's it! If we now override the cc, gcc and ld commands under Mac OS X and enfore this option, the various linking problems you have observed should be gone. What about the following (untested) patch? Need to override ranlib and strip, and maybe a few others

Re: Mac OS X: OpenSSL again

2007-06-03 Thread Ralf S. Engelschall
On Sun, Jun 03, 2007, Anders F Björklund wrote: > > I don't know of any linker option to have it look for static libs > > (other than explicitly listing them by name), but either a wrapper > > to the binary or even patching the source of the binary is doable. > > Reading through the source code I

Re: Mac OS X: OpenSSL again

2007-06-03 Thread Anders F Björklund
I did approach 1) for OpenSSL and approach 3) for Apache, and then "the pitch" succeeded* in running apache+lynx. :-) Hmm, almost forgot to mention that I did have to change the default apache configuration before it would start up: OpenPKG: start: apache:FAILED openpkg:rc:WARNING: /openpkg:apa

Re: Mac OS X: OpenSSL again

2007-06-03 Thread Anders F Björklund
I don't know of any linker option to have it look for static libs (other than explicitly listing them by name), but either a wrapper to the binary or even patching the source of the binary is doable. Reading through the source code I realize I didn't look *that* hard: "-search_paths_first

Re: Mac OS X: OpenSSL again

2007-06-03 Thread Anders F Björklund
Ralf S. Engelschall wrote: However, the *reason* for the workaround is the fact that since OpenPKG does not provide a shared OpenSSL library, Darwin ld(1) will try to use the /usr/lib variant instead... So this will affect everything else using OpenSSL as well. The real solution would be

Re: Mac OS X: OpenSSL again

2007-06-03 Thread Ralf S. Engelschall
On Sun, Jun 03, 2007, Anders F Björklund wrote: > First, a small addition to the openssl.patch for "test": > http://www.algonet.se/~afb/openpkg/openssl-addition.diff > (originally did the same thing for "apps" for the bootstrap) > > However, the *reason* for the workaround is the fact that >

Mac OS X: OpenSSL again

2007-06-03 Thread Anders F Björklund
First, a small addition to the openssl.patch for "test": http://www.algonet.se/~afb/openpkg/openssl-addition.diff (originally did the same thing for "apps" for the bootstrap) However, the *reason* for the workaround is the fact that since OpenPKG does not provide a shared OpenSSL library, Darwin