[BUILD:fail] cdrdao :: latest repository code (Bug #228)

Added by Jeremy Sutherland almost 4 years ago. Updated almost 4 years ago.

Status:Feedback Start date:09/15/2011
Priority:Low Due date:
Assignee:- % Done:


Target version:-


Running make with 3 jobs failed. Attempt to run with a single job? [y] make: *** [all] Error 2
make1: Leaving directory `/usr/src/cdrdao-sfcvs'

/usr/bin/make all-recursive
make1: Entering directory `/usr/src/cdrdao-sfcvs'
Making all in trackdb
make2: Entering directory `/usr/src/cdrdao-sfcvs/trackdb'
/usr/bin/antlr -k 3 -CC -w2 -fl TocLexer.dlg -ft TocParserTokens.h ./TocParser.g
ANTLR Parser Generator Version 2.7.7 (20110907) 1989-2005
warning: grammar file must be last; ignoring other arguments...
error: file 3 not found
/usr/bin/dlg -C2 -CC -cl TocLexerBase TocLexer.dlg
dlg Version 1.33MR33 1989-2001
dlg: Warning: Can't read file TocLexer.dlg.
i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/pccts -march=i686 -pipe -DPIC -fPIC -O3 -MT TocParser.o -MD -MP -MF .deps/TocParser.Tpo -c -o TocParser.o TocParser.cpp
i686-pc-linux-gnu-g++: error: TocParser.cpp: No such file or directory
i686-pc-linux-gnu-g++: fatal error: no input files
compilation terminated.
make2: * [TocParser.o] Error 1
make2: Leaving directory `/usr/src/cdrdao-sfcvs/trackdb'
make1: Leaving directory `/usr/src/cdrdao-sfcvs'
[all-recursive] Error 1
make: *
* [all] Error 2
! Problem Detected !

Issue hierarchy

Bug #141: [BUILD] Failure Master BugNew

Bug #229: [SCM build failures] these are for record onlyFeedback

Bug #228: [BUILD:fail] cdrdao :: latest repository codeFeedback


Updated by Bor Kraljič almost 4 years ago

In my opinion we CAN'T provide that SCM source will always build.

We should just put a warning that for SCM versions that code is alive and it could break without any waring and WE (as distribution) can't do much about it. We have more than enough work on our hands with testing & QA for spells with "static" sources.

We now have function for choosing branch of spell in PREPARE and such warning can be added very easily.

Updated by Jeremy Sutherland almost 4 years ago

I was not even considering having scm sources always building...

can we make a log or list of scm installed packages seperate from the master installed list?
and have a big fat warning that the user is pretty much choosing to ignore supportable options?

Updated by Jeremy Sutherland almost 4 years ago

  • Priority changed from Normal to Low
  • % Done changed from 0 to 100
  • Status changed from New to Feedback

Also available in: Atom PDF