Script to build avr-gcc-4.2.2 on Linux installs sources

Go To Last Post
6 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I ran out of space on my hardrive and went looking for the biggest offenders (debian linux). It turns out that the latest version of the scripts install the build and source directory along with the binaries and support files. Removing them frees up about 540M.

Markus

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

All the scripts keeps the sources , and they write a message at completion.
telling that you might want to clean up the build directories.

Maybe jörg or Eric could tell if the sources are used if debugging , and one "jumps" into avrlibc code.
Or if it is embedded into the dwarf-info. , i'd expect the first.

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, the debugging symbols for the library code are included into
the object files, and if you keep the library sources around, you
can step through the library code. (Eric has to avr-strip -g
all his files before shipping WinAVR, in order to remove the
debugging symbols since they don't make sense if you don't also
have the source code around.)

I think it's fair to ask the user to remove the compilation trees
rather than always cleaning everything up. After all, it's quite
possible someone also wants to make a stab at fixing a bug, or just
wants to browse around through all the tools' source code.

Perhaps you could offer the equivalent of a "make clean" step that
could be run by the user manually afterwards.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

dl8dtl wrote:

Perhaps you could offer the equivalent of a "make clean" step that
could be run by the user manually afterwards.

Sure ... will include one in the next update

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I ran the script in the background so I didn't see the message. I don't recall the older versions of the script (4.1.1) to install the sources. That's why it was such a surprise when I found them (a few weeks after installation).

Sorry about the noise.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

One could just keep the avrlibc sources , those are prob the only ones that have interest in an AVR environment.

The "Badboy" is prob the full GCC package

/Bingo