Notice the lack of -O2, etc.  This also broke SYMBOLS= PROFILE=, COVERAGE=, etc.

I am tempted to revert it all.

de...@trex:build$ hammer -j6 --mode=Release SYMBOLS=1 --verbose v8_shell
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
g++ -o 
/usr/local/google/home/deanm/chrome/git/new/src/sconsbuild/Release/obj/v8/src/snapshot-empty.o
-c -m32 -pthread -march=pentium4 -fno-exceptions -msse2 -mfpmath=sse
-DCHROMIUM_BUILD -DNDEBUG
-I/usr/local/google/home/deanm/chrome/git/new/src/sconsbuild/Release/obj/v8/src
-I/usr/local/google/home/deanm/chrome/git/new/src/v8/src
/usr/local/google/home/deanm/chrome/git/new/src/v8/src/snapshot-empty.cc
g++ -o 
/usr/local/google/home/deanm/chrome/git/new/src/sconsbuild/Release/obj/v8/src/accessors.o
-c -m32 -pthread -march=pentium4 -fno-exceptions -msse2 -mfpmath=sse
-DCHROMIUM_BUILD -DNDEBUG
-I/usr/local/google/home/deanm/chrome/git/new/src/sconsbuild/Release/obj/v8/src
-I/usr/local/google/home/deanm/chrome/git/new/src/v8/src
/usr/local/google/home/deanm/chrome/git/new/src/v8/src/accessors.cc
g++ -o 
/usr/local/google/home/deanm/chrome/git/new/src/sconsbuild/Release/obj/v8/src/allocation.o
-c -m32 -pthread -march=pentium4 -fno-exceptions -msse2 -mfpmath=sse
-DCHROMIUM_BUILD -DNDEBUG
-I/usr/local/google/home/deanm/chrome/git/new/src/sconsbuild/Release/obj/v8/src
-I/usr/local/google/home/deanm/chrome/git/new/src/v8/src
/usr/local/google/home/deanm/chrome/git/new/src/v8/src/allocation.cc



On Thu, Apr 2, 2009 at 12:43 PM, Dean McNamee <de...@chromium.org> wrote:
> -lX11 -lXrender -lXext (at least) was dropped in the switch to gyp.  I
> tried to understand how gyp worked or where these were coming from,
> but no luck.
>
> On Thu, Apr 2, 2009 at 12:35 PM, Dean McNamee <de...@chromium.org> wrote:
>> I can't actually get it to build (trying Release for now), I am
>> getting linker errors for X calls, we are probably not linking
>> correctly.  I will debug it :\
>>
>> On Thu, Apr 2, 2009 at 12:11 PM, Dean McNamee <de...@chromium.org> wrote:
>>> Word on the street is that the ccflags are all wrong, and that release
>>> builds aren't being built release properly.
>>>
>>> On Thu, Apr 2, 2009 at 7:23 AM, Mark Mentovai <m...@chromium.org> wrote:
>>>>
>>>> Awesome.  This is seriously good news.  Thanks!
>>>>
>>>> Mark
>>>>
>>>> Steven Knight wrote:
>>>>> Linux builds have been converted to gyp-generated SCons files.
>>>>>
>>>>> I'm in the process of updating the wiki pages to reflect the change.  
>>>>> Here's
>>>>> the executive summary of the most important points (or the ones I can
>>>>> remember):
>>>>>
>>>>>
>>>>>    - The gclient hook will have gyp generate the .scons files for you
>>>>>      after next update
>>>>>
>>>>>    - Output is now generated in src/sconsbuild/{Debug,Release}
>>>>>
>>>>>    - Consequently, it's going to rebuild your (Linux) world after
>>>>>      your first update
>>>>>
>>>>>    - The main build entry point is now the src/build directory;
>>>>>      see below for a little more detail.
>>>>>
>>>>>    - Start using --mode=Release (not --mode=opt) to build the
>>>>>      release version
>>>>>
>>>>>    - LOAD= does not work at the moment, but will shortly (there's a
>>>>>      CL teed up)
>>>>>
>>>>>    - Sorry SHARED=1 people, that's broken again
>>>>>
>>>>> Build instructions:
>>>>>
>>>>> $ cd $CHROMIUM_ROOT/src/build
>>>>> $ hammer [targets]
>>>>>
>>>>> Default is "all".  You can specify any of the targets from the .gyp files 
>>>>> to
>>>>> build just the specified targets.  So:
>>>>>
>>>>> $ cd $CHROMIUM_ROOT/src/build
>>>>> $ hammer app
>>>>> $ ../sconsbuild/Debug/chrome
>>>>>
>>>>> If you prefer to do everything from the src/ directory, use -C (like 
>>>>> make):
>>>>>
>>>>> $ cd $CHROMIUM_ROOT/src
>>>>> $ hammer -C build app
>>>>> $ sconsbuild/Debug/chrome
>>>>>
>>>>> If you have questions or notice problems, you know who to find...
>>>>
>>>> >>>>
>>>>
>>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to