Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / Mac Programming / December 2005



Tip: Looking for answers? Try searching our database.

LabVIEW 7.1 CIN, Xcode 2.2 link error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
C.R. Osterwald - 21 Dec 2005 17:20 GMT
I'm trying to link a very simple code interface node for LabVIEW 7.1,
and Xcode 2.2 generates a rather cryptic error that I have no clue
about sometime during the final link steps:

   Command /Developer/Private/jam failed with exit code 1

Here is the step it fails on:

   cd /Users/costerwa/Desktop/MakeBlockSigCIN
   setenv ASCII_OUTPUT_ANNOTATION YES
   setenv ENABLE_APPLE_JAM_EXTENSIONS YES
   setenv ENABLE_APPLE_JAM_OUTPUT_ANNOTATION YES
   setenv GROUP staff
   setenv NATIVE_ARCH ppc
   setenv USER costerwa
   /Developer/Private/jam -d1 -j1
JAMBASE=/Developer/Makefiles/pbx_jamfiles/ProjectBuilderJambase
JAMFILE=/Users/costerwa/Desktop/MakeBlockSigCIN/MakeBlockSigCIN.tmp\
Intermediates/MakeBlockSigCIN.build/Development/MakeBlockSigCIN.build/Ma
keBlockSigCIN.jam build ACTION=build _DEFAULT_GCC_VERSION=4.0
GCC_VERSION_IDENTIFIER=4_0 CONFIGURATION=Development
BUILD_STYLE=Development
CPP_HEADERMAP_FILE=/Users/costerwa/Desktop/MakeBlockSigCIN/MakeBlockSigC
IN.tmp\
Intermediates/MakeBlockSigCIN.build/Development/MakeBlockSigCIN.build/Ma
keBlockSigCIN.tmp.hmap SRCROOT=/Users/costerwa/Desktop/MakeBlockSigCIN
OBJROOT=/Users/costerwa/Desktop/MakeBlockSigCIN/MakeBlockSigCIN.tmp\
Intermediates
SYMROOT=/Users/costerwa/Desktop/MakeBlockSigCIN/MakeBlockSigCIN.tmp\
Intermediates DSTROOT=/tmp/MakeBlockSigCIN.dst

There is nothing in the Xcode 2.2 manual about exit codes, and "man
jam" is missing.  A search of developer.apple.com was fruitless.
"jamtool" and "jam tool" both give zero hits.

Does anyone know what this means?  Is this a fancy way of obscuring a
path or permissions error?
Hauke Fath - 21 Dec 2005 21:06 GMT
> There is nothing in the Xcode 2.2 manual about exit codes, and "man
> jam" is missing.  A search of developer.apple.com was fruitless.
> "jamtool" and "jam tool" both give zero hits.

Jam is an open source attempt at replacing make(1), hosted at
perforce.com - see e.g. http://maillist.perforce.com/pipermail/jamming

       hauke

Signature

Eine Linux User Group, um soziale Blockaden gegenüber Frauen
abzubauen?  Da wäre ja ein Schwulengesangsverein noch produktiver.

                                          {David Kastrup @ d.t.r}

C.R. Osterwald - 21 Dec 2005 22:07 GMT
>> There is nothing in the Xcode 2.2 manual about exit codes, and "man
>> jam" is missing.  A search of developer.apple.com was fruitless.
[quoted text clipped - 4 lines]
>
>        hauke

The main link seems to be here:  <http://www.perforce.com/jam/jam.html>

Unfortunately there doesn't seem to be any documentation about the exit
codes.
Eric Albert - 22 Dec 2005 06:42 GMT
> I'm trying to link a very simple code interface node for LabVIEW 7.1,
> and Xcode 2.2 generates a rather cryptic error that I have no clue
[quoted text clipped - 33 lines]
> Does anyone know what this means?  Is this a fancy way of obscuring a
> path or permissions error?

You didn't post enough of the detailed build log.  When you're using the
older Jam-based targets (as opposed to native targets, which you really
should upgrade to), Xcode uses jam to drive the whole build process.  
The error message tells you that something in your build failed, so
you'll want to find the error in the detailed build log and find the
line which corresponds to that, not the line which invokes jam.

-Eric

Signature

Eric Albert         ejalbert@cs.stanford.edu
http://outofcheese.org/

C.R. Osterwald - 22 Dec 2005 20:08 GMT
>> I'm trying to link a very simple code interface node for LabVIEW 7.1,
>> and Xcode 2.2 generates a rather cryptic error that I have no clue
[quoted text clipped - 40 lines]
>you'll want to find the error in the detailed build log and find the
>line which corresponds to that, not the line which invokes jam.

As you might have assumed, Xcode is still quite alien to me.  Too many
years of using CodeWarrior, I guess.  I did try upgrading the project,
which also failed to build, but differently.  It generated a
"FTextToPath error: 7" while trying to process one of the LabVIEW
libraries: "lvsbutilx: error building resource file: 7".  I still
haven't figured out where they list these errors.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.