octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #44754] Octave build failure when user-supplie


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44754] Octave build failure when user-supplied CPPFLAGS not understood by Qt moc
Date: Tue, 07 Apr 2015 03:04:14 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Iceweasel/35.0.1

URL:
  <http://savannah.gnu.org/bugs/?44754>

                 Summary: Octave build failure when user-supplied CPPFLAGS not
understood by Qt moc
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 06 Apr 2015 11:04:13 PM EDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: In Progress
             Assigned to: mtmiller
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

This has come up before and was partially fixed (see bug #42839). However,
there is still a build failure when the user supplies valid CPPFLAGS that are
not recognized by Qt's moc tool.

For example, cpp does accept several -W options, these should be accepted as
valid CPPFLAGS but should not be passed to moc. See for example:

https://reproducible.debian.net/rb-pkg/unstable/amd64/octave.html

Excerpt:

( echo '#ifdef HAVE_CONFIG_H'; echo '#include <config.h>'; echo '#endif';
moc-qt4 -DHAVE_CONFIG_H -I. -I..  -Werror=date-time -D_FORTIFY_SOURCE=2  
src/dialog.h ) > src/moc-dialog.cc-t
moc: Invalid argument
Usage: moc [options] <header-file>
...


I have a fix for this, just wanted to log the bug so this can be looked up for
reference later.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44754>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]