On 3/19/13 1:20 AM, Hinrich Schuetze wrote:
> Dear All,
> 
> Thanks for the quick replay. I'm resending my message with the (hopefully) 
> correct error message. I also attach the error message I got and the 
> config.log.
> 
> Thanks - Hinrich                                        
> 

We prefer _not_ getting attachments, because they require the extra
effort of pasting the text back into the message for replies--we're
heavily text-oriented.

Since configuration finished and the build started, the config.log isn't
terribly helpful, apart from indicating that your compiler version is a
new one from Apple, and that the "No recognized Xcode CLI" message at
the end of your build log may indicate a change that we have to account for.


"ld: archive has no table of contents for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make[2]: *** [dpkg-deb] Error 1:"

The above isn't that actually that useful for debugging purposes, since
all we know from that is you had an error sometime when building
dpkg-deb, but we don't know _what_ was having problems.

The best practice is to provide the _full_ line containing the compiler
command that was being run before the error messages started to occur,
and at least the _first_ few lines of error output, i.e. start at the
beginning rather than working back from the end.

You can send me a transcript from your terminal output off-list.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Fink-beginners mailing list
Fink-beginners@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.beginners
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to