Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Michael Stahl-2 wrote
...
can you patch in an echo around the CC_VERSION=`"${CC}" ... line to see
what the value of $CC and $CC_VERSION is?

I'll give a try after my day time job but if I do this, it means I should
just run "make nss.build" and not "make nss.clean && make nss.build" since
the clean would remove the patch. Is it ok?


Michael Stahl-2 wrote
did you do any changes from before when (presumably) the build worked,
or is this broken since the NSS upgrade commit
6e7991dfd8c54a833f4a9795a0d57f4690e92e6b ?

I must recognize I don't remember, it's been some time.
In fact, some months ago, I had succeeeded in building with 32 bits. Then,
with the same sources but with a brand new cygwin, I had tried with 64bits,
it had failed.
Then weeks later, I wanted to revert to 32 bits (with a brand new Cygwin32
but still with same sources) since 64bits building on Windows seemed to be
on-progress work.
In brief, I wonder if there could be any remnants with 64bits tests and
finally if I shouldn't scratch the whole thing:cygwin, LO sources, Visual
Studio and reinstall/redownload all the things to be sure.

Anyway, I'll keep you informed of this test.

Julien



--
View this message in context: 
http://nabble.documentfoundation.org/Fail-to-build-on-Windows-7-32-bits-tp4156056p4157666.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.