[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#812681: [help] Bug#812681: mira: FTBFS with flex >= 2.6]

Hi Jakub,

On Tue, Jan 26, 2016 at 05:12:26PM +0100, Jakub Wilk wrote:
> * Andreas Tille <andreas@an3as.eu>, 2016-01-25, 22:06:
> >sorry, I have no idea about fley and need help to fix this problem.
> I think it's a bit premature to ask debian-mentors for help when your RC bug
> is 7 minutes old. What you could do instead is:
> * Wait a bit longer. Perhaps one of the numerous co-maintainers knows how to
> fix the bug, but they all busy or asleep at the moment?

The thing is that I know my co-maintainers well enough regarding their
dense schedule (and knowledge about things like flex) that waiting
another 24 hours would not have changed anything.

> * Ask on the team's mailing list.

Receives the message via the bug e-mail anyway.

> * Ask upstream.

Yes, I might pick this option next time.
> (Not necessarily in that order.)
> >exp_flexer.cc:766:9: error: no match for 'operator=' (operand types are 'std::istream {aka std::basic_istream<char>}' and 'std::istream* {aka std::basic_istream<char>*}')
> >   yyin = & std::cin;
> >        ^
> The problem is that exp_flexer.cc was not regenerated from the corresponding
> *.ll file at build time. Instead, the file included in the .orig.tar (which
> was generated by an older flex) was used.
> Removing the pre-generated flex output fixed it for me:
> find -name '*.ll' | sed -e 's/[.]ll$/.cc/' | xargs rm

Thanks a lot for your patience and help



Reply to: