'lots of little changes' merge done

[Shantonu Sen]

Short of reverting the patch, I worked around this locally by doing:

./configure
make -j4 BOOT_CFLAGS="-gstabs+ -O2 -fomit-frame-pointer"

I haven't run the test suite, but this may be useful for people who  
want a default-dwarf compiler even if dsymutil is borken.

Shantonu

On Nov 4, 2006, at 9:59 AM, Daniel Berlin wrote:

>>
>> You need dwarf_utilities-25, I think.  I'm not sure where to get it
>> from for Tiger, I will inquire. It should be in the next Leopard seed
>> (if you have access to Leopard seeds).  In the meantime, you can
>> avoid the problem by copying /bin/true into your path as 'dsymutil';
>> the problem with that, or an autoconf test or whatever, is that if
>> you say 'gcc -g t.c -g -o t', debugging won't work.
>
> Geoff, *please* don't take this the wrong way, but can you please stop
> breaking the build for darwin for the current production OS X release?
>
> I understand you develop on future versions, but the majority of us
> with macs do not.
>
> I'd really appreciate it if you would test your changes in an
> environment that others have access to.
>
> Breaking i386-darwin on Tiger means I can't get work done for stage1
> as fast as I want to, and also hurts a bunch of other people.
>
> As such, I want to start the 48 hour clock on this change.
>
> I understand you probably can't get dwarf-utilities-25 out to people
> in that time frame, so i would suggest you do one of the following
>
> 1. Conditionalize this change on dwarf-utilities-25 being present (as
> roger suggests)
> 2. Conditionalize the change on the host being a proper version of  
> Leopard
> 3. Revert the patch (or move it to Apple's branch) until others can
> get access to the tools necessary to make it work.
>
> Thanks,
> Dan