[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51680] some LDFLAGS variables may be a space
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #51680] some LDFLAGS variables may be a space instead of empty string, throwing off other tests |
Date: |
Mon, 7 Aug 2017 00:12:20 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 |
URL:
<http://savannah.gnu.org/bugs/?51680>
Summary: some LDFLAGS variables may be a space instead of
empty string, throwing off other tests
Project: GNU Octave
Submitted by: mtmiller
Submitted on: Sun 06 Aug 2017 09:12:19 PM PDT
Category: Configuration and Build System
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Installation Failure
Status: In Progress
Assigned to: mtmiller
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.2.1
Operating System: GNU/Linux
_______________________________________________________
Details:
On Ubuntu 14.04, I find that some pkg-config commands may return what appears
to be an empty string, but is actually a space character. There are other
tests in configure and possibly elsewhere in the code base that test for empty
strings, for example
if test -n "$QT_LDFLAGS"; then
...
which is breaking the build configuration further down the line, for example
the set of library dependencies that are encoded in mkoctfile.
I'm working on a workaround for this that I can apply as a patch to the 4.2.1
release, and will post again when I get something working.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51680>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #51680] some LDFLAGS variables may be a space instead of empty string, throwing off other tests,
Mike Miller <=