Re: Debian install question
Hi, Sebastien!
I'm Cc'ing this to debian-openoffice, people out there know these problems and
workarounds better then me.
++ 23/05/02 11:21 +0200 - S?bastien Lefebvre:
Hi Peter,
First, I'd like to thank you for your contributions, particularly on the
openoffice/Debian project.Openoffice is what I miss on my laptop to run
Debian 100% of time.
I'm trying to install Openoffice on my woody (KDE 2.2.2, Kernel 2.2.20)
without success :
I first tried to install Openoffice from .tar.gz as I ignored the
existence of a Deb package. When I launch the installer, I have brown
rectangles, plus 2 or 3 lines appearing on the screen and the installer
seems to be nearly freezed. I tried it as user and root without success,
and with, more or less, the same results.
I then added the apt source in order to get the Deb package. But when
it's time to launch the installer (as user), I have the same problem
(rectangles, freeze etc...)
So I thought KDE could be involved into this problem and decided to use
Gnome 1.4 for the install :same result
I also used a normal Xsession without success.
Somebody had the same problem on a french newsgroup but nobody had a
piece of an answer.
Do you have any idea that can help me ?
Thanks a lot in advance
S?bastien
--
typedef enum{ COOL, SUCKS, OTSTOY }subjectValue; class Subject { ...
subjectValue value; ... public: ... void setValue (subjectValue newValue)
{value = newValue}}; class Matan : Subject { ... }; int main(){ Matan
*vmkmatan = new Matan(); vmkmatan-setValue(OTSTOY); }
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tcsh dependency
++ 16/05/02 19:58 +0200 - Jerome Warnier: Does anyone know why tcsh is needed to build OOo and if it is really needed? Yes, it is really needed. Some scripts in OOo build system are written in tcsh. Does the build-depend contain this? Yes. Nidd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Font hinting problems solved - sort of?
Really cool. Thanks. Phil Messenger [EMAIL PROTECTED] writes: Hi, You're probably aware that by default the font hinting with antialiased fonts in OpenOffice leaves a lot to be desired. The font FAQ indicates that this is because of the Apple patent problems with Freetype. Still, I've discovered that it's fairly trivial to work aroud this without actually modifying anything or rebuilding OpenOffice. This obviously depends on you having a freetype library on your system which does have autohinting and the bytecode interpreter enabled. Simply: export LD_PRELOAD=/usr/lib/libfreetype.so.6 before executing 'openoffice' results in nicely hinted fonts. Without: http://www.btinternet.com/~philmes/oo-freetype/without.png With: http://www.btinternet.com/~philmes/oo-freetype/with.png Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Peter Novodvorsky Deadheads, unite! http://myxomop.com/NiddWiki [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: deb for netbeans
Tom Tromey [EMAIL PROTECTED] writes: Chris == Chris Halls [EMAIL PROTECTED] writes: Chris No, it's not fixed yet. I am still building OOo packages with Chris an installed Blackdown JDK. Peter is working on removing Java Chris still. We have a much easier task than Netbeans, since Java Chris support is an optional extra, and very little of the build is Chris done using a Java compiler. Is it possible to build with a free java compiler, like gcj? no, not yet. But I hope that someone tries to do it. :) -- Peter Novodvorsky Deadheads, unite! http://myxomop.com/NiddWiki [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Building systems
++ 06/03/02 11:34 +0100 - Bernhard R. Link: Their system does quite an good job to comapile an huge pice of code, build around the compiler errors of dozens of architectures trying not to interfer with strange environments to get an office suite in one piece and doing on their own. I have only one question: Bernhard, how are you going to maintain your oo package's makefiles if they are not incorporated in openoffice source tree? Bye, Nidd.
Apologizes and progress
Hello, folks! I'm returning to my previous live cycles because problems with work and stody are almost solved. First, I want to apoligize Bernhard. I have to say that he began very good work and we need to support him in his deeds. His udk packages are great, and it seems that he developed unified algorithm for moving OpenOffice to GNU Make and more clean build system. But still it is long term way and I think we need to keep doing to branches for packaging: 1. Bad ugly huge openoffice package. I'm not sure that we need to make some big modifications for it. This is rather simple work and I'd like Jan to reserve some night to spend it on IRC and I'll try to teach him all tricks in this package, so he will be able to update this huge package with new versions coming. If anyone else intrested in this job, you're welcome. 2. Bright Bernhard's packages. Bernhard, can you send some status of work to the list? What are you working on, how's your progress? Thanks, it's great to work with you again guys. -- Peter NovodvorskyDeadheads, unite! Moscow State University, CS dept. [EMAIL PROTECTED] Debian Project [EMAIL PROTECTED] ALT Linux Team, Russia [EMAIL PROTECTED]
[erik.tews@gmx.net (Erik Tews)] Some more openoffice-bugs
---BeginMessage--- Hi Your deb is going to use bz2cat to extract the deb. On my woody-system, this package is called bzcat. You should rename it in the Makefile. ---End Message--- -- Peter Novodvorsky. Moscow State University, CS faculty -- [EMAIL PROTECTED] Debian Project -- [EMAIL PROTECTED] ALT Linux Team, Russia -- [EMAIL PROTECTED]
Re: Status of work on OpenOffice
Hello! I want to say, that you're talking about big problems that can happen in future. We need to make usable openoffice packages now. Frankly speaking, openoffice package that I've released on ~nidd/debian/unstable is buildable by autobuilder. If you could help us with making this package (good postinst/prerm scripts registering components??), you are welcome. But your words about ``future problems'' are not really helpful for us. Sorry, if my letter seems to be offensive, it's not true. Bernhard R. Link [EMAIL PROTECTED] writes: * Jan-Hendrik Palic [EMAIL PROTECTED] [011028 12:33]: Peter has made a picture [2] with the builddependency- tree, that shows us, splitting the source is impossible. [2] http://www.altlinux.ru/~nidd/oo/oo-components-depends.psz Wow, I had expected an much more complex tree. If you remove everything that should be replaced by in the final packages with the libraries supplied with debian, than there is not that much remaining. I had expected quite an mess, but it seems to have clear hirachies. I think most bejond the odk (Meta-)Package can be put in 2-5 Packages (perhaps also in 1, but I think if people adopt the odk for other projects, they will be glad to get it in reasonable sub-packages), The parts around the chaos might be worth to investigate, perhaps there will be some work upstream about this. I still think splitting the source in packages is the way to go for OOo in the long run. Upstream is modular, and reflecting this in the packaging will help the builders and perhaps allowing other odk-software to be packages easily. (If it will exist some day). Please, can you be more verbose? I still don't understand why splitting source in several source packages will help. It won't help autobuilders anyhow. I don't see any matter to do it, and it is quite hard to do. Could describe your point of view in details? In the meantime I think it is an good idea if we have one or some packages, that are not that much changed from upstream, as it fullfills an need for them, that is somewhat urgent. As these packages will most likely not work together with the autobuilders (they do not have /proc mounted in the chroot, do they?) Of course they do! -- Peter Novodvorsky http://www.altlinux.ru/AltLinux Team, Russia Debian.Org http://debian.org/~nidd Debian --- no need to wait for tomorrow.
Re: test Debian packages of openoffice
Hello! Jan-Hendrik Palic [EMAIL PROTECTED] writes: I'm not a debian-maintainer, but I will become on soon, I hope. But ... On Tue, Oct 23, 2001 at 11:30:41PM +0400, Peter Novodvorsky wrote: I've managed to build debian packages of openoffice. Build and install process is completely uninteractive and doesn't real xserver running. That's because of Xvfb and autoresponse solutions. (I'm not using XTest of course). Hmmm .. ok .. ok ... I'm fully disagree with your package. Didn't I see a mail, in what you said, that you intent to pack OpenOffice, too? Yes, you've seen, that is the mail you replied to. I mean, we had have work together, we were discussing on debian-openoffice, how we pack OpenOffice and you did it and you did nothing, we discussed it. Sorry, couldn't parse you phrase. As I see, you still don't have any packages and no real progress. ;-( But worst thing, IMHO, one deb for the whole OpenOffice, that's heavy! Yes, I don't like it too. But it isn't final release, true? Now we can do tweaking, etc. In fact I'l show you come calculations: Openoffice installed232M Help and other arch-indep 30M Jar files(will be excluded) 2.1M So files (libraries)180M Rdb Files 7M Everything else ... So, if we install one of highlevel openoffice apps, it requires all rdb files and mostly all libraries. So it's already ~170M. When you get arch-independant files you get 200M. So for one application you will install whole OpenOffice! Why won't we put it in one package? I've saw ITP onopenoffice by Noel Koethe, Clay Crouch and Adrian Bunk. Are you still trying to build openoffice in a package? is it ok, if I'll ITP it too and upload? You forgotten me, I did an ITP to retitle 101762 ITP: openoffice Bug#101762: RFP: openoffice -- The OpenOffice office suite. Changed Bug title. I'm sorry, I was wrong :( 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. You know, JDK is highly non-free and not in debian. Its only in incoming. So, if OpenOffice comes in an autobuilder, it will not be build, because, JDK is not able to be installed by apt. True. My thought of OpenOffice was: We grap trough the source and makes it compileable on as much as possible on several arches. Therefor, we have to wait for gcc-3.0 support. Actually, the source 638c does not kompile with gcc-3.0, libstlport-4.0 doesn't kompile with gcc-3.0, too. The next thing, I want is, that we became JDK-independent with OpenOffice and gpc-indipendent, because, OpenOffice will depend on this, and it will not came into main. But to get the whole Debian- Support, OpenOffice should came into main, this means a lot of work. Do you agree that we need to have some working version that we can edit? And last but not least, I don't want to download a 180MB debian-package. It's only 71 MB :). OpenOffice is modular, so we should work with it and provide smaller OpenOfficepackages! Car is also modular, but every part of it depends on another part (did you see sources of openoffice :)). Package uses doogie build system so it will be easy to work in team, if you would like that. Hey .. what do you think, why we are discussing on debian-openoffice? As I see you're not discussing that much. When I looked at mail archives I thought: These guys don't discuss anything, they can't even build openoffice (I looked in august), I need to make a first package to boost the progress. So did you have any progress in last two months? Here is my TODO, I'd like to hear what you are working on, to distribute our work. We are working on understanding the source and make it provideable for debian. Just in time, this peace of source is not providable for debian. OK, if you can tell my _why_ do you think so, I'll agree. - Divide everything in arch-dependant and arch independant parts I think, it would be better to see, which parts are in debian. IDL for example is right packaged in debian. I think, it is nessessary to have a look after parts in OpenOffice, which could be provided by well known libs in debian. This would debugging much easier... IMHO In my packages libstlport and libgpcl are not in openoffice distribution already. - After previous step is done, start porting to other platforms. (It's great that openoffice was ported to powerpc, yay!) No ... on the one Hand, the source must compileable with a compiler, which present on all arches, we have in debian. There are two
test Debian packages of openoffice
Hello! I've managed to build debian packages of openoffice. Build and install process is completely uninteractive and doesn't real xserver running. That's because of Xvfb and autoresponse solutions. (I'm not using XTest of course). I've saw ITP onopenoffice by Noel Koethe, Clay Crouch and Adrian Bunk. Are you still trying to build openoffice in a package? is it ok, if I'll ITP it too and upload? 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. Package uses doogie build system so it will be easy to work in team, if you would like that. Here is my TODO, I'd like to hear what you are working on, to distribute our work. ToDo: - Get rid of java - Divide everything in arch-dependant and arch independant parts - After previous step is done, start porting to other platforms. (It's great that openoffice was ported to powerpc, yay!) - Extract language packs and make multi languagable openoffice. It can be done with symlinks: /usr/lib/openoffice/default/[STANDARD OPENOFFICE INSTALL] ru/links to all standard files excluding russian specific resource files and russian registry. en_US - default ru_RU.KOI8-R - ru de/links to all standard files excluding german specific resource files and german registry. de_DE - de I have already wrapper script that makes uninteractive user install from /usr/lib/openoffice in case it isn't done already. So I will include also such test: if [ -d /usr/lib/openoffice/$LANG ]; do /usr/lib/openoffice/$LANG/program/soffice else /usr/lib/openoffice/default/program/soffice fi Suggestions are welcome. Thank you. [1] http://people.debian.org/~nidd/openoffice_0.638c-1.diff.gz [2] http://people.altlinux.ru/nidd/stlport4.0_4.0-0.1.diff.gz -- Peter Novodvorsky http://www.altlinux.ru/AltLinux Team, Russia Debian.Org http://debian.org/~nidd Debian --- no need to wait for tomorrow.
Re: Build of OpenOffice 683c on PPC
Jan-Hendrik Palic [EMAIL PROTECTED] writes: hi there ... :) It seems, that OpenOffice will build on I386, right? With gcc2.95 or gcc3.0? I'm working on building OpenOffice on PPC, but I have problem with gcj. Is it possible to build OpenOffice with gcj? -- Peter Novodvorsky http://www.altlinux.ru/AltLinux Team, Russia Debian.Org http://debian.org/~nidd Debian --- no need to wait for tomorrow.
current state of OO packages
Hello, people! What is the current state of packaging openoffice? Please make things a bit more public, k? -- Peter Novodvorsky http://www.altlinux.ru/AltLinux Team, Russia Debian.Org http://debian.org/~nidd Debian --- no need to wait for tomorrow.
Building OOo
Hello, I've written something that I name
Building OpenOffice For Debian mini-HOWTO
-
(C) Peter 'Nidd' Novodvorsky
Probably it will work on any other modern distribution, but I tried
only Debian.
System requires: Good processor, 128 Mb (256MB better),
2,5 Gb hard disk space.
Needed software and files:
- OpenOffice 638C from CVS (I didn't try 640).
- STLPort _4.0_ You won't build it with debian's 4.1
package. You can get package diff from here
http://people.altlinux.ru/nidd/stlport4.0_4.0-0.1.diff.gz
and stlport4.0 from stlport.com, and then build package
yourself (Currently I don't have enough connection
to put binaries)
- gcc 2.95.x.
- Java JDK 1.3.1. You can get it from blackdown.org:
deb
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/debian woody
non-free
This JDK package is extremly bad (it puts everything in /usr/java).
If you want, you can make FHS-compilant package with JDK1.3.1,
But you'll need to emulate java home, like we will do with
STLPort (see below).
- Sources for libgpcl0. (apt-get --tar-only source libgpcl0)
- little patch:
http://people.altlinux.ru/nidd/openoffice-mozsrc.patch
Building
Get OpenOffice from OO's cvs:
CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs
Password: anoncvs
Module: OpenOffice
Tag: OO638C
Build and install STLPort 4.0, then install JDK.
Copy gpc.{c,h} files from libgpcl distribution to
$OPENOFFICE_SOURCE_ROOT/external/gpc. Apply patch to the source tree
(with -p0 when PWD=$OPENOFFICE_SOURCE_ROOT). Make a temporary directory,
for example /tmp/stlport4. Make symlinks there:
lrwxrwxrwx1 nidd nidd 12 Sep 23 16:40 include - /usr/include
lrwxrwxrwx1 nidd nidd8 Sep 23 16:07 lib - /usr/lib
Now you are ready to build openoffice.
pushd $OPENOFFICE_SOURCE_ROOT/config_office
./configure --with-stlport4-home=/tmp/stlport4
--with-jdk-home=/usr/java/jdk1.3.1/
cd ..
csh -c 'source LinuxIntelEnv.Set; ./bootstrap; dmake'
# dmake ends with error but it's ok
cp /tmp/stlport4/libstlport_gcc.so
$OPENOFFICE_SOURCE_ROOT/solver/638/unxlngi3.pro/lib
csh -c 'source LinuxIntelEnv.Set; cd instsetoo; build'
popd
Now you have english oo distribution in
$OPENOFFICE_SOURCE_ROOT/instsetoo/unxlngi3.pro/01
german in
$OPENOFFICE_SOURCE_ROOT/instsetoo/unxlngi3.pro/49
english impression player in
$OPENOFFICE_SOURCE_ROOT/instsetoo/unxlngi3.pro/player/01
german in
$OPENOFFICE_SOURCE_ROOT/instsetoo/unxlngi3.pro/player/49
If you want to build customized version of OpenOffice for your
language, remove unset RES_$LANG in the end of LinuxIntelEnv.Set
and put setenv RES_$LANG=TRUE there. Then rebuild openoffice (you
don't need to remove all the source tree or even make clean).
TO DO List
--
1). Understand setup2's install response mode, so we could install openoffice
un-interactively and we could build packages. Still we need $DISPLAY for
setup2 and bmp utility. Needed skills: Good C++ reader.
2). Hack bmpmaker (tools/bmpmaker) to remove it's $DISPLAY dependancy.
I did some exploration here. You will need to build vcl project with
-DREMOTE_APPSERVER, which is done by ``dmake remote=true''. Needed
skills: make/dmake, C++ writer.
3). Hack setup2, kill it's ui and remove it's dependancy on $DISPLAY.
Needed skills: Goog C++ writer, you'll need to understand all OpenOffice
infrastructure.
After 3), we will have working Debian packages, that will be autobuildable
by autobuilders without $DISPLAY (no, Branden, there is no $DISPLAY
on every screen).
Documentation
-
All documentation can be found on www.openoffice.org. I've gathered some
documents and made a tarball. It will be on
http://people.altlinux.ru/nidd/oo_docs.tar.gz
as soon as it will be uploaded.
Programmers, I suggest you to go to api.openoffice.org directly. There
is good documentation in tarballs already, you won't have to and open
link by link to find html-docs.
Currently I am making hyphenation engine for OpenOffice and building it
for Debian is my next step. So tasks of Todo are free and are waiting
for their solvers.
Good night.
And sorry for bad english,
I hope content compensates it.
--
Peter Novodvorsky http://www.altlinux.ru/AltLinux Team, Russia
Debian.Org http://debian.org/~nidd
Debian --- no need to wait for tomorrow.
