[Top][All Lists]

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

[Octave-bug-tracker] [bug #43243] Failure building gui - fixable by comm

From: Jordi Gutiérrez Hermoso
Subject: [Octave-bug-tracker] [bug #43243] Failure building gui - fixable by commenting out pointless line of libgnu/stdio.h
Date: Thu, 18 Sep 2014 14:45:47 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 Iceweasel/32.0

Follow-up Comment #5, bug #43243 (project octave):

> Building octave 3.8.3 using gcc 

Do you literally mean gcc, or Apple's frontend to llvm? They behave
quite differently. As I understand it, homebrew cannot use a real gcc,
not without much difficulty, difficulties as the one you're
experiencing. In my experience, Apple deliberately makes it hard to
use a real gcc, but perhaps I am mistaken and too stupid for Apple, or
too stupid to understand your bug report.

> Both bugs are problems created by libgnu/stdio.h.
> They are, however, different problems created by different parts of
> stdio.h, which require different changes to solve.

I am not convinced this is the case. You appear to be experiencing
another symptom of the same problem. The error message says,

 ../libgnu/stdio.h:1034:1: error: conflicting declaration of 'char*
 gets(char*)' with 'C++' linkage 

But as the C++ standard says, uner C linkage the namespace is to be
ignored for the resulting symbol name. There would be no conflicting
declaration of the gets symbol if it were under the gnulib namespace
as it's supposed to be.

Please confirm that despite applying the fix from bug #43171, you
still observe trouble on Mac OS X.

At any rate, your suggested fix obviously cannot be implemented as-is,
as the first line of the file you're atttempting to patch reads,


If gnulib needs to be patched, this patch must to be applied deeper to
the original gnulib sources, not the auto-generated output.

> This is becoming ridiculous.

You may find a better audience for your frustration in the Octave
maintainers' list <address@hidden>. Let's keep the discussion
here pertinent to the problem at hand.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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