HDTenEightyP/NetNews huggingface dataset:
From: jclark@sdcc3.ucsd.edu (John Clark)
Newsgroups: gnu.gcc.help
Subject: Re: installing gcc linker (ld)
Date: 23 Jul 92 00:18:43 GMT
Distribution: gnu
Organization: University of California, San Diego

In article <1992Jul22.170054.23775@utkux1.utk.edu> rich@laser1.engr.utk.edu (Stevie-weave) writes:
+I get the same errors. Therefore, I built with the above option, installed
+the gnu cross loader found on sprite.berkely.edu (I couldn't figure out
+how to build ld out of binutils as a cross-loader) and it now works. The
+only thing that bothers me now is that the loader complains about the
+.so revision of libc.so..... when I load with -d -r options (not resolving
+globals, etc) because the VxWorks stuff resolves at load time. Does anybody
+know why?

I assume the 'ld' you got from the sprite machine was an executable,
then the revision error means that that executable was created on a
machine which has a different verion of the dynamically linked
libc.so.o than your current execution machine.

Sometimes the revision error is harmless, but then may not be so. I
would suggest figuring out why you couldn't build a cross-ld from
the binutils package.

-- 

John Clark
jclark@ucsd.edu
Newsgroups: gnu.gcc.help
Subject: Re: source for gcc gc+
From: marcello@deis20.cineca.it (Marcello Dalpasso)
Date: 29 Jul 92 14:38:55 +0100
Distribution: world
Organization: *********************************************************

The Official ftp distributor for any GNU product is

	prep.ai.mit.edu

in /pub/gnu

I think it's better mentioning that gcc and g++ actually comes in a unique package,
namely gcc-2.2.2.tar.Z, and the g++ package to be found in /pub/gnu is an out-of-date
version.

To use g++, you will also need libg++, a separate package to be installed after
gcc/g++ was successfully installed.

Hoping this can help you.

-- 
	Marcello Dalpasso (e-mail: marcello@deis16.cineca.it)
	D.E.I.S. - Department of Electronics and Computer Science	
	Viale Risorgimento 2, I-40136 Bologna, Italy			
	Phone: +39-51-644-3015 (fax: +39-51-644-3073)
From: poling@dayton.saic.com (Steven Poling)
Newsgroups: gnu.gcc.help
Subject: gcc 2.2.2 & ISC 3.0 v 3.2 Install
Date: 23 Jul 92 17:11:16 EDT
Organization: Science Applications Intl. Corp., Dayton, Ohio

	I am trying to install gcc 2.2.2 on a ISC 3.0 v 3.2 system and not
having much luck.  Everything compiles fine until I get to the execution
of the program called:  enquire, this program does some numeric bounds checking
and reports the results....  after I get two sets of error messages the
compile stops with the line:

	mv tmp-float.h float.h

	I used:  configure i386-isc to configure the compiler and started the
make with: make LANGUAGES=c

	Any help would be greatly appreciated.

	Steve 
	poling@dayton.saic.com


-- 
DISCLAIMER: SAIC is not responsible for the content of this message period.
_____________________________________________________________________________
               ____ ____    ___
Steven Poling /___ /___/ / /     Science Applications International Corporation
             ____//   / / /__                 Dayton, Ohio
-----------------------------------------------------------------------------
Internet: poling@dayton.saic.com     DECNET: dayvax::poling 
    uucp: dayvb!poling

Newsgroups: gnu.gcc.help
From: zoo@cygnus.com (david d 'zoo' zuhn)
Subject: Re: installing gcc linker (ld)
X-Md4-Signature: 796e8ab8f16556f2173a375c72eba996
Organization: Cygnus Support -- +1 415 322 3816
Distribution: gnu
Date: Tue, 21 Jul 1992 18:44:50 GMT
	<35900@sdcc12.ucsd.edu>


   +laser3$ ld -d -r -Bstatic -o test2.o test.o
   +ld: test.o: wrong machine type
   +collect: /usr/bin/ld returned 4 exit status

   However, your stated command line seems to indicate that you're
   using the sparc 'ld' rather than
   '/usr/local/lib/gcc-lib/sun3/2.2.2/ld' (or something to that
   effect).

Actually, what's probably happening here is that collect is being
installed for the cross-compiler, and collect has buried in it some
hardcoded pathnames for where to find the system linker.  

