Am 07.06.2007 um 21:21 schrieb Ralf S. Engelschall:
On Thu, Jun 07, 2007, Olivier Kaloudoff wrote:
...
Yes, for fixing those problems I really need direct access to the
platform as I have to poke around in system headers and try many
things
manually.
Usually, it is fully sufficient if
http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.txt
Ah, ok. I see. Some incompatibilities with the system headers. This is
usually easy to workaround, but unfortunately not blindly without system
access. One has to find the defintions in /usr/include and then apply a
Ralf S. Engelschall wrote:
Yes, for fixing those problems I really need direct access to the
platform as I have to poke around in system headers and try many things
manually.
Porting GNU binutils over to Darwin sounds like a big enough task
with eyes open, so probably not worth trying to do
Ralf S. Engelschall wrote:
Yes, for fixing those problems I really need direct access to the
platform as I have to poke around in system headers and try many things
manually.
Porting GNU binutils over to Darwin sounds like a big enough task
with eyes open, so probably not worth trying to do
On Tue, Jun 05, 2007, Olivier Kaloudoff wrote:
Virtual package gcc needed gcc g++ and i686-apple-darwin8-g++-4.0.1
i686-apple-darwin8-gcc-4.0.1 linked to /openpkg/bin
Are the i686-apple-darwin8-g??-4.0.1 symlinks really required? All
OpenPKG packages AFAIK search just for gcc and g++ but
On Tue, Jun 05, 2007, Olivier Kaloudoff wrote:
So, please bootstrap a fresh instance again under Mac OS X and try to
build up to Apache with SSL support or whatever else and give feedback.
At least the problems under Mac OS X now should be a lot less than
before...
openpkg-20070604
On Tue, Jun 05, 2007, Ralf S. Engelschall wrote:
[...]
for the moment, on the i386, I have to create two virtual packages,
as suggested by Bill (binutils and gcc).
A gcc package should be enough as this is the only one requiring
binutils. OTOH, is GCC or Binutils the actual problem under