Opened 11 years ago

Closed 9 years ago

Last modified 9 years ago

#7436 closed defect (duplicate)

frobby optional spkg doesn't build on a lot of machines

Reported by: was Owned by: tbd
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: packages: optional Keywords:
Cc: Merged in:
Authors: Reviewers: Benjamin Jones
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


On many Linux boxes, building the frobby-0.7.6 spkg fails as follows:

gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) 
mkdir -p bin/release/ 
g++ -Wall -ansi -pedantic -Wextra -Wno-uninitialized -Wno-unused-parameter -Werror -isystem /tmp/wstein/farm/sage-4.2.1.alpha0/loc
al/include -O3 -c src/main.cpp -o bin/release/main.o
src/main.cpp: In function ‘int main(int, const char**)’:
src/main.cpp:30: error: ‘srand’ was not declared in this scope
make: *** [bin/release/main.o] Error 1
Error building Frobby.

real    0m2.271s
user    0m0.320s
sys     0m0.410s
sage: An error occurred while installing frobby-0.7.6

I ran the command "sage -i frobby-0.7.6" on the build farm and it fails on:

  • debian32/64
  • fedora32/64
  • mandriva32/64
  • opensuse32/64
  • ubuntu32/64

It works on centos (=REDHAT). It works on sage.math. Basically it works with gcc <= 4.2 and fails with newer GCC's.

Change History (9)

comment:1 Changed 11 years ago by drkirkby

I get the same problem on Solaris, with gcc 4.4.2


comment:2 Changed 11 years ago by drkirkby

Also fail on Solaris 10 (SPARC) with gcc 4.4.2

comment:3 Changed 11 years ago by drkirkby

Oops, I appear to have put the same comment twice!

comment:4 Changed 9 years ago by benjaminfjones

  • Milestone changed from sage-5.1 to sage-duplicate/invalid/wontfix
  • Report Upstream set to N/A

comment:5 Changed 9 years ago by benjaminfjones

  • Status changed from new to needs_review

comment:6 Changed 9 years ago by benjaminfjones

  • Status changed from needs_review to positive_review

comment:7 Changed 9 years ago by jdemeyer

  • Resolution set to duplicate
  • Reviewers set to Benjamin Jones
  • Status changed from positive_review to closed

comment:8 Changed 9 years ago by drkirkby

As a matter of interest, what was the reason for not fixing it? I thought optional packages were supposed to build on all supported machines. So the only logical things to me were to either

1) Fix it 2) Make it experimental and not optional.

It this bug report a duplicate, as the resolution is set to?

I appreciate the fact this has remained like this for 3 years probably means nobody cares too much, but the concept of closing a ticket without fixing an issue seems wrong to me.


comment:9 Changed 9 years ago by benjaminfjones

This was closed because #13007 does fix the problem on the platforms in the ticket description. I did not test the new spkg there on solaris though.

Note: See TracTickets for help on using tickets.