This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/11878] 'glibc' build documentation is apparently incomplete


http://sourceware.org/bugzilla/show_bug.cgi?id=11878

Sergei Steshenko <sergstesh at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #3 from Sergei Steshenko <sergstesh at yahoo dot com> 2012-02-18 14:00:51 UTC ---
"
The bug you linked to, bug 11875, looks like it was a genuine configure bug
(rather than a doc bug) which was fixed by:

commit 84b9230c404aed4fd3a7bb3d045ca367043dde8c
" - how interesting. 

I.e. the build mechanism _does_ have bugs from time to time. But you, guys,
unlike in other FOSS project, do not accept bug reports against build mechanism
?

How outlandish. How discriminatory.


"
But identifying such a deficiency from a build
failure requires that the person seeing the failure, with access to the system
on which it appears, debugs the failure so they can understand the underlying
cause.  That's what's meant by not filing build failures in Bugzilla: a build
failure by itself does not give enough information to be a useful problem
report
" - sorry, I don't buy it.

I have filed "tons" of "'make' fails even though 'configure' is OK" bug reports
against various FOSS project, and in the vast majority of cases the bugs are
fixed.

Nobody had access to my computer; in most cases 'config.log' was sufficient for
the developers to fix the problems.

It looks like you guys at RedHat lack elementary debugging skills and
methodology.

In order to debug such failures remotely you need to tell the submitter which
'print' statements to insert into which files, and/or which debug tools to use
(for example, http://bashdb.sourceforge.net/remake/ helps quite a lot to debug
Makefiles).

So, guys, just don't try to sell us, the rest of the world, your discriminatory
attitude towards your own bugs in your own build mechanism.

It is against the very foundation of FOSS movements, whose one of the strongest
sale points is: (see, for example,
http://www.linuxplanet.com/linuxplanet/reports/7082/1/ ) :
"
By contrast, for most open source supporters, the licensing is a way to improve
the quality of software. The open source argument is that, because the source
code is available, bugs will be more easily discovered -- or, as Eric S.
Raymond put it, "with enough eyes, all bugs are shallow."
".

Thank you very much again for defeating the very purpose of FOSS by not
accepting bug reports (against build mechanism) and stonewalling any effort to
change the situation.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]