You need to remove the ld in $(libsubdir)/ld and replace that with the
cross-linker.  The linker in the binutils should work just find for a
cross-68k environment.


  david d 'zoo' zuhn |  
    cygnus support   |  "Man made it, man can fix it."
    zoo@cygnus.com   |  		-- anonymous biker in South Dakota
Newsgroups: gnu.gcc.help
From: rms@gnu.ai.mit.edu (Richard Stallman)
Subject: building cross-compiler from sparc -> sco
Organization: GNUs Not Usenet
Distribution: gnu
Date: Fri, 31 Jul 1992 11:08:25 GMT

Please don't try to use version 2.1 at this date.
Many of its problems are already fixed in 2.2.2.

GCC version 2 is still pretty new (and still in beta test);
it isn't of much use to test any but the latest test version.
Newsgroups: gnu.gcc.help
From: kevinb@dev1.csg.ssd.fsi.com (Kevin Bonifield)
Subject: How to generate interrupt module with RTE
Date: Wed, 22 Jul 1992 12:56:14 GMT
Distribution: us
Organization: FlightSafety Simulation Systems Division - Tulsa

  I am using gcc for an embedded 68340 application.  Is there any way
to create an interrupt service routine that returns with RTE instead
of RTS?  Some compilers (Microtec) use a "#interrupt" to define functions
for this usage.  I will be filling the vector table and need to generate
quite a few ISRs.

Thanks!


----------------------------------------------------------------------------
Kevin Bonifield                        |  Phone: 918-251-0500 x520
Avionics Interface Computer Design     |  Email: kevinb@fsi.com
FlightSafety - Simulator Systems Div   |
----------------------------------------------------------------------------
From: Werner_Behrenbeck@pb.maus.de (Werner Behrenbeck)
Newsgroups: gnu.gcc.help
Subject: djgpp documentation problems
Date: Sun, 26 Jul 92 17:10:00 GMT
Organization: MausNet
X-Gateway: MausGate/News 1.11

i bought the 386 version of the gnu c++ system.
(name of "djgpp")
the doc-files are in TeX but i don't know how
to print this.
i have TeX on my computer (emtex 3.x).
please gimme a hint.
From: oueichek@ngulu (Ibaa Oueichek)
Newsgroups: gnu.gcc.help
Subject: HELP INSTALL GCC ON HP9k750
Date: 28 Jul 92 14:32:45 GMT
Organization: IMAG, University of Grenoble, France
X-Newsreader: Tin 1.1 PL4


  I'm trying desperately to install gcc-2.2.2 on an hp9k750 running hpux 
version 8.07.
  We need it as a development tool, so we need debugging facilities. But
unfortunately the file INSTALL says that the -g option isn't supported.
The proposed solution consists of grabbing the GDB debugger from mancos.cs.utah
edu (already done). Then install GAS in the file /usr/local/lib/gcc-lib/
hp9k750-hpux/2.2.2/as and delete the line :

#undef DBX_DEBUGGING_INFO 

from tm.h and then build gcc.
  The problem is we can't build gas (version 1.38), it seems that it doesn't
support the precision architecture of the hp9k750 (hope i'm committing a
mistake here).
  If we try to build gcc without gas (using the native hp assembler ) it runs
ok till the creation of gcc. Then gcc tries to compile libraries, and we get
the following error messages :

as: /usr/tmp/cca11705.s @line#20 [err#1050]
  Illegal symbol in label position - .stabs "long long int:t7=r1;0;-1;",128,0,0,
as: /usr/tmp/cca11705.s @line#21 [err#1050]
  Illegal symbol in label position - .stabs "short unsigned int:t8=r1;0;65535;",
Newsgroups: gnu.gcc.help
From: liz@grian.cps.altadena.ca.us (Liz Allen)
Subject: building cross-compiler from sparc -> sco
Organization: College Park Software, Altadena, CA
Date: Fri, 31 Jul 1992 07:13:43 GMT

