hi,
when building pike 7.6 from cvs i noticed a few things that could be improved:
after configure a summary of what was detected is shown. but when you just run make as suggested then you never see that summary because it gets buried in the compile outbut following it. hence it would be nice to show that summary after a complete make run as well.
after finding that a lot of libs were missing to build GL and all that i found that after installing them neither make force_autoconfig nor make force_configure not even make clean would do anything to update the findings.
i had to remove the whole build tree to get the new libs detected.
greetings, martin.
In the last episode (May 14), Martin Bhr said:
after finding that a lot of libs were missing to build GL and all that i found that after installing them neither make force_autoconfig nor make force_configure not even make clean would do anything to update the findings.
i had to remove the whole build tree to get the new libs detected.
Removing build/<arch>/config.cache and then running force_configure should work, I think.
fre 2004-05-14 klockan 05.12 skrev Dan Nelson:
In the last episode (May 14), Martin Bhr said:
i had to remove the whole build tree to get the new libs detected.
Removing build/<arch>/config.cache and then running force_configure should work, I think.
Maybe add a target "fore_reconfigure" which removes the config.cace would be an option.
// Mikael
I think a "reconfigure" (without the "force_" part) would be very nice.
/ Marcus Agehall (Scanian)
Previous text:
2004-05-14 09:54: Subject: Re: some observations on the build process
fre 2004-05-14 klockan 05.12 skrev Dan Nelson:
In the last episode (May 14), Martin Bhr said:
i had to remove the whole build tree to get the new libs detected.
Removing build/<arch>/config.cache and then running force_configure should work, I think.
Maybe add a target "fore_reconfigure" which removes the config.cace would be an option.
// Mikael
/ Brevbäraren
Removing build/<arch>/config.cache and then running force_configure should work, I think.
That's even documented in README-CVS. Anyway, I've added a reconfigure target in 7.7 now.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-14 05:13: Subject: Re: some observations on the build process
In the last episode (May 14), Martin Bhr said:
after finding that a lot of libs were missing to build GL and all that i found that after installing them neither make force_autoconfig nor make force_configure not even make clean would do anything to update the findings.
i had to remove the whole build tree to get the new libs detected.
Removing build/<arch>/config.cache and then running force_configure should work, I think.
-- Dan Nelson dnelson@allantgroup.com
/ Brevbäraren
And I hereby name you the hero of the day!
(And silently wish I had cvs access from work so that I could check in the stuff I do during "spare" workhours...)
/ Marcus Agehall (Scanian)
Previous text:
2004-05-18 00:00: Subject: Re: some observations on the build process
Removing build/<arch>/config.cache and then running force_configure should work, I think.
That's even documented in README-CVS. Anyway, I've added a reconfigure target in 7.7 now.
/ Martin Stjernholm, Roxen IS
How do you manage to have KOM but not CVS?
/ Per Hedbor ()
Previous text:
2004-05-18 07:29: Subject: Re: some observations on the build process
And I hereby name you the hero of the day!
(And silently wish I had cvs access from work so that I could check in the stuff I do during "spare" workhours...)
/ Marcus Agehall (Scanian)
I think this answers the question:
Användare: WebKOM%scaniaproxy1.scania.com(unknown)@normandie.lysator.liu.se
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-05-18 08:41: Subject: Re: some observations on the build process
How do you manage to have KOM but not CVS?
/ Per Hedbor ()
Whohoo! ;) And the hypothesis that the amount of appreciation is completely unrelated to the amount of work is thereby proven. That change was really really trivial.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-18 07:29: Subject: Re: some observations on the build process
And I hereby name you the hero of the day!
(And silently wish I had cvs access from work so that I could check in the stuff I do during "spare" workhours...)
/ Marcus Agehall (Scanian)
Naturally it's the amount of work, puzzlement and confusion that is saved others that is the more important factor, yes. :-)
/ Johan Sundström (Achtung Liebe!)
Previous text:
2004-05-18 20:42: Subject: Re: some observations on the build process
Whohoo! ;) And the hypothesis that the amount of appreciation is completely unrelated to the amount of work is thereby proven. That change was really really trivial.
/ Martin Stjernholm, Roxen IS
Saving it as config.txt or something like that would also be nice.
/ Johan Sundström (Achtung Liebe!)
Previous text:
2004-05-14 02:40: Subject: some observations on the build process
hi,
when building pike 7.6 from cvs i noticed a few things that could be improved:
after configure a summary of what was detected is shown. but when you just run make as suggested then you never see that summary because it gets buried in the compile outbut following it. hence it would be nice to show that summary after a complete make run as well.
after finding that a lot of libs were missing to build GL and all that i found that after installing them neither make force_autoconfig nor make force_configure not even make clean would do anything to update the findings.
i had to remove the whole build tree to get the new libs detected.
greetings, martin.
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
Dan Nelson -
Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum -
Marcus Agehall (Scanian) ＠ Pike (-) developers forum
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum
-
Martin Bähr -
Martin Stjernholm, Roxen IS ＠ Pike developers forum
-
Mikael Brandström -
Per Hedbor () ＠ Pike (-) developers forum
-
Peter Bortas (Kein Paket!) ＠ Pike (-) developers forum