Re: [webkit-dev] WebKit Fails to build in XCode 3.1 - (SOLVED)
Thank you! Mark, Thank you! Dave, I edited my .profile as instructed and I'm now able to build again - yippee! And thank you once again. Best regards, Sam On 3 Jul 2008, at 23:24, Mark Rowe wrote: On Jul 3, 2008, at 3:17 PM, Samuel Davis wrote: Hi David, Thanks for getting back to me :-) After running *which iconv* I get the following: Macintosh:~ samueljd$ which iconv /sw/bin/iconv After running *iconv --version* I get the following: Macintosh:~ samueljd$ iconv --version iconv (GNU libiconv 1.9) Copyright (C) 2000-2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Bruno Haible. Yes! I do have Fink installed on my Mac and I also have the latest version of Mac OSX installed (i.e Leopard 10.5.4). You have an older version of iconv installed via fink than what comes with Leopard. Either remove /sw/bin from your PATH environment variable, move it to the end of PATH after /usr/bin so that system binaries take preference, upgrade the version of iconv that you have installed via fink, or edit the copystrings script to hard-code /usr/bin/iconv. Any of these approaches should resolve your problem. - Mark ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] WebKit Fails to build in XCode 3.1
Xcode 3.1 should work.
If you run which iconv from a Terminal window, what is the output?
If you run iconv --version, what is the output?
Do you have Fink or MacPorts installed?
Which version of Mac OS X do you have installed?
Dave
On Thu, 7/3/08, Samuel Davis [EMAIL PROTECTED] wrote:
Hi Mark, Hi David
Your guidance is much appreciated on this issue - thanks!
I have examined the *copystrings* script file on my
machine, which
happens to be a Ruby script, and the part where the command
*iconv* is
used is shown below:
# Convert the input file to the output encoding (usually
UTF-16); the
output location is normally in the Resources directory of
the product.
system('iconv --from-code=' +
OPTIONS[:InputEnc] + ' --to-
code=' + OPTIONS[:OutputEnc] + '
' + path + ' ' +
OPTIONS[:OutputDir] + '/' + pathBaseName +
'')
if $?.termsig then $stderr.puts
#{File.basename($0)}: error:
iconv terminated with signal #{$?.termsig} ; exit 1 ;
end
exit $?.exitstatus unless $?.exitstatus == 0
From what I can see, I would interpret it as shown below:
[-f fromcode] is equivalent to '--from-code=
' + OPTIONS[:InputEnc]'
[-t tocode] is equivalent to '
--to-code=' + OPTIONS[:OutputEnc] +
'
[file ...] is equivalent to ' + path +
' ' + OPTIONS[:OutputDir]
+ '/' + pathBaseName + '')
Here is the Man pages synopsis:
iconv [-c] [-s] [-f encoding] [-t encoding]
[inputfile ...]
iconv -l
There seems to be some inconsistencies here! And, I would
conclude
that there is a mis-match in the syntax between them.
I previously forgot to mention that I had updated my XCode
tool chain
between the time I was able to build and the time that I
wasn't able
to build (i.e. now!). I had a look at the WebKit pages
and all it
says is that XCode 2.3 or later is required to build. So I
would
assume that my installation of XCode 3.1 should be okay.
But it
appears not to be!
Could it be that XCode 3.1 can't build WebKit?
So far I have updated my SVN Client, deleted my local
WebKit trunk
(with rm -rf), Installed a brand new copy of the WebKit
trunk, but the
problem still persist! I'm not able to build on my
machine.
I would appreciate any further ideas that you might have
that would
help me to solve this most annoying problem.
Best regards,
Sam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] WebKit Fails to build in XCode 3.1
Hi David,
Thanks for getting back to me :-)
After running *which iconv* I get the following:
Macintosh:~ samueljd$ which iconv
/sw/bin/iconv
After running *iconv --version* I get the following:
Macintosh:~ samueljd$ iconv --version
iconv (GNU libiconv 1.9)
Copyright (C) 2000-2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Written by Bruno Haible.
Yes! I do have Fink installed on my Mac and I also have the latest
version of Mac OSX installed (i.e Leopard 10.5.4).
Thanks!
Best regards,
Sam
On 3 Jul 2008, at 15:36, David Kilzer wrote:
Xcode 3.1 should work.
If you run which iconv from a Terminal window, what is the output?
If you run iconv --version, what is the output?
Do you have Fink or MacPorts installed?
Which version of Mac OS X do you have installed?
Dave
On Thu, 7/3/08, Samuel Davis [EMAIL PROTECTED] wrote:
Hi Mark, Hi David
Your guidance is much appreciated on this issue - thanks!
I have examined the *copystrings* script file on my
machine, which
happens to be a Ruby script, and the part where the command
*iconv* is
used is shown below:
# Convert the input file to the output encoding (usually
UTF-16); the
output location is normally in the Resources directory of
the product.
system('iconv --from-code=' +
OPTIONS[:InputEnc] + ' --to-
code=' + OPTIONS[:OutputEnc] + '
' + path + ' ' +
OPTIONS[:OutputDir] + '/' + pathBaseName +
'')
if $?.termsig then $stderr.puts
#{File.basename($0)}: error:
iconv terminated with signal #{$?.termsig} ; exit 1 ;
end
exit $?.exitstatus unless $?.exitstatus == 0
From what I can see, I would interpret it as shown below:
[-f fromcode] is equivalent to '--from-code=
' + OPTIONS[:InputEnc]'
[-t tocode] is equivalent to '
--to-code=' + OPTIONS[:OutputEnc] +
'
[file ...] is equivalent to ' + path +
' ' + OPTIONS[:OutputDir]
+ '/' + pathBaseName + '')
Here is the Man pages synopsis:
iconv [-c] [-s] [-f encoding] [-t encoding]
[inputfile ...]
iconv -l
There seems to be some inconsistencies here! And, I would
conclude
that there is a mis-match in the syntax between them.
I previously forgot to mention that I had updated my XCode
tool chain
between the time I was able to build and the time that I
wasn't able
to build (i.e. now!). I had a look at the WebKit pages
and all it
says is that XCode 2.3 or later is required to build. So I
would
assume that my installation of XCode 3.1 should be okay.
But it
appears not to be!
Could it be that XCode 3.1 can't build WebKit?
So far I have updated my SVN Client, deleted my local
WebKit trunk
(with rm -rf), Installed a brand new copy of the WebKit
trunk, but the
problem still persist! I'm not able to build on my
machine.
I would appreciate any further ideas that you might have
that would
help me to solve this most annoying problem.
Best regards,
Sam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] WebKit Fails to build in XCode 3.1
Hi Mark, Thanks again for the hint... I have been monitoring the Latest Build Status page at http://build.webkit.org/one_box_per_builder and it appears that there hasn't been a successful build for a while, at least the status shows that the last 8 build attempts failed. The Status page shows that the last successful build was on trunk 27090. I would have greater confidence that the WebKit source would build successfully on my machine if WebKit Org were able to build a successful target themselves. Hence, I will make another attempt to build locally when the Build Status shows that a successful build has been achieved by WebKit Org. Also I'm using the Command Line to build my local target. I have examined the log that was produced by the Terminal when I attempted a local build and I couldn't find anything that would indicate that an error occurred during the build process apart from the comments that I sent you below. Once again, thanks for helping me out :-) Best regards, Sam On 2 Jul 2008, at 01:33, Mark Rowe wrote: On 2008-07-01, at 17:24, Samuel Davis wrote: Hi Mark, Thanks for the hint ;-) [.. snip ..] The following build commands failed: JavaScriptGlue: CopyStringsFile /Users/samueljd/WebKit/WebKitBuild/Release/ JavaScriptGlue.framework/Versions/A/Resources/English.lproj/ InfoPlist.strings English.lproj/InfoPlist.strings (1 failure) Again, this only indicates that a command earlier in the build failed. The specific error message will be earlier in the build transcript. Are you building from within Xcode or from the command- line? If from the command-line, the full transcript should be displayed in your terminal window. If you're building from within Xcode, see http://roobasoft.com/blog/2006/04/17/see-build-transcripts/ for how to display the build transcript. If you can provide the actual error that is occurring it will be much easier to help you. Thanks, Mark ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] WebKit Fails to build in XCode 3.1
If you had a connection failure while checking out/updating Subversion, you may want to remove the entire directory that was being updated, or simply check out the source from scratch again. An svn stat . command may tell you something, but sometimes svn can hork a subdirectory structure to the point where it's easier to simply remove (rm -rf) the directory and then run svn up again (or check out the whole source from scratch). Dave On Wed, 7/2/08, Samuel Davis [EMAIL PROTECTED] wrote: Hi Mark, This problem just won't go away :-( RE: __ Checking Dependencies... ** BUILD FAILED ** The following build commands failed: JavaScriptGlue: CopyStringsFile /Users/samueljd/WebKit/WebKitBuild/Release/ JavaScriptGlue.framework/Versions/A/Resources/English.lproj/ InfoPlist.strings English.lproj/InfoPlist.strings (1 failure) When I first installed the SVN client and checked out the WebKit trunk I was able to build without any problems. The problems occurred some weeks later when my internet connection went down while I was checking out an updated WebKit trunk. I have since deleted the old version of WebKit trunk from my machine and checked out a spanking new one but I'm still not able to build the target on my machine. Believe you me this is really frustrating mainly because I can't see why I can't build targets anymore even with a brand new trunk. Do I need to update my SVN client? While building WebKit with command-line in the Terminal, the output shows lots of compiler commands but there is nothing in it that I can identify as a compiler error. So I tried a creative approach to solving the problem by attempting to build JavaScriptCore.xcodeproj in XCode. The JavaScriptCore target built successfully without any errors. However, when I tried to build JavaScriptGlue.xcodeproj within XCode I had numerous errors (53) as apposed to a single Error when using the command-line. Perhaps this suggest that there is some inter-dependancies between the sub-projects (i.e. JavaScriptCore, JavaScriptGlue, WebCore and WebKit) when building WebKit, hence the reason for the build pearl script. Here is where the command that fails is first displayed the Terminal: CopyStringsFile /Users/samueljd/WebKit/WebKitBuild/Release/ JavaScriptGlue.framework/Versions/A/Resources/English.lproj/ InfoPlist.strings English.lproj/InfoPlist.strings mkdir /Users/samueljd/WebKit/WebKitBuild/Release/ JavaScriptGlue.framework/Versions/A/Resources/English.lproj cd /Users/samueljd/WebKit/JavaScriptGlue /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/ Contents/Resources/copystrings --validate --inputencoding UTF-16 -- outputencoding UTF-16 English.lproj/InfoPlist.strings --outdir /Users/ samueljd/WebKit/WebKitBuild/Release/JavaScriptGlue.framework/Versions/ A/Resources/English.lproj Usage: iconv [-c] [-s] [-f fromcode] [-t tocode] [file ...] or:iconv -l After this output, there are a lot of compiler commands starting with CompileC but I can't see anything that looks like an error code or output. Strange problem indeed! Do you know of any creative ways in which I could start building WebKit again on my local machine? Any suggestions would be much appreciated :-) Best regards, Sam___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] WebKit Fails to build in XCode 3.1
Hello, Hallo, Hei, Hola, I have been trying to build WebKit (http://webkit.org/) on my local machine and the build process keeps failing with the following reason: --- === BUILDING AGGREGATE TARGET All OF PROJECT JavaScriptCore WITH CONFIGURATION Release === Checking Dependencies... ** BUILD FAILED ** The following build commands failed: JavaScriptCore: Ld /Users/samueljd/WebKit/WebKitBuild/Release/ JavaScriptCore.framework/Versions/A/JavaScriptCore normal i386 jsc: Ld /Users/samueljd/WebKit/WebKitBuild/Release/jsc normal i386 (2 failures) --- Procedure: 1) Check out WebKit source from the SVN repository: svn checkout http://svn.webkit.org/repository/webkit/trunk WebKit Build revision that was checked out: 34932 2) Build Source on local machine: WebKit/WebKitTools/Scripts/build-webkit This command run's a perl script that should build the target. Result: The build process fails and gives the aforementioned reason above as the cause of failure :-( According the the build status information at http://build.webkit.org/one_box_per_builder build 34932 has failed. - Does this mean that it's not possible to do a local build? - Also, does anyone know what the general problem could be? Kindest regards, Sam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] WebKit Fails to build in XCode 3.1
On 2008-07-01, at 16:12, Samuel Davis wrote: Hello, Hallo, Hei, Hola, I have been trying to build WebKit (http://webkit.org/) on my local machine and the build process keeps failing with the following reason: === BUILDING AGGREGATE TARGET All OF PROJECT JavaScriptCore WITH CONFIGURATION Release === Checking Dependencies... ** BUILD FAILED ** The following build commands failed: JavaScriptCore: Ld /Users/samueljd/WebKit/WebKitBuild/Release/ JavaScriptCore.framework/Versions/A/JavaScriptCore normal i386 jsc: Ld /Users/samueljd/WebKit/WebKitBuild/Release/jsc normal i386 (2 failures) These are not error messages themselves, they are only indicative of errors earlier in the build process. To see the error messages themselves you should find where the two failing commands were executed earlier in the build. According the the build status information at http://build.webkit.org/one_box_per_builder build 34932 has failed. - Does this mean that it's not possible to do a local build? Yes, that means the build was broken in that revision. It has since been fixed, so after svn uping you should be good to go. - Mark smime.p7s Description: S/MIME cryptographic signature ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
