This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gcc-in-cxx] Get past stage1 on darwin
Tobias SchlÃter <tobias.schlueter@physik.uni-muenchen.de> writes:
> Ian Lance Taylor wrote:
>
>> Does the directory
>>
>> /Users/tobi/src/gcc-in-cxx/build/prev-i386-apple-darwin8.11.1
>>
>> exist? Presumably it would contain a libgcc subdirectory. If it does
>> not exist, where is the stage1 libgcc?
>
> It is there, and libgcc is indeed built. On the other hand ...
>
>> Does the build log show that libstdc++-v3 was built in stage1? It
>> should appear in between building the stage1 libgcc and starting the
>> stage2 build.
>
> the first mention of libstdc++ in the build logs is during the
> configuration of stage2. The build proceeds directly from building
> libgcc to stage2.
Odd. When I build, I see libstdc++-v3 building in stage 1. This
happens bcause bootstrap=true is set for the libstdc++-v3 target module
in the top level Makefile.def. This then adds a dependency
all-stage1: all-stage1-target-libstdc++-v3
in the top level Makefile.in.
The top level configure script does apply extra substitutions to adjust
@if statements in Makefile.in when generating Makefile, by adding lines
to ac_extra_sub. I wonder if the '+' charaacters in libstdc++-v3 could
be confusing that somehow. In my generated top level Makefile, I see
lines like this:
.PHONY: all-stage1-target-libstdc++-v3 maybe-all-stage1-target-libstdc++-v3
.PHONY: clean-stage1-target-libstdc++-v3 maybe-clean-stage1-target-libstdc++-v3
maybe-all-stage1-target-libstdc++-v3:
maybe-clean-stage1-target-libstdc++-v3:
maybe-all-stage1-target-libstdc++-v3: all-stage1-target-libstdc++-v3
all-stage1: all-stage1-target-libstdc++-v3
TARGET-stage1-target-libstdc++-v3 = $(TARGET-target-libstdc++-v3)
all-stage1-target-libstdc++-v3: configure-stage1-target-libstdc++-v3
In Makefile.in the key all-stage1: line is enclosed in
@if target-libstdc++-v3-bootstrap
What do you see in your Makefile?
Ian