On quarta-feira, 11 de dezembro de 2013 03:04:22, Jan Kundrát wrote: > Hi, I tried compiling Qt5 from git (release branch) again tonight on my > Linux machine (64bit Gentoo). The last time I did it was with Qt 5.1, so I > had plenty of old stuff around. > > TL;DR version -- despite the fact that I restored git modules as documented > on the wiki, I still got hard to debug errors and wasted hours of time > (both human and CPU) on this. A couple of questions/suggestions: > > - If a submodule is known [1] to be broken, why is is linked to from the > release branch of the top-level repo?
qtjsondb should be removed, indeed. We removed qtphonon.
Note that qt5.git contains modules that aren't part of the release, though.
> - Why is `make first` the default target instead of `make all`?
Because, as its name says, "first" is the first target.
But it doesn't make a difference, does it? Both targets should do the same.
> - How comes that running `make` does not report an error at the very end of
> the process?
It does. Maybe your make program is broken?
[snip]
> But if one looks closely enough, the process surely failed:
>
> $ echo $?
> 2
No, looks like it isn't. It reported an error.
> ...except that any indication about the failure is now five minutes deep in
> the scrollback (this is a SandyBridge i5 with 16 GB of RAM). There is *no*
> user-friendly error message which might possibly tell me that there was an
> error. I have to go actively looking for it via the exit status. This is
> not sane.
http://savannah.gnu.org/projects/make/
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
