Ticket #19871 (closed defect: wontfix)
gdb @ 6.8 fails to build everything
|Reported by:||dweber@…||Owned by:||dweber@…|
|Keywords:||Cc:||f.baart@…, karoly@…, alexoedelman@…, captsolo@…, larry.velazquez@…|
I put this Portfile together in the hope that the build and install would be smooth. It's not. It may be that the automatic detection of the target architecture is wrong. The main concern is this:
checking build system type... i386-apple-darwin9.7.0 checking host system type... i386-apple-darwin9.7.0 checking target system type... i386-apple-darwin9.7.0 checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking whether we are using the GNU C++ compiler... yes checking whether /usr/bin/g++-4.0 accepts -g... yes checking for gnatbind... no checking for gnatmake... no checking whether compiler driver understands Ada... no checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2 *** This configuration is not supported in the following subdirectories: bfd opcodes gdb sim (Any other directories should still work fine.)
So what is happening is the build and install is working, but only partially. It would be preferable that the build fails at this point, but it does not!
It looks like the main thing to get right is the target platform identifier. I looked into it briefly, but it's not resolved yet. I would hope that if the target platform is identified correctly (and fully supported by gdb 6.8), the port will be functional.
If anyone has the motivation and patience to look into it further (as I will when I get time), the first thing to do is to run port in debug mode, i.e.:
sudo port -d destroot gdb
This will provide a lot of information on what port is doing. The destroot target does the configure and build, then runs make install with a custom DESTDIR. MacPorts uses that DESTDIR, called destroot, as a way to parse the files in the port, install the files into /opt/local/var/macports/software/gdb/ and then activate the port with hard links in /opt/local to the files in the software/gdb installation.
The destroot path for this port is
The pitiful truth is that the only files currently installed there are:
.../destroot/ .../destroot//opt .../destroot//opt/local .../destroot//opt/local/lib .../destroot//opt/local/lib/libiberty.a .../destroot//opt/local/share .../destroot//opt/local/share/info .../destroot//opt/local/share/info/configure.info .../destroot//opt/local/share/info/standards.info
- Status changed from new to assigned
- Owner changed from dweber to dweber@…
- Status changed from assigned to closed
- Resolution set to wontfix