Re: sigc++ configure.in

2000-06-23 Thread Andreas Vox
"Eric J. Schwertfeger" wrote: > On Wed, 21 Jun 2000, Andre Poenitz wrote: > > > The only difference between "./configure" and ". ./configure" > > is that the latter works even if ./configure has no executable permissions > > set. So maybe it's a permissicon problem, it certainly has nothing to

Re: sigc++ configure.in

2000-06-22 Thread Eric J. Schwertfeger
On Wed, 21 Jun 2000, Andre Poenitz wrote: > The only difference between "./configure" and ". ./configure" > is that the latter works even if ./configure has no executable permissions > set. So maybe it's a permissicon problem, it certainly has nothing to do > with having . in $PATH or your choi

Re: sigc++ configure.in

2000-06-21 Thread Stephan Witt
Andre Poenitz wrote: > > > I had the same problem under Solaris 2.6. The problem is only > > bash looks in the current directory, sh and ksh don't. The lines in > > configure.in > > should be changed to > > . ./configure > > (worked for me) > > Well, I believe it worked for you, but I do not bel

Re: sigc++ configure.in

2000-06-21 Thread Andre Poenitz
> I had the same problem under Solaris 2.6. The problem is only > bash looks in the current directory, sh and ksh don't. The lines in > configure.in > should be changed to > . ./configure > (worked for me) Well, I believe it worked for you, but I do not believe that there is any sh/ksh/whatever t

Re: sigc++ configure.in

2000-06-21 Thread Andreas Vox
Hi there! André Pönitz wrote: >> Anyway that is not the problem, the problem is the configure that is >> built in the sigc++ directory builds a file about a third of the way >> in called ac_threads.sh, it then wants to RUN this file. It does this with: >> >> . ac_threads.sh >> >> This will O

Re: sigc++ configure.in

2000-06-13 Thread Andre Poenitz
> A bit of a pain but not much of one. Even less of a pain if you read INSTALL and follow the instructions under "Note for CVS checkouts" that are telling you to run ./autogen.sh ;-) > Anyway that is not the problem, the problem is the configure that is > built in the sigc++ directory build

sigc++ configure.in

2000-06-13 Thread Michael Frankowski
Good Morning, I don't know if you have caught this bug yet, but in case you haven't. I checked out the CVS copy this morning, built up all the the configure.in to configure files, I would note that there are four and you have to know to go and find them all. A bit of a pain but not much of