RE: How to fix "‘get_current_dir_name’ was not declared in this scope" ?

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

 



Hi Jonathan

Thanks for your answer. I just needed to know where to look.

Best regards

David

> -----Original Message-----
> From: Jonathan Wakely [mailto:jwakely.gcc@xxxxxxxxx]
> Sent: 14 November 2013 12:07
> To: David Aldrich
> Cc: gcc-help@xxxxxxxxxxx
> Subject: Re: How to fix "‘get_current_dir_name’ was not declared in this scope"
> ?
> 
> On 14 November 2013 11:57, David Aldrich wrote:
> > Hi
> >
> > Our application builds fine on Ubuntu 12.04 LTS, using gcc 4.6.3.
> >
> > However, when I attempt to build on Fedora 19, which uses gcc 4.8.2 I see:
> >
> > g++ -I../../Kernel -Wall -m64 -O3 -c -o FileSystem.o FileSystem.cpp
> > FileSystem.cpp: In static member function ‘static std::string
> FileSystem::currentDir()’:
> > FileSystem.cpp:108:34: error: ‘get_current_dir_name’ was not declared
> > in this scope p = get_current_dir_name();
> >
> > Please will someone explain how to fix this?
> 
> Declare the function, of course!
> 
> It's declared in <unistd.h> so make sure you include that.
> 
> If you use that function without including <unistd.h> then your code was always
> broken, but you got away with it in the past.  See the header dependency
> changes section of http://gcc.gnu.org/gcc-4.7/porting_to.html for more details.
> 
> 
>  Click
> https://www.mailcontrol.com/sr/ue91J159rp!GX2PQPOmvUi5k6UwC8217nDq3J
> XqYyXHMltAxjHyTnnsqMfZP2+Q66JsWorzTs4aU8yB5sLY89Q==  to report this
> email as spam.





[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux