[Mesa-dev] [PATCH] Allow static libstdc++/libgcc linking if selected

Vivek Das Mohapatra vivek at collabora.com
Sun Mar 15 17:44:23 PDT 2015


>> +    fi;
>> +    STATIC_STDCPP_LIBS="-l:libgcc.a -l:libgcc_eh.a -l:libstdc++.a";
>> +    STATIC_STDCPP_LDFLAGS="-static-libgcc -static-libstdc++ \
>> +                          -l:libgcc.a -l:libstdc++.a \
> Do we need this line considering the STATIC_STDCPP_LIBS above ?

Yes, I can't remember the exact failure mode but they both had to
be there to make things work: I can run a build without it and
save the error(s) if you're interested in the details.

>>  GALLIUM_COMMON_LIB_DEPS = \
>>         -lm \
>> +       $(STATIC_STDCPP_LIBS) \
> Don't the classic dri modules need this? Afaict you'll end up removing
> the references (link) to the C++ runtime and libgcc_s and things won't
> end up too well.

I've been doing a bit of work to make the patch compatible with static
llvm (I had link failures), I'll check those as well. Currently I have
no .so which pull in libstdc++ or libgcc_s, so I think I've got it covered.
I'll post another patch when I've addressed your other comments.



More information about the mesa-dev mailing list