Re: Qt configure patch #2

2002-09-12 Thread Andre Poenitz
On Thu, Sep 12, 2002 at 03:51:06PM +0100, Angus Leeming wrote: > > | of course. > > > > as one stream? > > > > mov -v 2>&1 | cat > > Thanks. And can stderr be piped on its own? (moc -v 2> | cat > doesn't work). moc -v 2>&1 >/dev/null | ... should work I think Andre' -- Those who desire to g

Re: Qt configure patch #2

2002-09-12 Thread Angus Leeming
On Thursday 12 September 2002 4:33 pm, John Levon wrote: > Yes, it wouldn't. I'm talking horseshit. > Try moc -v 2>&1 >/dev/null instead Splendid! A

Re: Qt configure patch #2

2002-09-12 Thread John Levon
On Thu, Sep 12, 2002 at 03:56:28PM +0100, Angus Leeming wrote: > Doesn't work here > aleem@thorax:aleem$ moc -v >/dev/null 2>&1 | cat > aleem@thorax:aleem$ Yes, it wouldn't. I'm talking horseshit. Try moc -v 2>&1 >/dev/null instead regards john -- "To be fair i do look quite like a monkey ...

Re: Qt configure patch #2

2002-09-12 Thread Angus Leeming
On Thursday 12 September 2002 4:24 pm, John Levon wrote: > On Thu, Sep 12, 2002 at 03:51:06PM +0100, Angus Leeming wrote: > > Thanks. And can stderr be piped on its own? (moc -v 2> | cat > > doesn't work). > > moc -v >/dev/null 2>&1 Doesn't work here aleem@thorax:aleem$ moc -v >/dev/null 2>&1 | c

Re: Qt configure patch #2

2002-09-12 Thread John Levon
On Thu, Sep 12, 2002 at 03:51:06PM +0100, Angus Leeming wrote: > Thanks. And can stderr be piped on its own? (moc -v 2> | cat > doesn't work). moc -v >/dev/null 2>&1 but it's not necessary regards john -- "To be fair i do look quite like a monkey ..." - Peter Reid

Re: Qt configure patch #2

2002-09-12 Thread Angus Leeming
On Thursday 12 September 2002 4:20 pm, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > | How do you pipe stderr too? Other than > | moc -v > testmoc 2>&1; cat testmoc | ... ; rm -f testmoc > | of course. > > as one stream? > > mov -v 2>&1 | cat Thanks. And can stderr

Re: Qt configure patch #2

2002-09-12 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | How do you pipe stderr too? Other than | moc -v > testmoc 2>&1; cat testmoc | ... ; rm -f testmoc | of course. as one stream? mov -v 2>&1 | cat -- Lgb

Re: Qt configure patch #2

2002-09-12 Thread José Abílio Oliveira Matos
On Thursday 12 September 2002 15:48, John Levon wrote: > > That's very odd. Whats the moc -v output again ? [15:50][jamatos@rilke:~/lyx/lyx-qt]$moc -v Qt Meta Object Compiler version 19 (Qt 3.0.3) > Does moc -v go to stderr ? [15:50][jamatos@rilke:~/lyx/lyx-qt]$moc -v 2> /dev/null [15:51][jamat

Re: Qt configure patch #2

2002-09-12 Thread John Levon
On Thu, Sep 12, 2002 at 03:50:28PM +0100, José Abílio Oliveira Matos wrote: > > recognised command), then this test will be fine: > > moc -v 2> /dev/null | grep 'Qt' > > Here (with Qt2), echo $? prints '1' to console because the test > > failed. What happens with Qt3? > > [15:45][jamatos@ril

Re: Qt configure patch #2

2002-09-12 Thread José Abílio Oliveira Matos
On Thursday 12 September 2002 15:11, Angus Leeming wrote: > Of course if Qt3's moc -v prints to stdout (because -v is a > recognised command), then this test will be fine: > moc -v 2> /dev/null | grep 'Qt' > Here (with Qt2), echo $? prints '1' to console because the test > failed. What happe

Re: Qt configure patch #2

2002-09-12 Thread Angus Leeming
On Thursday 12 September 2002 3:03 pm, Angus Leeming wrote: > On Thursday 12 September 2002 2:52 pm, John Levon wrote: > > No. The FIXME means what it says. Can you please collaborate > > with Angus to get a working test here. > > You mean that moc -v line should be > > moc -v | \ >

Re: Qt configure patch #2

2002-09-12 Thread Angus Leeming
On Thursday 12 September 2002 2:52 pm, John Levon wrote: > No. The FIXME means what it says. Can you please collaborate > with Angus to get a working test here. You mean that moc -v line should be moc -v | \ sed -e '/Qt [mM]eta/ ! d' -e 's/.*(\(.*\))/\1/' | \

Re: Qt configure patch #2

2002-09-12 Thread John Levon
On Thu, Sep 12, 2002 at 03:44:53PM +0200, Juergen Vigna wrote: > Well I tried and faild :( > > Do you need some config.log files? No. The FIXME means what it says. Can you please collaborate with Angus to get a working test here. Basically, you have a system where binaries called "moc" and "mo

Re: Qt configure patch #2

2002-09-12 Thread Juergen Vigna
Well I tried and faild :( This is what I get when configuring: > checking for XOpenIM... yes > checking for moc2... /usr/bin/moc2 > checking for moc... /usr/lib/qt3/bin/moc > configure: error: FIXME This seems the culpable code in configure: > if test -n "$ac_moc1" -a -n "$ac_moc

Re: Qt configure patch #2

2002-09-11 Thread Lars Gullik Bjønnes
John Levon <[EMAIL PROTECTED]> writes: | this one fixes a couple of silly typos | | please report I have not tested it but it looks ok. I belive this is better than what we currently have, and will be a nicer starting point if more discovery is needed. -- Lgb

Qt configure patch #2

2002-09-11 Thread John Levon
this one fixes a couple of silly typos please report john -- "This *is* Usenet, after all, where virtually every conversation that goes on is fairly ludicrous in the first place." - Godwin's Law FAQ ? config/qt2.bak.m4 Index: autogen.sh ==