Re: [Libreoffice] New build problem

Sidney Markowitz <sidney -AT- sidney.com>
Sat, 02 Oct 2010 17:03:38 +1300

Sidney Markowitz wrote, On 2/10/10 2:34 PM:

Entering .../build/lb/boost

cd ./unxlngx6.pro/misc/build/boost_1_39_0/libs/thread/src/win32 && dmake
dmake:  Error: -- No target
dmake:  Error code 255, while making 'boostthreadlib'


It looks like this commit is the problem:

Author: Tor Lillqvist <tlillqvist@   >
Date:   Sat Oct 2 00:39:37 2010 +0300

    Build the thread-related code on Windows into a library

I don't understand what the code is supposed to be in
clone/libs-extern-sys/boost/makefile.mak, because it looks like the build line
at the end is in a directory specific to win32 but the conditionalization
doesn't specify Windows only.

Context

[Libreoffice] Install problem · Seo Sanghyeon
- Re: [Libreoffice] Install problem · Michael Meeks
  - Re: [Libreoffice] Install problem · krishnan parthasarathi
    - Re: [Libreoffice] Install problem · Michael Meeks
      - Re: [Libreoffice] Install problem · sidney
        
        Re: [Libreoffice] Install problem · Kohei Yoshida
        
        Re: [Libreoffice] Install problem · Sidney Markowitz
        
        [Libreoffice] New build problem · Sidney Markowitz
        Re: [Libreoffice] New build problem · Sidney Markowitz
        Re: [Libreoffice] New build problem · Sidney Markowitz
        
        Re: [Libreoffice] New build problem · Tor Lillqvist
        Re: [Libreoffice] New build problem · Tor Lillqvist
        Re: [Libreoffice] New build problem · Sidney Markowitz
      - Re: [Libreoffice] Install problem · krishnan parthasarathi

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.