New To Mac-Forums?

Welcome to our community! Join the discussion today by registering your FREE account. If you have any problems with the registration process, please contact us!

Get your questions answered by community gurus Advice and insight from world-class Apple enthusiasts Exclusive access to members-only contests, giveaways and deals

Join today!

Start a Discussion

Mac-Forums Brief

Subscribe to Mac-Forums Brief to receive special offers from Mac-Forums partners and sponsors

Join the conversation RSS
OS X - Development and Darwin Discussion and questions about development for Mac OS X.

building GCC without debuging information

Post Reply New Thread Subscribe

Thread Tools

Member Since: Oct 20, 2010
Posts: 1
mesalas is on a distinguished road

mesalas is offline
I have been using gfortran from binary distributions to compile small scientific programs for some time now. Not long ago I decided to try and compile gfortran myself in order to get a better understanding of the gcc compilers and to get more "streamlined" gcc setup. Before I had several fortran compilers that was configured for different things and but what I want is one compiler configured for all my needs, so I figured that this could be done by compiling it myself.

In order to be able to be able to remove the compiler and more importantly install it easily again I use fink to compile the code and install it as .deb packages.
Now this worked out relatively well but I have one problem that I cant figure out:

When I compile my fortran77 code with the -g option in order to debug it it seems like some information about libgfortran in the build directory is added, this causes errors in the gnu debugger as the build directory is long gone.

when I run the program in GDB I get 200 lines like this:

warning: `/sw64/src/': can't open to read symbols: No such file or directory.
where "transpose_generic.o" can be exchanged with any of the ~200 libs, and where : /sw64/src/ was the dir gcc was build in.

I can't figure out if this affects the GDB or not.
Furthermore, I have encountered this problem before with all of the binary distributions of gfortran I have used before.

I guess my questions goes as following: How come gfortran points to some files that were present in the build dir but never installed, and how can this debugging information be removed?

My gcc was configured with the following options:
./configure --enable-languages=fortran --prefix=/sw64

I hope I can get some help in order to understand this problem.

QUOTE Thanks

Post Reply New Thread Subscribe

« IE for mac | Compile source code to DMG? »
Thread Tools

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off
Forum Jump

Similar Threads
Thread Starter
Last Post
Mac-Forums Switchers FAQ and Information eric Switcher Hangout 57 03-18-2010 08:25 AM
I cannot properly install gcc and gfortran gcordoba OS X - Development and Darwin 3 02-18-2010 04:28 PM
Recording information problem with iTunes 8.0.1 schwine Music, Audio, and Podcasting 0 11-25-2008 11:56 AM
gcc compiling jdgti OS X - Development and Darwin 5 09-20-2006 04:08 AM
How to install GCC version 4.xx???? Philipina OS X - Development and Darwin 1 04-14-2006 10:25 AM

All times are GMT -4. The time now is 06:07 PM.

Powered by vBulletin
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.

Welcome to

Create your username to jump into the discussion!

New members like you have made this community the ultimate source for your Mac since 2003!

(4 digit year)

Already a member?