I'm trying to build a cross-compiler for sparc to sco xenix using gcc
2.1.  I created a regular gcc first and that went fine.  I then tried
to create the cross-compiler following the directions about doing a
stage1 and a stage2 even though that didn't really make sense to me.
When I tried to build stage2, I got the following (I've added a couple
new lines):

  make CC=stage1/gcc CFLAGS="-g -O -Bstage1/"
  stage1/gcc -DCROSS_COMPILE   -g -O -Bstage1/     -I. -I. -I./config \
    -DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-sco/`awk '{printf "%s",
    substr ($4, 2, length ($4) - 3); }' ./version.c`/include\" \
    -DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/g++-include\" \
    -DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
    -DCROSS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-sco/`awk '{printf "%s", 
    substr ($4, 2, length ($4) - 3); }' ./version.c`/sys-include\" \
    -c `echo ./cccp.c | sed 's,^\./,,'`
  cccp.c:61: sys/types.h: No such file or directory
  cccp.c:62: sys/stat.h: No such file or directory
  cccp.c:63: ctype.h: No such file or directory
  cccp.c:64: stdio.h: No such file or directory
  cccp.c:65: signal.h: No such file or directory
  cccp.c:68: sys/file.h: No such file or directory
  cccp.c:70: sys/time.h: No such file or directory
  cccp.c:71: sys/resource.h: No such file or directory
  *** Error code 1
  make: Fatal error: Command failed for target `cccp.o'


Next I tried to do the following makes:

  make CC=/local/bin/gcc all
  make CC=/local/bin/gcc install-cross

The install-cross failed with "install: crtbegin.o: No such file or
directory".  So, I then tried:

   make CC=/local/bin/gcc crtbegin.o crtend.o

This gave me:

  ./gcc -DCROSS_COMPILE   -g -B./ -I. -I. -I./config -DCRT_BEGIN \
    -finhibit-size-directive -g0 -c ./crtstuff.c -o crtbegin.o

And then *lots* of assembler error messages.


Obviously, I'm not doing the Right Thing, but I can't figure out what
the Right Thing is.  I also don't have an SCO box here handy.  What I
need to do is create a cross-compiler without SCO which I can use to
cross-compile a program for a customer and then take the resultant
object file over to the customer's machine.  Is that possible?

Please email me as I can't keep up with as many newsgroups as I'd like
to!  ;-)

Thanks.
-- 
		- Liz Allen	liz@grian.cps.altadena.ca.us
				ames!elroy!grian!liz
"God is light; in him there is no darkness at all." -- 1 John 1:5b
From: brendan@cs.widener.edu (Brendan Kehoe)
Newsgroups: gnu.gcc.help
Subject: Re: Gnu C Libraries
Date: 23 Jul 1992 08:23:07 -0400
Organization: Widener University Computer Science Dept, Chester PA
NNTP-Posting-Host: betty.cs.widener.edu

beaker@milton.u.washington.edu wrote:
>I just wanted to confirm that the gnu C libraries don't
>come with gcc when you install it.  I already have obtained
>the g++ libraries and installed them, but I don't want to
>go to the trouble of putting on the gnu C libraries unless
>I have to.

You don't need the GNU libc assuming your system comes with one (/lib/libc.a?).

Most systems don't ship C++ libraries, but many do ship a linkable C library.
-- 
Brendan Kehoe, Sun Network Manager                      brendan@cs.widener.edu
Widener University                                                 Chester, PA
                                              At Bennigan's, EVERYONE gets it!
From: kimcm@login.dkuug.dk (Kim Chr. Madsen)
Newsgroups: gnu.gcc.help
Subject: Re: SYSCALLS.c.X ?? Where does it come from?
Date: 16 Jul 92 12:37:29 GMT

graham@convex.com (Marv Graham) writes:

>Starting with gcc-2.2.2.tar.Z, I can build all the tools, but when I execute
>protoize, it asks for file SYSCALLS.c.X.  Where does this file come from?

There is a bug -- ahemm small inconvenience -- in the Makefile, it states
that you should include "proto" in the LANGUAGES variable and protoize and
unprotoize will be installed, this is not strictly true. They will be compiled
and the SYSCALLS.c.X will be in the directory where you compiled the compiler.
To install it you have to use the makefile target "install-proto":

	make -k CC="stage2/gcc -Bstage2/" CFLAGS="-O" install-proto


							Kim Chr. Madsen.

Newsgroups: gnu.gcc.help
From: amc@WLV.IIPO.GTEGSC.COM (Allen M. Cohen)
Subject: Unresolved references during linking of g++ objects
Organization: GTE Government Systems
Distribution: usa
Date: Sat, 25 Jul 92 02:21:58 GMT

I built gcc 2.2.2 on a 486 machine with ISC Unix 3.0.

I tried to build a Public domain program called XcRichText, which
has some c++ code.  I used gcc 2.2.2.

I got the following undefined refs:
_assert__FPcT0i                     ../libXc.a
strcat__FPcPCc                      ../libXc.a
strchr__FPCci                       ../libXc.a
_15ParagraphFormat.default_tab_width_ ../libXc.a
strcspn__FPCcT0                     ../libXc.a

When I built with the -S option, I noticed that the assembly language
output does indeed make the latter references.

E.G.:
  Why does gcc build an instruction like:
     call strcat__FPcPCc
instead of just:
     call strcat???
-- 
<> Allen M. Cohen -- Autologic, Inc. 1050 Rancho Conejo Blvd.,T.O. Ca.91320 <>
<> 1853 Stonesgate St.             Internet:  amc@IIPO.GTEGSC.COM           <>
<> Westlake Village, Ca. 91361     Telephone: (805) 498-9611 ext. 195       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Organization: University of Illinois at Chicago
Date: Tuesday, 28 Jul 1992 14:47:24 CDT
From: Chuck Metalitz <U13272@uicvm.uic.edu>
Newsgroups: gnu.gcc.help
Subject: How to Install? Elementary question

Looking at the documentation, I infer that to install gcc one must already
have a working c compiler.  Failing that, one cross-compiles by using
a compiler on some other computer.

Am I correct so far?

Chuck Metalitz     u13272@uicvm.uic.edu
Northeastern Illinois Planning Commission
From: tardif@outaouais.ulaval.ca (Pierre-Martin Tardif)
Newsgroups: gnu.gcc.help
Subject: GCC as MC683xx cross-compiler on a PC
Date: 24 Jul 92 01:21:14 GMT
Organization: Universite Laval

Hi,

	As the subject line tells you, I am looking a way
to get GCC run on my PC (80386-33) to compile to S19
format of the MC68332 opcode...

	I am totaly new to GCC so I don't know
		WHERE, HOW and WHAT to get to make it work
		HOW to make it cross-compile MC68332 code
		If I will be able to link the code
		Etc...

So, hhhhheeeeeeeeeelllllllllppppppppp mmmmmmmmmeeeeeeee !!!!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-- 
Pierre-Martin Tardif, etudiant gradue  (email: tardif@gel.ulaval.ca)
Laboratoire de Vision et Systemes Numeriques
Universite Laval, Pavillon Adrien-Pouliot, local 00100-I, Ste-Foy, Quebec,
Canada, G1K 7P4         (418-656-2131, ext 4848)
Newsgroups: gnu.gcc.help
From: meissner@osf.ORG
Subject: Re: installing gcc linker (ld)
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 22 Jul 1992 06:31:14 GMT

| 
|    +laser3$ ld -d -r -Bstatic -o test2.o test.o
|    +ld: test.o: wrong machine type
|    +collect: /usr/bin/ld returned 4 exit status
| 
|    However, your stated command line seems to indicate that you're
|    using the sparc 'ld' rather than
|    '/usr/local/lib/gcc-lib/sun3/2.2.2/ld' (or something to that
|    effect).
| 
| Actually, what's probably happening here is that collect is being
| installed for the cross-compiler, and collect has buried in it some
| hardcoded pathnames for where to find the system linker.  
| 
| You need to remove the ld in $(libsubdir)/ld and replace that with the
| cross-linker.  The linker in the binutils should work just find for a
| cross-68k environment.

Or alternatively, put the real linker as $(libsubdir)/real-ld, and
then you can happily do cross development of GCC and G++ files.  If
your system needs collect, and you replace 'ld' with a real linker,
you will not be able to use static constructors and destructors in
G++.

--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

You are in a twisty little passage of standards, all conflicting.
Newsgroups: gnu.gcc.help
From: schilli@Physik.TU-Muenchen.DE (Burkhard Schillinger)
Subject: gcc for kontron sys7 unix (7char variable names) wanted
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Thu, 30 Jul 1992 13:45:44 GMT

recently, I was given an old 10 Mhz 68000 Unix machine, a kontron psi 9068,
with a defective hard disk. As the manufacturer was near by, I got it fixed,
and am now playing 'sysop' at home without getting killed by our 
'real' sysadmins here. The Unix is an AT&T based system 7 , but 
limited to 7 character variable names. So I would like to compile an old 
(slender!) version of gcc for this machine. However, sources for gcc I found
so far contain longer variable names, of course. So, before I spend weeks 
replacing variable names , my question arises: Has anybody had the same 
problem and has already converted gcc sources to  7character variable names, or does an old version exist with such? The version could be a very old one, newer ones could probably be compiled with the help of the first running version...

Any help would be highly appreciated!

Thanks in advance,  

-Burkhard.
From: sram@lccinc.UUCP (Siddharth Ram)
Newsgroups: gnu.gcc.help
Subject: gcc struc return convention ..
Date: 27 Jul 92 16:13:01 GMT
Organization: LCC Inc., Arlington VA

The gcc manual states :

        On the Sparc, GNU CC uses an incompatible calling convention for
        structures.  It passes them by including their contents in the argument
        list, whereas the standard compiler passes them effectively by
        reference.
        This really ought to be fixed, but such calling conventions are not yet
        supported in GNU CC, so it isn't straightforward to fix it.

        The convention for structure returning is also incompatible, and
        `-fpcc-struct-return' does not help.


