[CWB] Character encoding problems when transferring corpus

[Hardie, Andrew]

A quick look around on the web suggests that this error arises if you try to link two files built for different processor architectures. From your gcc output, the root problem would seem to be the point at which libglib is linked into libcl : one has been built for i386 and one for x86-64. 
 
>>>
ld: warning: in /usr/local/Cellar/glib/2.32.4/lib/libglib-2.0.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
<<<
 
i.e. sounds as if Glib has been built for x86-64 but you are building CWB as i386. 

Now, the gcc call in your make-output has both -arch i386 and -arch x86_64 , so at a guess I would say that means that glib on your system must have been built as x86_64 only... Perhaps this is something you can fix with a flag to the configure script when you build it? 

(sorry I know nothing about OS X in particular as opposed to other Unixes, so cannot offer a more specific hint!)
 
Andrew.
________________________________

From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of Josep M. Fontana
Sent: 17 August 2012 16:19
To: Open source development of the Corpus WorkBench
Subject: Re: [CWB] Character encoding problems when transferring corpus




	Hi,
	
	I followed the instructions in INSTALL carefully. I ran 'make clean', 'make depend', 'make all' and 'make install'. Find the output of all these commands in attached files. 
	
	Before reading these files, please clarify something for me because perhaps there is something more fundamental I'm doing wrong. When you say "compile and install CWB 3.4", you mean running these 4 commands I have mentioned. I assume that if I am in /cwb, these commands will compile the source code that I have in this directory. When I read the INSTALL file, though, I see that its heading says "Release 3.5 BETA", not 3.4. 
	
	Before compiling, when I checked the code via subversion with:
	
	svn co https://cwb.svn.sourceforge.net/svnroot/cwb/cwb/trunk cwb
	
	I saw a message saying "Checked out revision 331."
	
	I just want to make sure I'm doing this right all the way and that I'm working with the correct version of the code.
	
	As you will see in output for 'make all', the previous error "lipo: can't open input file..." continues to appear but this time I don't see the other error you mention: 
	
	

		i686-apple-darwin10-gcc-4.2.1: /Users/jfontana/cwb/utils/../cl/libcl.a: No such file or directory
		

	The source of the error seems to be related to:
	
	"...file was built for unsupported file format which is not the architecture being linked (i386)"
	[...]
	"ld: symbol(s) not found for architecture i386"
	
	
	Josep M.
	
	On 8/17/12 3:13 AM, Stefan Evert wrote:
	

			"lipo: can't open input file: /var/folders/4c/4cqHpGvGGzucg8Ge2XytcU+++TM/-Tmp-//ccsmnms7.out (No such file or directory)
			make[1]: *** [cqp] Error 1
			make: *** [cqp] Error 2"
			

		That is a weird error message, but reading the complete output you sent previously shows the actual source of the error:
		
		

			i686-apple-darwin10-gcc-4.2.1: /Users/jfontana/cwb/utils/../cl/libcl.a: No such file or directory
			

		CQP (and the other command-line utilities) can't be compiled because you failed to build the CL library (libcl.a) due to the missing pkg-config.
		
		If you've restarted from scratch and followed the instructions in the INSTALL file, this should not happen, because "make all" should stop with an error when trying to compile libcl.a.
		
		Can you step through the process again carefully and send us every command you executed plus its output?  The easiest way to do so will be to open a new Terminal window, compile and install CWB 3.4 from this window, and then press Cmd-S (or select "Export Text As..." from the "Shell" menu).
		
		Best,
		Stefan
		_______________________________________________
		CWB mailing list
		CWB at sslmit.unibo.it
		http://devel.sslmit.unibo.it/mailman/listinfo/cwb