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

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

[Octave-bug-tracker] [bug #38518] make dist produces a bad source packag


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #38518] make dist produces a bad source package when Qt not present
Date: Thu, 14 Mar 2013 20:44:42 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20100101 Firefox/17.0

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

                 Summary: make dist produces a bad source package when Qt not
present
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Thu 14 Mar 2013 04:44:40 PM EDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

When Qt is not found, or if --disable-gui is given, the dist target works but
produces an octave source distribution without the libgui subdirectory. Trying
to build that source package fails because configure requires
libgui/Makefile.in.

The easy solution would be to disable make dist like we do when docs are
disabled. But that is mainly because we definitely want the documentation to
be in the source distribution, right?

It should be possible, and would be nice, to be able to run make dist without
Qt, assuming there are no EXTRA_DIST files under libgui that are generated
using any of the Qt tools. I think that's the case but I'm not sure.

Automake definitely allows conditional SUBDIRS that will be entered for dist
and distclean targets but not for other make targets.

I discovered this on a Hydra build, where Octave is being built without Qt (so
far) and make dist is used to produce a source package that is then built on
i686-linux and x86_64-linux. See for example
http://hydra.nixos.org/build/4397119/log/tail-reload




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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