Hello,

I have performed a nuightly when i check the log i have this king of error :

cc1: error: unrecognized command line option "-fno-dwarf2-indirect-strings"
dmake: Warning: Target `def.targ' not remade because of errors

This error is frequently appears for files into the 
usr/src/uts/i86pc/unix/debug32 folder and the
usr/src/uts/i86pc/unix/debug64 folder

I use the on-src-24042006 sources.

This is my opensolaris.sh file :

NIGHTLY_OPTIONS="-FNnadDmrt";           export NIGHTLY_OPTIONS

# This is a variable for the rest of the script - GATE doesn't matter to
# nightly itself
GATE=testws;                    export GATE

# CODEMGR_WS - where is your workspace at (or what should nightly name it)
CODEMGR_WS="/export/home/$GATE";                        export CODEMGR_WS

# Location of encumbered binaries.
ON_CLOSED_BINS="$CODEMGR_WS/closed";            export ON_CLOSED_BINS

# This flag controls whether to build the closed source.  If
# undefined, nightly(1) and bldenv(1) will set it according to whether
# the closed tree is present.
# CLOSED_IS_PRESENT="no";               export CLOSED_IS_PRESENT

# Maximum number of dmake jobs.  The recommended number is 2 + (2 *
# NCPUS), where NCPUS is the number of CPUs on your build system.
maxjobs() {
        ncpu=`/usr/sbin/psrinfo -p`
        expr $ncpu \* 2 + 2
}
DMAKE_MAX_JOBS=`maxjobs`;                       export DMAKE_MAX_JOBS

# path to onbld tool binaries
ONBLD_BIN="/opt/onbld/bin"

# used by bfu.
FASTFS=$ONBLD_BIN/`uname -p`/fastfs;            export FASTFS
BFULD=$ONBLD_BIN/`uname -p`/bfuld;              export BFULD
GZIPBIN=/usr/bin/gzip;                          export GZIPBIN
ACR=$ONBLD_BIN/acr;                             export ACR

# PARENT_WS is used to determine the parent of this workspace. This is
# for the options that deal with the parent workspace (such as where the
# proto area will go).
PARENT_WS="";                   export PARENT_WS

# CLONE_WS is the workspace nightly should do a bringover from. Since it's
# going to bringover usr/src, this could take a while, so we use the
# clone instead of the gate (see the gate's README).
CLONE_WS="";                    export CLONE_WS

# The bringover, if any, is done as STAFFER.
# Set STAFFER to your own login as gatekeeper or developer
# The point is to use group "staff" and avoid referencing the parent
# workspace as root.
# Some scripts optionally send mail messages to MAILTO.
#
STAFFER=root;                           export STAFFER
MAILTO=$STAFFER;                        export MAILTO

# The project (see project(4)) under which to run this build.  If not
# specified, the build is simply run in a new task in the current project.
BUILD_PROJECT=;                         export BUILD_PROJECT

# You should not need to change the next four lines
LOCKNAME="`basename $CODEMGR_WS`_nightly.lock"; export LOCKNAME
ATLOG="$CODEMGR_WS/log";                        export ATLOG
LOGFILE="$ATLOG/nightly.log";                   export LOGFILE
MACH=`uname -p`;                                export MACH

# REF_PROTO_LIST - for comparing the list of stuff in your proto area
# with. Generally this should be left alone, since you want to see differences
# from your parent (the gate).
#
REF_PROTO_LIST=$PARENT_WS/usr/src/proto_list_${MACH}; export REF_PROTO_LIST

# where cpio archives of the OS are placed. Usually this should be left
# alone too.
CPIODIR="${CODEMGR_WS}/archives/${MACH}/nightly";       export CPIODIR

#
#       build environment variables, including version info for mcs, motd,
# motd, uname and boot messages. Mostly you shouldn't change this except
# when the release slips (nah) or you move an environment file to a new
# release
#
ROOT="$CODEMGR_WS/proto/root_${MACH}";  export ROOT
SRC="$CODEMGR_WS/usr/src";              export SRC
VERSION="$GATE";                        export VERSION

# the source product has no SCCS history, and is modified to remove source
# that cannot be shipped. EXPORT_SRC is where the clear files are copied, then
# modified with 'make EXPORT_SRC'.
EXPORT_SRC="$CODEMGR_WS/export_src";    export EXPORT_SRC

# CRYPT_SRC is similar to EXPORT_SRC, but after 'make CRYPT_SRC' the files in
# xmod/cry_files are saved. They are dropped on the exportable source to create
# the domestic build.
CRYPT_SRC="$CODEMGR_WS/crypt_src";      export CRYPT_SRC

#
# the RELEASE and RELEASE_DATE variables are set in Makefile.master;
# there might be special reasons to override them here, but that
# should not be the case in general
#
# RELEASE="5.11";                       export RELEASE
# RELEASE_DATE="October 2007";          export RELEASE_DATE

# proto area in parent for optionally depositing a copy of headers and
# libraries corresponding to the protolibs target
# not applicable given the NIGHTLY_OPTIONS
#
PARENT_ROOT=$PARENT_WS/proto/root_$MACH; export PARENT_ROOT

#
#       package creation variable. you probably shouldn't change this either.
#
PKGARCHIVE="${CODEMGR_WS}/packages/${MACH}/nightly";    export PKGARCHIVE

# we want make to do as much as it can, just in case there's more than
# one problem.
MAKEFLAGS=k;    export MAKEFLAGS

# Magic variable to prevent the devpro compilers/teamware from sending
# mail back to devpro on every use.
UT_NO_USAGE_TRACKING="1"; export UT_NO_USAGE_TRACKING

# Build tools - don't change these unless you know what you're doing.  These
# variables allows you to get the compilers and onbld files locally or
# through cachefs.  Set BUILD_TOOLS to pull everything from one location.
# Alternately, you can set ONBLD_TOOLS to where you keep the contents of
# SUNWonbld and SPRO_ROOT to where you keep the compilers.  SPRO_VROOT
# exists to make it easier to test new versions of the compiler.
BUILD_TOOLS=/opt;                               export BUILD_TOOLS
#ONBLD_TOOLS=/opt/onbld;                        export ONBLD_TOOLS
SPRO_ROOT=/opt/SUNWspro;                        export SPRO_ROOT
SPRO_VROOT=$SPRO_ROOT;                          export SPRO_VROOT

# This goes along with lint - it is a series of the form "A [y|n]" which
# means "go to directory A and run 'make lint'" Then mail me (y) the
# difference in the lint output. 'y' should only be used if the area you're
# linting is actually lint clean or you'll get lots of mail.
# You shouldn't need to change this though.
#LINTDIRS="$SRC y";     export LINTDIRS

# Set this flag to 'n' to disable the automatic validation of the dmake
# version in use.  The default is to check it.
#CHECK_DMAKE=y

# Set this flag to 'n' to disable the use of 'checkpaths'.  The default,
# if the 'N' option is not specified, is to run this test.
#CHECK_PATHS=y

# BRINGOVER_FILES is the list of files nightly passes to bringover.
# If not set the default is "usr", but it can be used for bringing
# over deleted_files or other nifty directories.
#BRINGOVER_FILES="usr deleted_files"





-----Message d'origine-----
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Jean-François Ndi
Envoyé : samedi 29 avril 2006 07:18
À : [email protected]
Objet : Re: [osol-help] Install of opensolaris


Hello,

>Can someone help
> me!
> 
> 
>I try to create and
> tarball of open solaris for install it, but i have
> this message :
> 
># Install -G kernel.foo
> -k i86pc
> 
> cp: cannot access
> /export/home/testws/usr/src/uts/i86pc/unix/debug64/uni
> x
> 
>can't create
> /tmp/Install.root/i86pc/platform/i86pc/kernel.foo/amd6
> 4/unix
> 
>Install failed
> 
> #
>
> 
>This file do not exist
> in the sources.
>

Have you performed a nightly? If yes, have you checked the log to verify that 
everything went right?

> 
>What can i do?
>

Hope that can help,

J-F
 
 
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
[email protected]
_______________________________________________
opensolaris-help mailing list
[email protected]

Reply via email to