Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"error: identifier "printf" is undefined" during make

Open
#18 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
build-system

Research direction

Start by reviewing System.cmake.src and src/ocustorage/transfer_routines.cu around line 144, then reproduce the failure with cmake and make on the stated Ubuntu and OpenCurrent v1.1.0 setup. Done means the build proceeds past these compilation errors without the undefined printf diagnostics.

Written by the indexing model from the issue text.

Description

auto-migrated Priority-Medium Type-Defect
What steps will reproduce the problem?
1. Followed instructions in System.cmake.src to cmake. 
   Had to add the following lines:
    SET(NetCDF_INCLUDE_DIR "/usr/include/")
    SET(NetCDF_LIBRARY "/usr/lib/libnetcdf.so")

2. Ran make. Got to 8% and were then interrupted by: 
<path>/opencurrent-1.1.0/src/ocustorage/transfer_routines.cu(144): error: 
identifier "printf" is undefined
<^^Repeated 10 more times for different lines in the same file^^>
11 errors detected in the compilation of 
"/tmp/tmpxft_00002674_00000000-4_transfer_routines.cpp1.ii".


What version of the product are you using? On what operating system?
OpenCurrent v1.1.0 release (tar.gz file)
GeForce GTX 580 (compute capability 2.0, 1536 Mb memory).
Ubuntu 11.04 x86_64

Please provide any additional information below.


Original issue reported on code.google.com by eskil.au...@gmail.com on 5 Jul 2011 at 1:13

Dominant language
Cuda
Stars
6
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ExpectationMax/opencurrent

All issues in ExpectationMax/opencurrent

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.