Bug 150879 - gphoto2 does nov compile with gcc-4.0.0-0.32
gphoto2 does nov compile with gcc-4.0.0-0.32
Product: Fedora
Classification: Fedora
Component: gphoto2 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2005-03-11 11:19 EST by Sammy
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 2.1.5-5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-11 18:06:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sammy 2005-03-11 11:19:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux; X11; en_US) KHTML/3.3.2 (like Gecko)

Description of problem:
I am trying to rebuild this from the source rpm and I get the error:

gphoto2-port.c: In function 'gp_port_read':
gphoto2-port.c:411: error: syntax error before '(' token
gphoto2-port.c:411: error: '__nbytes_val' undeclared (first use in this function)
gphoto2-port.c:411: error: (Each undeclared identifier is reported only once
gphoto2-port.c:411: error: for each function it appears in.)
gphoto2-port.c:411: warning: passing argument 1 of 'read' makes integer from pointer without a cast
gphoto2-port.c: At top level:
gphoto2-port.c:411: error: syntax error before ')' token
gphoto2-port.c:417: error: syntax error before string constant
gphoto2-port.c:417: warning: type defaults to 'int' in declaration of 'gp_log_data'
gphoto2-port.c:417: error: conflicting types for 'gp_log_data'

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. try building gphoto2 from source rpm
2. look at error

Additional info:
Comment 1 Sammy 2005-03-11 15:03:32 EST
Everything compiles fine if you don't use FORTIFY_SOURCE option! 
Comment 2 Tim Waugh 2005-03-11 18:06:45 EST
Fixed in 2.1.5-5.  Thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.