🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

1 total messages Started by Eric Marshall Wed, 16 Dec 1992 13:42
complete bug report for "trouble linking Objective C files"
#1556
Author: Eric Marshall
Date: Wed, 16 Dec 1992 13:42
59 lines
2631 bytes
	>    To enable someone to investigate the bug, you should include all
	> these things:
	> 
	>    * The version of GNU CC.  You can get this by running it with the
	>      `-v' option.

	2.3.2

	>      Without this, we won't know whether there is any point in looking
	>      for the bug in the current version of GNU CC.
	> 
	>    * A complete input file that will reproduce the bug.  If the bug is
	>      in the C preprocessor, send a source file and any header files
	>      that it requires.  If the bug is in the compiler proper (`cc1'),
	>      run your source file through the C preprocessor by doing `gcc -E
	>      SOURCEFILE > OUTFILE', then include the contents of OUTFILE in the
	>      bug report.  (When you do this, use the same `-I', `-D' or `-U'
	>      options that you used in actual compilation.)

	m.m contains:

		main(){}

	>    * The command arguments you gave GNU CC or GNU C++ to compile that
	>      example and observe the bug.  For example, did you use `-O'?  To
	>      guarantee you won't omit something important, list all the options.

	-lobjc

	>    * The type of machine you are using, and the operating system name
	>      and version number.

	SPARCStation 1 running SunOS 4.1.1

	>    * The operands you gave to the `configure' command when you installed
	>      the compiler.

	--target=sparc-sun-sunos4.1

	>    * A complete list of any modifications you have made to the compiler
	>      source.  (We don't promise to investigate the bug unless it
	>      happens in an unmodified compiler.  But if you've made
	>      modifications and don't tell us, then you are sending us on a wild
	>      goose chase.)

	None.

	>    * Details of any other deviations from the standard procedure for
	>      installing GNU CC.

	None.

	>    * A description of what behavior you observe that you believe is
	>      incorrect.  For example, "The compiler gets a fatal signal," or,
	>      "The assembler instruction at line 208 in the output is incorrect."
	The compiler emits the following message and does not produce
an a.out file:

	m.m:0: storage size of `_OBJC_SELECTOR_REFERENCES' isn't known
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads