pkgsrc-Bugs archive

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

pkg/43066: audio/csound5 transform/wrapper problem ?? (NetBSD 4.0/i386)

>Number:         43066
>Category:       pkg
>Synopsis:       audio/csound5   transform/wrapper problem ??   (NetBSD 
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 28 08:05:00 +0000 2010
>Originator:     Robert Elz
>Release:        NetBSD 4.0 / i386   (pkgsrc current 2010-03-28)
        Prince of Songkla University
System: NetBSD 4.0_STABLE NetBSD 4.0_STABLE 
(JADE-1.696-20080517) #9: Fri May 23 18:55:13 ICT 2008 i386
Architecture: i386
Machine: i386
        audio/csound5 doesn't build ....   OK, that's not much of
        a description...  how about it *really* doesn't build...

        I use pkg_comp with libkver and NetBSD 4.0 release sets
        installed (X11_TYPE=modular instead of the x* sets, but
        that's irrelevant here I think).

        Attempting to build audio/csound5 (csound5-5.01nb6) fails,
        the previous version (...nb5) worked.

        The build shows ...

===> Configuring for csound5-5.01nb6
=> Checking for portability problems in extracted files
===> Building for csound5-5.01nb6
echo USETOOLS=no\ DL_CFLAGS= [remainder of LONG line deleted]
cd /pkg_comp/obj/pkgsrc/audio/csound5/4x/Csound5.01 && /usr/bin/env USETOOLS=no 
DL_CFLAGS= [remainder of similar LONG line with less \'s deleted]
scons: Reading SConscript files ...

C S O U N D 5

SCons build file for Csound 5:
API library, plugin opcodes, utilities, and front ends.

By Michael Gogins <gogins at pipeline dot com>

For custom options, run 'scons -h'.
For default options, run 'scons -H'.
If headers or libraries are not found, edit ''.
For Linux, run in the standard shell
    with standard Python and just run 'scons'.
For MinGW, run in the MSys shell
    and use WIN32 Python to run scons.

/usr/pkg/lib/scons-1.1.0/SCons/Platform/ DeprecationWarning: The 
popen2 module is deprecated.  Use the subprocess module.
  import popen2
/usr/pkg/lib/scons-1.1.0/SCons/Tool/ DeprecationWarning: the md5 
module is deprecated; use hashlib instead
  import md5
System platform is 'netbsd4'.
Build platform is 'netbsd'.
SCons tools on this platform:  ['default', 'gnulink', 'gcc', 'g++', 'g77', 
'gas', 'ar', 'CVS', 'filesystem', 'javac', 'lex', 'm4', 'RCS', 'rpcgen', 
'swig', 'tar', 'yacc', 'zip']

CONFIGURATION DECISION: Using single-precision floating point for audio samples.
Checking for C header file stdio.h... no
 *** Failed to compile a simple test program. The compiler is
 *** possibly not set up correctly, or is used with invalid flags.
 *** Check config.log to find out more about the error.
*** Error code 255

make: stopped in /usr/pkgsrc/audio/csound5
*** Error code 1


        The file it is trying to compile is

                #include <stdio.h>

        (not indented of course) - that's the whole thing...

        It looks as if the "or is used with invalid flags" guess
        as to the cause of the failure is spot on though, when
        this is compiled, in addition to a whole bunch of reasonable
        looking compiler options, the compiler is passed ...

                - W a l l

        (5 options it seems, each one character long).

        (The very long lines I truncated in the build log above had no
        mention of "-Wall" or anything similar, nothing there looked odd
        or I would have left them intact.)

        I've been looking and I just can't see where this happens.
        I can see where "-Wall" is added to CFLAGS, and I can see
        that when .wrapper/bin/gcc is called, it is - W a l l already,
        so it is not something that that wrapper script is doing,
        it is happening earlier than that.

        But where??   All this stuff is black magic to me.

        I have however seem a similar thing before with
        "-pthread" also being passed as '- p t h r e a d" but
        when I've seen that, it seems to mostly just generate warnings
        and be ignored (it looks ugly, but seems harmless).

        Does anyone have any idea what is making this mess?


Home | Main Index | Thread Index | Old Index