I am not sure. My changes definitely didn't affect that.
I think it might have always been the case, that "source ..." is necessary
before ./bootstrap.
On Thu, Jan 26, 2017 at 6:39 AM, Patricia Shanahan wrote:
> Thanks. That worked.
>
> The step-by-step puts winenv.set.sh after ./bootstrap, and
Thanks. That worked.
The step-by-step puts winenv.set.sh after ./bootstrap, and that used to
work. Do you expect it to work again, or do we need to edit the
instructions?
On 1/25/2017 8:25 PM, Damjan Jovanovic wrote:
Try "source winenv.set.sh" between ./configure and ./bootstrap.
Damjan
On
Try "source winenv.set.sh" between ./configure and ./bootstrap.
Damjan
On Thu, Jan 26, 2017 at 2:20 AM, Patricia Shanahan wrote:
> I am trying to set up a new debug environment, incorporating the recent
> changes to how debug works. Unfortunately, my configure-and-bootstrap
> cannot find dmake.
Hi Marcus;
On 01/25/17 23:41, Marcus wrote:
In general the addition is OK. However, there is not yet agreement what
"supported" means. So, just to add FreeBSD to the list doesn't work as
it's not the same as for Win, Linux, Mac where we have a different
definition.
Marcus
I avoided making c
I am trying to set up a new debug environment, incorporating the recent
changes to how debug works. Unfortunately, my configure-and-bootstrap
cannot find dmake. It looks for it in a different URL from the one
specified as DMAKE_URL from configure.
run_configure.sh contains my configure paramet
In general the addition is OK. However, there is not yet agreement what
"supported" means. So, just to add FreeBSD to the list doesn't work as
it's not the same as for Win, Linux, Mac where we have a different
definition.
Marcus
Am 25.01.2017 um 16:07 schrieb p...@apache.org:
Author: pfg
D
FWD to OP, not subscribed to the list.
Hagar
Le 24/01/2017 à 16:51, FR web forum a écrit :
https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=78706&hilit=chromebook
- Mail original -
De: "Conner Holt"
À: dev@openoffice.apache.org
Envoyé: Mardi 24 Janvier 2017 16:02:52
Objet: Ch
On 25 Jan, Damjan Jovanovic wrote:
> Hi
>
> For a while I've noticed how gbuild modules don't have debug symbols unless
> built with the maximum debug level ("./configure --enable-debug" globally
> or "build debug=true" per module) which also produces oceans of log
> messages we usually don't want
Hi
For a while I've noticed how gbuild modules don't have debug symbols unless
built with the maximum debug level ("./configure --enable-debug" globally
or "build debug=true" per module) which also produces oceans of log
messages we usually don't want.
In r1780246, I've finally changed debugging
Am 24.01.2017 um 23:02 schrieb Andrea Pescetti:
>
> I see some risk of confusion here. I mean, there is surely a set of
> "privileged" platforms that are those for which we build and make
> available releases from our download page: Windows, MacOS X, and Linux
> variants. Then there is a set of "
> -Original Message-
> From: Simon Phipps [mailto:si...@webmink.com]
> In fact Go-OO was started by Ximian in 2003, long before Novell bought
> them, as a convenient build system for developers not working
> within Sun.
> The difficulty of getting the Sun team to accept patches, and
11 matches
Mail list logo
