On Thu, 2002-02-21 at 20:09, Jan-Hendrik Palic wrote:
> Hi ..
>
> I should write mail, wenn Im very tired .. sorry ..
>
> Ok. I told, that I applied the bison patch from IssueZilla to get
> OpenOffice build with bison 1.3x. It works but shortly after that, I got
> this:
>
> ../../unxlngppc.pro
On Fri, 2002-02-15 at 21:09, Jan-Hendrik Palic wrote:
> Hi ...
>
> I'm working on packaging OO for debian.
> But I have some problem, with bison and yacc.
> The problem in idlc is fixed by a patch in discuss-openoffice ML.
>
This is a bison 1.30 or 1.31 problem. The file naming rules have
cha
On Mon, 2002-01-28 at 23:55, Erik Tews wrote:
> Aeh, I thought you are looking for a person willing to test a
> openoffice-source-deb on ia32, not the normal openoffice source
> distribution. I have now tried to compile this for some times but never
> succeeded. So is there a person who has created
On Mon, 2002-01-28 at 21:46, Erik Tews wrote:
> On Mon, Jan 28, 2002 at 01:42:17AM +0100, Jan-Hendrik Palic wrote:
>
> I got a dual pIII with 550 MHz and 768 MB ram. Debian Woody is installed
> on LVM and a lot of distspace is left. So I will be able to test the
> build there. But the box has no p
There is something fishy with the woody builds. Potato apparently works
OK but setup crashes when build under woody. This is obviously a
problem for others because there is debugging lines around the line I
commented out in CVS. This one needs to be solved properly.
Here is my original post to
On Fri, 2002-01-18 at 23:39, Ken Foskey wrote:
>
> The bison saga continues. I am using an unsupported version of bison
> but I cannot figure these errors from rsc:
This is what I understand the problem to be:
rsc uses bison to generate its parser. Bison runs with
bison -d
Matthias Klose wrote:
Jan-Hendrik Palic writes:
The change from javac to gcj is the next problem. gcj will not be able
to compile the javasource in openoffice, kaffe isn't it to.
If anyone knows a solution, please tell us!
would gcj from the HEAD branch (3.1) a solution?
I was talking ab
Peter Novodvorsky wrote:
Okey, the diff.gz is here[1], it requires libstlport4.0[-dev]. Debian
has only 4.1 packages. You can find stlport4.0 diffs here[2]. You'll need
j2sdk1.3 from blackdown.org. I couldn't upload binary because of small
bandwidth.
For what it is worth I actually run OO
Jan-Hendrik Palic wrote:
hi ..
I upgradet my sidbox (PPC) yesterday, but know .. at bootstrap, I many
errors, and I don't know, what lib is responsible for it!
I attached the output!
Does anyone has a hint?
Stupid question, do you have patch installed? This is not a deb
default and thi
13.10.2001 13:15 Uhr schrieb Ken Foskey ([EMAIL PROTECTED]):
This brings me back to the original question. How does
unxlngi3.pro/inc/com/sun/star/awt/VclWindowPeerAttribute.hdl get created?
KenF
Usually all *.hdl files are C++-headers generated from a UNO registry by
cppumaker. The compl
Benhard told me about some features in the idlc code. I have worked
though the code to make it compile -Wall. This has exposed some
features with the error handling but would not nessecarily explain any
crash in it. Some printing as string of structures not the text within.
Anyway there ar
Peter Novodvorsky wrote:
- little patch:
http://people.altlinux.ru/nidd/openoffice-mozsrc.patch
This is no longer required. They forgot to tag a new version properly,
it is now corrected and verified by me.
By the way thanks for the effort, can you post a URL for this on the
web
Multiple replies
To convert Open Office to auto anything is impossible, IMHO. No doubt
there will be a development thread that tries and they might suceed.
Frankly this is not my interest. The process works well so long as
you do not drift from the script to get the thing compiling. I
Martin Schulze wrote:
Have you considered running a semi-public development CVS Repository
for the OpenOffice source already? You could request /cvs/openoffice
on cvs.debian.org and move the current source into it.
Why have two source repositories. This seems a little risky. If you
can pa
14 matches
Mail list logo
