Re: matplitlib build problems
On Thu, Sep 18, 2008 at 9:42 AM, Cyril Brulebois wrote: > Kumar Appaiah <[EMAIL PROTECTED]> (18/09/2008): >> Now, this shouldn't really happen, since g++ is supposed to be present >> during the build, right? Also, note that the g++ package is being >> installed on arm and ia64, but not on mips and powerpc. > > At least on ia64 (didn't check the others), looks like broken chroot: > | Toolchain package versions: libc6.1-dev_2.7-6 gcc-4.3_4.3.1-9 g++-4.3_ > binutils_2.18.1~cvs20080103-7 libstdc++6_4.3.1-9 libstdc++6-4.3-dev_ > > Note the x_ packages (as opposed to x_y), they are missing. It appears that the chroot is outdated, and this is being fixed. But the problem stems from the fact that the versions of gcc and g++ on these buildds seem mismatched, and the build system tries to build C++ using gcc, which fails. I have reported the problem upstream as well. Thanks. Kumar -- Kumar Appaiah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: matplitlib build problems
Kumar Appaiah <[EMAIL PROTECTED]> (18/09/2008): > Now, this shouldn't really happen, since g++ is supposed to be present > during the build, right? Also, note that the g++ package is being > installed on arm and ia64, but not on mips and powerpc. At least on ia64 (didn't check the others), looks like broken chroot: | Toolchain package versions: libc6.1-dev_2.7-6 gcc-4.3_4.3.1-9 g++-4.3_ binutils_2.18.1~cvs20080103-7 libstdc++6_4.3.1-9 libstdc++6-4.3-dev_ Note the x_ packages (as opposed to x_y), they are missing. Mraw, KiBi. signature.asc Description: Digital signature
matplitlib build problems
Dear Debian Python, I recently uploaded a backported fix for matplotlib to t-p-u. Unfortunately, it failed to build on four architectures, and the errors can be found here: http://buildd.debian.org/~jeroen/status/package.php?p=matplotlib&suite=testing Now, they all end with the cc1plus missing problem, i.e. "gcc: error trying to exec 'cc1plus': execvp: No such file or directory" Now, this shouldn't really happen, since g++ is supposed to be present during the build, right? Also, note that the g++ package is being installed on arm and ia64, but not on mips and powerpc. I'd appreciate it if someone could please help me understand this problem. Thanks in advance. Kumar -- Kumar Appaiah signature.asc Description: Digital signature
