type S_REGULAR does not match previous objects type S_COALESCED
Anton van Oosten
anton.van.oosten at telenet.be
Thu Nov 6 10:15:36 PST 2008
I removed
/usr/local/bin:
c++ powerpc-apple-darwin6.2-g++
cpp powerpc-apple-darwin6.2-gcc
g++ powerpc-apple-darwin6.2-gcc-3.4
g77 powerpc-apple-darwin6.2-gcj
powerpc-apple-darwin6.2-c++
/usr/local/lib:
gcc gcc-lib libstdc++.a libstdc++.la
This fixed the problem.
Thanks for your help!
Anton
Op 3-nov-08, om 00:46 heeft Ryan Schmidt het volgende geschreven:
> On Nov 2, 2008, at 16:15, Anton van Oosten wrote:
>
>> Op 23-okt-08, om 21:20 heeft Ryan Schmidt het volgende geschreven:
>>
>>> On Oct 23, 2008, at 14:13, Anton van Oosten wrote:
>>>
>>>> Op 21-okt-08, om 23:51 heeft Bryan Blackburn het volgende
>>>> geschreven:
>>>>
>>>>> On Tue, Oct 21, 2008 at 11:21:38PM +0200, Anton van Oosten said:
>>>>>
>>>>>> If I remove the overloading gcc, so that the /usr/bin/gcc is
>>>>>> used, I
>>>>>> still get the error.
>>>>>> It looks like I have a really old libstdc++.a in usr/local/lib.
>>>>>> If I move that I get
>>>>> [...]
>>>>>> powerpc-apple-darwin8-g++-4.0.1: /usr/local/lib/libstdc++.a:
>>>>>> No such
>>>>>> file or directory
>>>>>
>>>>> Did you run a 'sudo port clean --work pdflib' prior to trying
>>>>> to install
>>>>> again? If not, that's probably the issue as the configure
>>>>> stage had seen
>>>>> those libraries already so the Makefiles were still referencing
>>>>> them.
>>>>
>>>> Thanks, but this did not solve the issue.
>>>> Could this be an inconsistency between libstdc++.a and gcc?
>>>
>>> It still tries to use /usr/local/lib/libstdc++.a even though that
>>> file no longer exists? I was going to suggest that maybe one of
>>> pdflib's dependencies had already been built with knowledge of
>>> that library, but pdflib doesn't have any dependencies. Hmm.
>>> Maybe we need to see the complete debug output. Run:
>>>
>>> sudo port clean pdflib
>>> sudo port -d install pdflib 2>&1 | tee ~/Desktop/pdflib.txt
>>>
>>> Then send pdflib.txt from your Desktop.
>>
>> Here is the log file.
>
> I didn't see the message "powerpc-apple-darwin8-g++-4.0.1: /usr/
> local/lib/libstdc++.a: No such file or directory" in that output. I
> did see other messages about things in /usr/local though, like:
>
> /usr/bin/ld: warning -L: directory name (/usr/local/gcc/powerpc-
> apple-darwin6.2/libstdc++-v3/src/.libs) does not exist
> /usr/bin/ld: warning -L: directory name (:) does not exist
> /usr/bin/ld: /usr/local/lib/libstdc++.a(ostream-inst.o) section's
> (__TEXT,__eh_frame) type S_REGULAR does not match previous objects
> type S_COALESCED
> /usr/bin/ld: /usr/local/lib/libstdc++.a(ostream-inst.o) section's
> (__TEXT,__eh_frame) type S_REGULAR does not match previous objects
> type S_COALESCED
>
> That "powerpc-apple-darwin6.2" bit is very suspicious; it indicates
> it was built for Mac OS X 10.2 (Mac OS X 10.x == Darwin (x + 4))
> which is very old.
>
> What do you have in /usr/local at this time? Having things in /usr/
> local often causes problems for MacPorts which is why we recommend
> not having anything there when using MacPorts.
>
> What version of Xcode do you have? Get info on /Developer/
> Applications/Xcode.app to find out. If it's less than 2.4.1, please
> update to either 2.4.1 or 2.5. Older versions have been known to
> cause problems and are therefore not supported. Xcode can be
> downloaded from Apple Developer Connection at http://
> connect.apple.com/ .
>
>
>
More information about the macports-users
mailing list