Re: fixes for lyx-1.3.4 on OpenBSD

2004-03-01 Thread Zvezdan Petkovic
On Mon, Mar 01, 2004 at 05:24:49PM +0100, Jean-Marc Lasgouttes wrote: > > "Zvezdan" == Zvezdan Petkovic <[EMAIL PROTECTED]> writes: > > Zvezdan> Hello everybody, I've built a port of lyx-1.3.4 for OpenBSD. > Zvezdan> Here are the fixes I had to apply. > > Hi Zvezdan, > > Following the discus

Re: fixes for lyx-1.3.4 on OpenBSD

2004-03-01 Thread Jean-Marc Lasgouttes
> "Zvezdan" == Zvezdan Petkovic <[EMAIL PROTECTED]> writes: Zvezdan> Hello everybody, I've built a port of lyx-1.3.4 for OpenBSD. Zvezdan> Here are the fixes I had to apply. Hi Zvezdan, Following the discussion of your patches, I have applied the qt.m4 patch to HEAD and BRANCH_1_3_X, and the

Re: fixes for lyx-1.3.4 on OpenBSD

2004-03-01 Thread Lars Gullik Bjønnes
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Angus Leeming <[EMAIL PROTECTED]> writes: > | | Zvezdan Petkovic wrote: >> >>> Hello everybody, >>> >>> I've built a port of lyx-1.3.4 for OpenBSD. >>> Here are the fixes I had to apply. >> >>> 3. I had to patch boost platform specific file. It m

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-25 Thread Zvezdan Petkovic
Angus, On Wed, Feb 25, 2004 at 09:29:42AM +, Angus Leeming wrote: > I remember a chat I had with Paul Smith on the gnu-make list. > Basically, he suggested that if I *had* to use a syntax common to all > makes then the only way was > > .C:.ui > $${HEADER}=... \ (can't remember t

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-25 Thread Angus Leeming
Zvezdan Petkovic wrote: > Even worse is the third case we have there: > > %.C: %.h %.ui > $(UIC) $(UICFLAGS) -impl $^ -o $@ > > This is basically, telling that you make X.C file using X.h file, > but > they also depend on X.ui. You can't do that with suffix rules. > > .h.C: X.ui > > is a wrong

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread John Levon
On Tue, Feb 24, 2004 at 08:11:28PM -0500, Zvezdan Petkovic wrote: > Right. But LyX config didn't do that. It bailed out because it I guess you missed the tone of my comments. "It would be nice if they'd done *this* in the first place" not "We won't fix it because I want *this*". I'm just ranti

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
On Tue, Feb 24, 2004 at 06:13:42PM +, John Levon wrote: > No you don't. qt-config would default to the "system" Qt, as I showed > you in the fake ls output. In the case above, qt3 with mt. If a program > depends on qt2 or non-mt, it specifically runs with --no-mt or qt-config > -v 2 or whatever

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread John Levon
On Tue, Feb 24, 2004 at 12:56:25PM -0500, Zvezdan Petkovic wrote: > I suspect the problem is when a user has KDE with qt3-mt dependency, > and perhaps a single application which either doesn't support threading > and depends on qt3 or even qt2. Then you have both installed. > > If your configure

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
On Tue, Feb 24, 2004 at 05:22:17PM +, John Levon wrote: > with --moc, --uic options etc. *That's* sane. I suspect the problem is when a user has KDE with qt3-mt dependency, and perhaps a single application which either doesn't support threading and depends on qt3 or even qt2. Then you have b

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
On Tue, Feb 24, 2004 at 12:01:43PM +0100, Jean-Marc Lasgouttes wrote: > > What about asking on the automake list whether there is some provision > to do what we want to do? > > And what is the main problem in this rule? The fact that append _moc > to the name? Do we really need to do that? No.

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
On Tue, Feb 24, 2004 at 11:32:14AM +, Angus Leeming wrote: > Lars Gullik Bjønnes wrote: > > What about the ".for" stuff and LOOPLIST? > > > > (.for might be part of "standard" make, but I have never seen it > > used before.) > > I've never seen it before either, but I'll try it out. I have a

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread John Levon
On Tue, Feb 24, 2004 at 12:10:32PM -0500, Zvezdan Petkovic wrote: > LyX configure script looks for moc2 and moc only. > On OpenBSD it happens to be moc3-mt. And it never gets found. Ugh. What a mess. > The only way to have all of them in the same time is to call them > differently (moc2, moc3,

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
On Tue, Feb 24, 2004 at 11:23:47AM +0100, Lars Gullik Bjønnes wrote: > What about the ".for" stuff and LOOPLIST? > > (.for might be part of "standard" make, but I have never seen it > used before.) It's BSD make specific. As I mentioned in the previous mail, the good thing about both GNU make an

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
On Tue, Feb 24, 2004 at 10:36:08AM +0100, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > | Excellent! I tried to remove the gnu make dependency myself but these > | three had me stumped. > > Except that I do not think we can use it as is... the am__object_X > stuff might

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Zvezdan Petkovic
John, On Tue, Feb 24, 2004 at 02:11:02AM +, John Levon wrote: > On Mon, Feb 23, 2004 at 07:45:15PM -0500, Zvezdan Petkovic wrote: > > >automagically defined. The trouble is that LyX's configure doesn't > >respect MOC and UIC environment variables and overwrites them. > > > >The

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Angus Leeming
Lars Gullik Bjønnes wrote: > What about the ".for" stuff and LOOPLIST? > > (.for might be part of "standard" make, but I have never seen it > used before.) I've never seen it before either, but I'll try it out. I have a machine here running DEC/Compaq/HP Alpha with a 1.3.x cvs tree. I've applie

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Jean-Marc Lasgouttes
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> I understand your feelings entirely. GNU make's syntax is Angus> extremely intuitive. However, there are many flavours of make Angus> out there other than GNU and BSD. Unfortunately only GNU make Angus> understands gnu-isms. Angus>

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: >> Except that I do not think we can use it as is... the am__object_X >> stuff might AFAIK change with different versions of automake. > | I don't think that the patch alters the am__object_X stuff. | Just the dependency rules

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Angus Leeming
Lars Gullik Bjønnes wrote: > Except that I do not think we can use it as is... the am__object_X > stuff might AFAIK change with different versions of automake. I don't think that the patch alters the am__object_X stuff. Just the dependency rules: + ${file}: ${srcdir}/../${file:_moc.C=.h} +

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | Zvezdan Petkovic wrote: > >> Hello everybody, >> >> I've built a port of lyx-1.3.4 for OpenBSD. >> Here are the fixes I had to apply. > >> 3. I had to patch boost platform specific file. It makes a wrong >>assumption that all BSDs have macro based

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-24 Thread Angus Leeming
Zvezdan Petkovic wrote: > Hello everybody, > > I've built a port of lyx-1.3.4 for OpenBSD. > Here are the fixes I had to apply. > 3. I had to patch boost platform specific file. It makes a wrong >assumption that all BSDs have macro based . Patch is >attached below. Lars, can I leave t

Re: fixes for lyx-1.3.4 on OpenBSD

2004-02-23 Thread John Levon
On Mon, Feb 23, 2004 at 07:45:15PM -0500, Zvezdan Petkovic wrote: >automagically defined. The trouble is that LyX's configure doesn't >respect MOC and UIC environment variables and overwrites them. > >The patch mentioned in the comment above that would fix this is >attached below

fixes for lyx-1.3.4 on OpenBSD

2004-02-23 Thread Zvezdan Petkovic
Hello everybody, I've built a port of lyx-1.3.4 for OpenBSD. Here are the fixes I had to apply. 1. OpenBSD uses special conventions for storing qt files to be able to have multiple versions installed at the same time. When building a port it's enough to add MODULES+= qt