are there any plans for fixing this ? if so, when is it due for
release. could some kind soul at FSF respond ?

thanks
siddharth Ram
uunet!hallofjustice!sram

-- 
.signature not included (empty)
Newsgroups: gnu.gcc.help
From: robert@triton.jpl.nasa.gov (Robert Angelino)
Subject: Wanted:  Back-end module(s) for GCC to produce either PDP-11...
Reply-To: Allen_Van_Sickel.LAX1B@xerox.com
Organization: Jet Propulsion Laboratory, Pasadena CA
Date: Tue, 28 Jul 1992 16:03:46 GMT

Request for a friend in need not on the internet.

	Wanted:  Back-end module(s) for GCC to produce either PDP-11 native
object code, or MACRO-11 assembler.  GCC will be used on a VAX running VMS as a
cross-compiler to a PDP-11 target.

thanks

reply to Allen_Van_Sickel.LAX1B@xerox.com

-robert
Newsgroups: gnu.gcc.help
From: chr@bio128.uni-bielefeld.de (Christian Bartling)
Subject: ld error
Date: Thu, 23 Jul 92 13:35:41 GMT
Organization: Universitaet Bielefeld

We have some problems to get the libg++-2.2 library compiled.

System information:

NeXT-Cube with NeXT-Step 2.0
GCC 2.1 from the Sonata NeXT-Archives
libg++ Source with one little modification in procbuf.C

