On Thu, 2024-07-04 at 15:06 +0200, Jean-Marc Lasgouttes wrote:
> Or just
> ./config.status --recheck
Thank you.
This is nice to know.
> > @Jean-Marc I see now that --no-create --no-recursion are no longer
> > the
> > default. Before when calling ~/SRC_DIR/configure those options were
> > always a
Le 04/07/2024 à 14:01, José Matos a écrit :
On Thu, 2024-07-04 at 13:47 +0200, Pavel Sanda wrote:
I would be concerned if running ./configure does not fix the Qt
version.
Does it fix it in your case?
Pavel
Yes, it works.
Since you do an out source dir build I always need to extract the
previ
On Thu, Jul 04, 2024 at 01:01:34PM +0100, José Matos wrote:
> Since you do an out source dir build I always need to extract the
> previous call from config.log file.
Workaround which I often use:
./autogen.sh
make
(configure is automatically triggered when you lauch make and it take
the paramete
On Thu, 2024-07-04 at 13:47 +0200, Pavel Sanda wrote:
> I would be concerned if running ./configure does not fix the Qt
> version.
> Does it fix it in your case?
>
> Pavel
Yes, it works.
Since you do an out source dir build I always need to extract the
previous call from config.log file.
For th
Le 04/07/2024 à 13:47, Pavel Sanda a écrit :
On Thu, Jul 04, 2024 at 12:29:13PM +0100, José Matos wrote:
There is some mechanism in action because all C++ files were recompiled
when the Qt version changed.
I would be concerned if running ./configure does not fix the Qt version.
Does it fix it
On Thu, Jul 04, 2024 at 12:29:13PM +0100, José Matos wrote:
> There is some mechanism in action because all C++ files were recompiled
> when the Qt version changed.
I would be concerned if running ./configure does not fix the Qt version.
Does it fix it in your case?
Pavel
--
lyx-devel mailing li
On Thu, 2024-07-04 at 12:16 +0200, Pavel Sanda wrote:
> But isn't it reasonable to run configure again when Qt changes?
> And it's not just QT, I think that if you don't rerun autogen
> you won't get correct lyx version when we bump the version.
>
> Pavel
There is some mechanism in action because
On Thu, Jul 04, 2024 at 10:47:00AM +0100, José Matos wrote:
> The Qt version is an old one, most likely the one used last time that
> configure ran.
But isn't it reasonable to run configure again when Qt changes?
And it's not just QT, I think that if you don't rerun autogen
you won't get correct l
Le 04/07/2024 à 11:47, José Matos a écrit :
The Qt version is an old one, most likely the one used last time that
configure ran.
Indeed. Not sure what to do about it. But the Qt version at configure
time may matter, if we did tricks according to it.
JMarc
--
lyx-devel mailing list
lyx-devel
Even before starting I should say that I am just raising this issue but
we do not need to fix it because it applies only to developers and not
to packagers. I have both hats so I know which one to pick and when.
😀️
This is just to share what I learn and I do not think that we need to
care about th
10 matches
Mail list logo
