summaryrefslogtreecommitdiff
path: root/include/makeinclude/platform_sunos5_sunc++_4.1.GNU
diff options
context:
space:
mode:
Diffstat (limited to 'include/makeinclude/platform_sunos5_sunc++_4.1.GNU')
-rw-r--r--include/makeinclude/platform_sunos5_sunc++_4.1.GNU46
1 files changed, 0 insertions, 46 deletions
diff --git a/include/makeinclude/platform_sunos5_sunc++_4.1.GNU b/include/makeinclude/platform_sunos5_sunc++_4.1.GNU
deleted file mode 100644
index 8a0f97d0cc4..00000000000
--- a/include/makeinclude/platform_sunos5_sunc++_4.1.GNU
+++ /dev/null
@@ -1,46 +0,0 @@
-# SunOS 5.x (Solaris 2.x) with SunC++ 4.1
-# *not* using Orbix
-#
-# Note: with the +w option, some ACE files might generate warnings of
-# one of these types:
-# 1) "template manager : Warning: No valid template database available.
-# Creating default repository "Templates.DB"":
-# self explanatory, and apparently harmless.
-# 2) "Warning: Could not find source for " one of the following:
-# default constructor, copy constructor, destructor, or assignment
-# operator. It appears that with +w, Sun C++ 4.x issues this warning
-# whenever it has to generate one of these functions (because it wasn't
-# defined by the user). This isn't really a problem.
-# 3) "Warning: <foo> hides the function " or "hides the same name in an
-# outer scope". A useful warning, perhaps, but not really a problem.
-# There should be no other warnings from Sun C++ when building ACE.
-#
-CC = cc
-CXX = CC +w -mt -noex -pta # -D__ACE_INLINE__
-DLD = $(CXX)
-LD = $(CXX)
-LDFLAGS += -R $(WRAPPER_ROOT)/ace
-LIBS += -lsocket -ldl -lnsl -lgen
-PIC = -PIC
-# SUNC++ 4.1 has a bug with the -xar command:
-#
-# from 'CC -readme' the following bug is reported:
-#
-# 4. Using -xar to add generated templates
-# ----------------------------------------
-#
-# When using -xar to add generated templates to an archive,
-# please be aware that this command will both update
-# existing object files in the archive, and add new ones.
-# Existing object files that may be obsolete will still
-# be present. In these cases, the safest course of action
-# would be to delete the .a file prior to the invocation of -xar.
-#
-# so here we remove the archive prior to making the new one
-#
-AR = rm -f $@ ; CC
-ARFLAGS = -xar -o
-RANLIB = echo
-SOFLAGS = -G $(CPPFLAGS)
-SOBUILD = $(COMPILE.cc) $(PIC) -o $(VSHDIR)$*.o $<; \
- $(SOLINK.cc) -o $@ -h $@ $(LDFLAGS) $(VSHDIR)$*.o