The library compiles fine. In fact we get a libg++.a in the working  
directory, but every time the ld-linker is invoked a linking error occurs:

ld: /usr/local/lib/gcc-lib/next/2.1//libg++.a(streambuf.o) symbol 1391  
(___DTOR_LIST__) has unknown n_type field (0x16)
collect: /bin/ld returned 1 exit status

It looks like the wrong ld (/bin/ld) is used, so we copied the right ld  
int this directory and linked again. After a while the NeXT paniced and we  
had to power off.....

That`s it ! Where can we get a working linker or is it the wrong collect  
???

thanks

---
Christian Bartling
chr@bio128.uni-bielefeld.de
Newsgroups: gnu.gcc.help
From: kale@aelle.cs.odu.edu (Vijay S. Kale)
Subject: source for gcc gc+
Organization: Old Dominion University
Date: Tue, 28 Jul 1992 15:39:46 GMT


Hi Folks,

 Could any one out there give me pointers to the sources for gc+ and gcc
 
 Just two ftp sites would be more then enough.


 Will appreciate very much.


..Vijay
From: jclark@sdcc3.ucsd.edu (John Clark)
Newsgroups: gnu.gcc.help
Subject: Re: installing gcc linker (ld)
Date: 21 Jul 92 18:55:22 GMT
Distribution: gnu
Organization: University of California, San Diego

In article <1992Jul18.190052.11346@utkux1.utk.edu> rich@laser1.engr.utk.edu (Stevie-weave) writes:
+
+In a similar and related issue, I'm building gcc-2.2.2 as a x-compiler for
+VxWorks for a 68030 processor with the compiler host a Sparc2. Some other
+stuff we have needs a cross loader, but the ld that is in the
+sun3/2.2.2/ set doesn't work. It dies with
+
+laser3$ ld -d -r -Bstatic -o test2.o test.o
+ld: test.o: wrong machine type
+collect: /usr/bin/ld returned 4 exit status

The complete sparc to mc68030 environment requires that you build a
X-ld program supplied in the 'binutils' package, I think the current
released version is 1.94 or so. The 'ld' function built will take
the 68k gas output and create an executable.

If you've already compiled the GNU ld, and got the above error, then
you may not have 'configured' the build correctly. You should have
configured with a line something to the effect of:

configure -host=sun4 -target=sun3

(may be off modulo some dashes, but there is doc in the bintuils
directory with examples).

However, your stated command line seems to indicate that you're
using the sparc 'ld' rather than
'/usr/local/lib/gcc-lib/sun3/2.2.2/ld' (or something to that
effect).


As a practice, I've set up the m68k ld to be in /usr/local/bin/ld68k
which may be linked to the ugly path list above. Similarly, gcc68k
and gas68k would be linked to the appropriate m68k executables. This
prevents the inadvertent use of the host's native tools and the
resulting 'wrong machine....' error messages.

-- 

John Clark
jclark@ucsd.edu
Xref: sparky gnu.gcc.help:1762 comp.sys.sun.hardware:3497 comp.sys.sun.misc:3282 comp.unix.solaris:108
From: jclark@sdcc3.ucsd.edu (John Clark)
Newsgroups: gnu.gcc.help,comp.sys.sun.hardware,comp.sys.sun.misc,comp.unix.solaris
Subject: Re: SPARC assember directive ".text" generated by GCC 1.40
Date: 23 Jul 92 00:54:34 GMT
Followup-To: gnu.gcc.help
Organization: University of California, San Diego

In article <1992Jul22.194602.17372@amhux2.amherst.edu> twpierce@amhux1.amherst.edu (Tim Pierce) writes:
+
+GCC generates a ".text" assembler directive at the beginning of
>programs that utilize constant strings, apparently to inform the
+assembler that the following section of the program stores text.
+Example, from a program that includes the statement
+"printf ("%d\n", i)":
+
+gcc_compiled.:
+.text
+LC0:
+	.ascii "%d\12\0"
+	.align 4
+.global _main
+	.proc 1
+	...
+
+I cannot find mention of the .text directive anywhere in the Sun-4
+assembler manual, nor in the SPARC Architecture Manual from SPARC

The '.text' and '.data' directives are the only way to choose which
of the 3 segments to place data in an 'a.out' file, for the standard
GNU gas assembler. The 3rd is the BSS(Block Storage Segment) directive
'.comm' which causes space to be allocated when the program is loaded
but cannot be used to initialize data.

'.text' refers to the code segment, '.data' to initialized data. 

If you had the 'gas' document I think these directives are mentioned
there. Even more ancient, is the MIT 'as' doc.

The reason why strings wind up in '.text' is that 'guarentes' the
non-writeableness of them. Older compilers were haphazard about
where strings such as "mktmpXXXXXX" would wind up, and so one could
have

	tmpfileName = mktemp( "mktmpXXXXXX" );

Which the subroutine would re-write 'XXXXXX' with a unique number,
typically the process id number, and the program could then use for
a unique file name.

This is a bozo no-no in modern times, and so one must do some thing
like the following,

char TempFileName[] = "mktmpXXXXX";/* initialize a data segement string */

func()
{
	mktemp( TempFileName ); /* Create a unique string value */
}

Alternatively, you can use the '-fwriteable-strings' option and have
the good old days symantics about strings, i.e. you would have:


/Public/Gnu/LIBC/glibc-1.03 (174) gcc -S -O -fwritable-strings t.c
/Public/Gnu/LIBC/glibc-1.03 (175) more t.s
gcc2_compiled.:
.data
        .align 8
LC0:
        .ascii "test of writeable strings\12\0"
.text
        .align 4
        .global _main
        .proc   04
_main:
        !#PROLOGUE# 0
        save %sp,-136,%sp
        !#PROLOGUE# 1
        call ___main,0
        nop
        sethi %hi(LC0),%o0
        call _printf,0
        or %o0,%lo(LC0),%o0
        ret
        restore

/Public/Gnu/LIBC/glibc-1.03 (176)


As for the Sun4 reference manuals on 'as', the '.text' is
implemented as:

	.seg	"text"

and ".data" as:

	.seg	"data"

and ".comm" as:

	.seg	"bss"
VarName:
	.skip	 32	! allocate 32 bytes of storage for
			! character buffer VarName.
-- 

John Clark
jclark@ucsd.edu