Compiling Packages from Source

I am having some issues using the "make" command when compiling any kind of source code. When doing so, I get the sort of error that one would would expect when trying to build without headers. However, this is not the case. I do have the kernel headers installed (matching the kernel version, of course) and still I am unable to build. Interestingly enough, I am able to make packages from the AUR from source using packer, so I assume that I am able to make packages. Or am I painfully deluded in my understanding?

TheHebes wrote:@tavianator- I have looked, the RTL8188CE driver is not present is NOT in the AUR. (packer -Ss r 8188 comes up with nothing). Furthermore, @graysky, I do have have kernel26-headers installed. Both the kernel and headers are version 2.6.39 3-1. For the most part, by the looks of it, there is no packagebuild available, so managing this through pacman is not looking like an option. From what I gather, "make" is the only way this is going to compile.
The driver you want is indeed in the AUR. Look at the description:
http://aur.archlinux.org/packages.php?ID=46797
The driver name and version number exactly match the errors from make you posted above:
TheHebes wrote:make[1]: *** No rule to make target `*/rtl8192ce_linux_2.6.0006.0321.2011/HAL/rtl8192'. Stop.
Last edited by mrstegeman (2011-08-10 11:36:02)

Similar Messages

Compile a package from source...

I'm trying to learn how to compile a package from source code.
I choose bfgminer as my example. I know there's already a pre-built package.
# Get bfgminer-3.3.0
wget http://luke.dashjr.org/programs/bitcoin … 3.3.0.tbz2
tar -Jxvf bfgminer-3.3.0.tar.bz2
cd bfgminer-3.3.0
pacman -S uthash # Required Dependencies
pacman -S lm_sensors
# I want to be able to remove unnecessary modules, so I defined CFLAGS:
CFLAGS="--disable-avalon --disable-opencl --disable-bitfury --disable-littlefury --disable-bitforce --disable-modminer --disable-x6500 --disable-ztex"
./configure
# The package compiles successfully, but It seems to have ignored the CFLAGS.
Configuration Options Summary:
Enabled..Drivers.....: avalon bigpic bitforce bitfury_gpio cairnsmore erupter icarus littlefury modminer opencl opencl:adl opencl:sensors x6500 ztex
Disabled.Drivers.....: bfsb cpu metabank proxy
To enable proxy, install libmicrohttpd 0.9.5+ (getwork) or libevent 2.0.3+ (stratum)
Enabled..Algorithms..: SHA256d
Disabled.Algorithms..: scrypt
Enabled..Options.....: ncursesw5
Disabled.Options.....:
Compilation............: make (or gmake)
CFLAGS...............: -pthread -g -O2 -I/usr/include/libusb-1.0 -pthread -Ilibblkmaker
LDFLAGS..............: -pthread -Llibblkmaker/.libs -Wl,-rpath,\$$ORIGIN/libblkmaker/.libs,-zorigin -lpthread -ldl -lcurl -ljansson -L/usr/lib -lncursesw -lm -ludev -lusb-1.0 -lsensors -lblkmaker_jansson-0.1 -lblkmaker-0.1
Installation...........: make install && ldconfig #(as root if needed, with 'su' or 'sudo')
prefix...............: /usr/local
What did I do wrong?

cfr wrote:
ThinkFast wrote:Well you may have misread it at first, but I am running as root. For me, after building a system it seems hard to know when to create a standard user. And it's easy to just continue as root. Most tutorials don't mention it at all.
Can it be done after the first login as root and changing the root password?
Easy it may be, but it is also incredibly dangerous. I find it terrifying that people even think of doing this.
I don't know which tutorials you are reading but the Beginners' Guide clearly includes this step as the first one to complete after rebooting into your new system:
https://wiki.archlinux.org/index.php/Be … management
You should do the minimum necessary as root. You should only ever perform a task as root if (1) the task cannot be performed with less privileges, (2) you understand exactly what the task is designed to accomplish AND (3) you understand why it needs to be performed with root privileges.
While I admit that most do not go this far, I do not compile code with an account which is even in wheel. That means I don't compile even as my regular user - let alone root.
I guess I have just gotten lucky so far. Thanks for your advise.

Compiling a package from source files

I am trying to install a package from source files. The installation instructions for this package say that I should just download the scripts to one directory, enter the correct paths in the Makefile (which comes with the package) and run "make".
The problem is that while the g++ compiler is there on my computer
(there is a binary called g++ located at
/Developer/usr/bin/g++
I am not sure if that is the real compiler. Or where the c header files are, for instance, I can't find math.h, or stdio.h or any of the other standard files.
Any help will be greatly appreciated. I am very new to command lines, so please explain as you would to a five year old.
To help with specifics, I edited the Makefile so that the first part looks like:
#MATLABDIR ?= /usr/local/matlab
# for Mac
MATLABDIR ?= /Applications/MATLAB_R2008b.app
CXX ?= g++
#CXX = g++-4.1
CFLAGS = -Wall -Wconversion -O3 -fPIC -I$(MATLABDIR)/extern/include
Thanks a ton for the help

Your compiler program is gcc. (/usr/bin/gcc).
http://gcc.gnu.org/
in terminal type (at the prompt):
gcc --version
(press return)
should output the following:
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5646) (dot 1)
Copyright (C) 2007 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.
If it does, your compiler is alive and kicking and ready for action, if not, reinstall developer tools
package from your SL install DVD.
The usual ritual for compiling is to drag the directory containing the source code to your desktop,
then, in terminal, change terminal path to the source directory using the change directory command
"cd".
example; say I have a program called cdrtools 2.0.1 and the source is in a folder I dragged to my
desktop called cdrtools_2.0.1:
In terminal i would type:
cd /Users/kj/Desktop/cdrtools_2.0.1
Follow the instructions that come with the package. Typically they will tell you to:
./configure
( Many packages have a configure script which will query your system and configure themselves
appropriately. Not supported by all software).
make
( Compile the software. Some require a file name to build such as make foo. make reads a file
normally called Makefile for what commands to run).
make install
( Install the software. Typically packages will put themselves in /usr/local. Run as root).
That is the usual ritual, but you must follow the instructions that come with the software, as they
may vary.
Read documentation!
Look for files called: INSTALL, README, SETUP, or similar.
For more information see the following:
http://luv.asn.au/overheads/compile.html
Now beware that some source code written before Snow Leopard was released may not compile
properly on SL, because of SL's 64Bit gcc extensions. If the source has not been updated to run
under the Snow Leopard compiler, then the compilation may fail.
IF the program fails to compile, or fails to run after compiling, then most likely, then the source
may need updating.
good luck, and don't pull all your hair out at once. Save some for later.
The guys in the 'NIX forum can help you with all the grizzly details as you go on your quest.
http://discussions.apple.com/forum.jspa?forumID=735
Good luck,
Kj ♘

Making package from source

I just created a working build of firefox 3.0.8 from source without using abs. I am wondering how I would be able to turn my build into a package that I can install via pacman.
I don't really know what information I need to give but any help would be appriciated.

Spelchek wrote:I'm running arch for fun and expirience, so I thought that compiling something the normal way would be a good thing to learn.
I was overlooking things as usual, but I have run into a new problem. When I run the "make package" command it creates a bzip and not the gzip as required by pacman.
but...abs IS the normal way. It just keeps track of all the files installed and makes the package for pacman...., which, is exactly what you're asking how to do.
If you want to compile a custom firefox for yourself, do it in the form of a PKGBUILD

Compiling packages from command line

hi...good morning all...
I want to compile 5 packages from command prompt..
I have written a batch file like this...
d:
call sqlplus -s scott/tiger@ora11g @package1.sql
call sqlplus -s scott/tiger@ora11g @package2.sql
call sqlplus -s scott/tiger@ora11g @package3.sql
call sqlplus -s scott/tiger@ora11g @package4.sql
call sqlplus -s scott/tiger@ora11g @package5.sql
pause
exit
But it is not running...only the package 1 is getting compiled after putting a '/' after the prompt "call sqlplus -s scott/tiger@ora11g @package1.sql"..
But the rest of the packages are not getting compiled..it is not throwing any error also...I have kept the 5 package bodies in the D drive...
Please help..

thanks a lot friends for your replies...
@mahir: I have made a test.sql(in d drive) file which contains the following wntry only
@d:\package1.sql
@d:\package2.sql
@d:\package3.sql
@d:\package4.sql
@d:\package5.sql
and from another bat file(run.bat) i have called that...
sqlplus -s scott/tiger@oracle11g @test.sql
but it is not running....
I have pressed '/' then the first package compiled and again it got stopped..
the number of times i pressed '/', the number of times it got compiled...there are only 5 packages...but if i pressed the '/' for 20 times ,it is compiled for 20 times...so i think the rest of the packages are not getting compiled...
@ravikumar: I dont want to execute the same command for different packages...I want to run all the packages at a single go...

Virtual memory exhausted when compiling packages from AUR

Recently I've seen this error more and more often. When I tried compiling some packages from AUR, I ended up getting "virtual memory exhausted" error. The first time it happened with clementine-git, then android-studio. Can I do something about it?

I am also facing the same problem. I am trying to install a package, and the installations aborts saying 'virtual memory exhausted'. The RAM is 2 GB and i have alloted 2 GB as swap. Things i have tried so far
-install using yaourt
-install using makepkg.
-change TMPDIR to HDD.
Even when i tried it without any window manager to start, limiting the RAM usage, the problem still persists. The only way is to allot an extra swap space, but that would mean that i will have to delete a partition, which is not a feasible solution. Is there anything else one could do. ?
if it helps,
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 20
file size (blocks, -f) unlimited
pending signals (-i) 16033
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 16033
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

[solved]Problem compiling alsa from source

I'm trying to install alsa-driver-1.0.18a from source because I need to compile it with snd-virtuoso. So I run "./configure --with-cards=virtuoso --with-sequencer=yes" then when I run "make" I get this at the end of it.
make -C /lib/modules/2.6.27-ARCH/build SUBDIRS=/usr/src/alsa/alsa-driver-1.0.18a CPP="gcc -E" CC="gcc" modules
make[1]: Entering directory `/usr/src/linux-2.6.27-ARCH'
CC [M] /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.o
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:282:1: warning: "GFP_DMA32" redefined
In file included from include/linux/kmod.h:22,
from include/linux/module.h:13,
from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:57,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/linux/gfp.h:105:1: warning: this is the location of the previous definition
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:831: error: static declaration of 'jiffies_to_msecs' follows non-static declaration
include/linux/jiffies.h:286: error: previous declaration of 'jiffies_to_msecs' was here
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:850: error: static declaration of 'msecs_to_jiffies' follows non-static declaration
include/linux/jiffies.h:288: error: previous declaration of 'msecs_to_jiffies' was here
In file included from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:948,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/linux/pci.h:627: error: expected identifier or '(' before numeric constant
In file included from include/asm/pci.h:4,
from include/linux/pci.h:989,
from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:948,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/linux/mm.h:261: error: conflicting types for 'snd_compat_vmalloc_to_page'
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:752: error: previous declaration of 'snd_compat_vmalloc_to_page' was here
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h: In function 'snd_pci_orig_save_state':
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:1197: error: too many arguments to function 'pci_save_state'
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h: In function 'snd_pci_orig_restore_state':
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:1201: error: too many arguments to function 'pci_restore_state'
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:1598:1: warning: "page_to_pfn" redefined
In file included from include/asm/page.h:196,
from include/asm/pda.h:8,
from include/asm/current.h:19,
from include/asm/processor.h:15,
from include/linux/prefetch.h:14,
from include/linux/list.h:6,
from include/linux/module.h:9,
from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:57,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/asm-generic/memory_model.h:78:1: warning: this is the location of the previous definition
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c: In function 'snd_compat_vmalloc_to_page':
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:44: error: implicit declaration of function 'VMALLOC_VMADDR'
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:49: error: incompatible type for argument 1 of 'pud_val'
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:50: error: implicit declaration of function 'pte_offset'
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:50: warning: assignment makes pointer from integer without a cast
make[3]: *** [/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.o] Error 1
make[2]: *** [/usr/src/alsa/alsa-driver-1.0.18a/acore] Error 2
make[1]: *** [_module_/usr/src/alsa/alsa-driver-1.0.18a] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.27-ARCH'
make: *** [compile] Error 2
edit: I tried compiling it on another computer and it was able too...not sure why mine wont. Although I do seem to remember possibly forgetting to uninstall it before making it again (after kernel upgrade)...I've tried multiple times to compile so far. Is there someway I can get a list of things to delete to manually remove all remnants of a previous install of alsa-driver?
Last edited by Gauvenator (2008-12-13 19:48:11)

Ok I ended up compiling the kernel from source for something else, so I tried compiling the alsa driver from source and it worked...maybe something was leftover in the previous kernel source directory that was causing problems.

How to build a package from sources

hi all,
Can someone please give some advices regarding making binaries from sources. I have found that a lot of programs on Snow Leopard can be also run in terminal and are in source form and need to be build. I have installed Xcode already and I have some programming skills as well such as using MinGW (GNU GCC) and VS EE on WinXP. I have never done anything in any UNIX-like system and I know sources need to be just compiled.
Please, give me a link if you have any =)
Regards.

I think you have done something in a UNIX-like system. MinGW is designed to provide a UNIX-line build system with GCC for Windows. Now, however, you have the real thing.
In most cases, all you need to do is extract the source tarbar into a directory (or checkout via CVS or SVN). Go into that directory with the Terminal and type "configure" and, if that goes well, "make", and if that looks good "sudo make install".

Compiling package from file messages

When compiling a package stored in a file a get the message:
Warning: execution completed with warning
PACKAGE BODY maintain_catalogs_pkg Compiled.
But when I open the package itself and compile it, the compiler gives errors in the package. So the two don't correspond.
Oracle DB: 10g r2
SQL Developer version: 1.5.0.53.38

An alternative is what you would have done for a SQL script creating a package in SQL*Plus (which is possibly why the current behaviour is intended) - that is to have the "SHOW ERRORS PACKAGE [BODY] <PACKAGE>" command after the creation of the package / package body.
Note that this command only works when run as a script command and not as a statement. Also, "SHOW ERRORS VIEW <VIEW>" will always report no errors, even if the same statement would report errors in SQL*Plus.
Presumably at some point, the SQL Developer team will revisit the "Awaiting Community Votes" requests like this one which have received a lot of votes with a high score.
theFurryOne

[SOLVED]Compiling a program from source (Tomoe)

I'm trying to compile Tomoe: http://tomoe.sourceforge.jp/cgi-bin/en/blog/index.rb
It is a handwriting recognition tool for East Asian languages. For those of you familiar with them, you'd know that there are some characters that are just so obscure you can't type them with your IME and the only way to input them is with a handwriting recognition program. (Browsing a unicode character map is only something a madman can do) MS has one built in their IME, but I've had to live by copying things from wiktionary up until now on Linux, and I think this program might be my saving grace if I can get it working.
I would want to make a PKGBUILD, but I really have no experiance with that kind of stuff at all, so I'm going to try to compile it from source the old fashioned way at least. I figured if it installs things into /usr/local/ by default it won't mess up with pacman too much.
However I'd need 3 packages. One for tomoe, another for tomoe-gtk, and another for scim-tomoe. And the 3rd depends on the 2nd which depends on the 1st. I installed tomoe fine with ./configure && make && make install, but when I try to install tomoe-gtk I get an error at ./configure:
checking for TOMOE... configure: error: Package requirements (tomoe >= 0.4.0) were not met:
No package 'tomoe' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables TOMOE_CFLAGS
and TOMOE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Of course I know that I installed tomoe, slocate gives me:
(It gave me more stuff too, but they are all in the build directory in my home so I excluded them.)
/usr/local/etc/tomoe
/usr/local/etc/tomoe/config
/usr/local/include/tomoe
/usr/local/include/tomoe/pytomoe-utils.h
/usr/local/include/tomoe/tomoe-candidate.h
/usr/local/include/tomoe/tomoe-char.h
/usr/local/include/tomoe/tomoe-config.h
/usr/local/include/tomoe/tomoe-context.h
/usr/local/include/tomoe/tomoe-dict.h
/usr/local/include/tomoe/tomoe-enum-types.h
/usr/local/include/tomoe/tomoe-module-impl.h
/usr/local/include/tomoe/tomoe-module.h
/usr/local/include/tomoe/tomoe-query.h
/usr/local/include/tomoe/tomoe-reading.h
/usr/local/include/tomoe/tomoe-recognizer.h
/usr/local/include/tomoe/tomoe-shelf.h
/usr/local/include/tomoe/tomoe-writing.h
/usr/local/include/tomoe/tomoe.h
/usr/local/lib/libtomoe.a
/usr/local/lib/libtomoe.la
/usr/local/lib/libtomoe.so
/usr/local/lib/libtomoe.so.0
/usr/local/lib/libtomoe.so.0.1.0
/usr/local/lib/tomoe
/usr/local/lib/pkgconfig/pytomoe.pc
/usr/local/lib/pkgconfig/tomoe.pc
/usr/local/lib/python2.6/site-packages/tomoe.a
/usr/local/lib/python2.6/site-packages/tomoe.la
/usr/local/lib/python2.6/site-packages/tomoe.so
/usr/local/lib/tomoe/module
/usr/local/lib/tomoe/module/dict
/usr/local/lib/tomoe/module/recognizer
/usr/local/lib/tomoe/module/dict/mysql.a
/usr/local/lib/tomoe/module/dict/mysql.la
/usr/local/lib/tomoe/module/dict/mysql.so
/usr/local/lib/tomoe/module/dict/unihan.a
/usr/local/lib/tomoe/module/dict/unihan.la
/usr/local/lib/tomoe/module/dict/unihan.so
/usr/local/lib/tomoe/module/dict/xml.a
/usr/local/lib/tomoe/module/dict/xml.la
/usr/local/lib/tomoe/module/dict/xml.so
/usr/local/lib/tomoe/module/recognizer/simple.a
/usr/local/lib/tomoe/module/recognizer/simple.la
/usr/local/lib/tomoe/module/recognizer/simple.so
/usr/local/share/tomoe
/usr/local/share/gtk-doc/html/tomoe
/usr/local/share/gtk-doc/html/tomoe/TomoeCandidate.html
/usr/local/share/gtk-doc/html/tomoe/TomoeChar.html
/usr/local/share/gtk-doc/html/tomoe/TomoeConfig.html
/usr/local/share/gtk-doc/html/tomoe/TomoeContext.html
/usr/local/share/gtk-doc/html/tomoe/TomoeDict.html
/usr/local/share/gtk-doc/html/tomoe/TomoeQuery.html
/usr/local/share/gtk-doc/html/tomoe/TomoeReading.html
/usr/local/share/gtk-doc/html/tomoe/TomoeRecognizer.html
/usr/local/share/gtk-doc/html/tomoe/TomoeShelf.html
/usr/local/share/gtk-doc/html/tomoe/TomoeWriting.html
/usr/local/share/gtk-doc/html/tomoe/home.png
/usr/local/share/gtk-doc/html/tomoe/index.html
/usr/local/share/gtk-doc/html/tomoe/index.sgml
/usr/local/share/gtk-doc/html/tomoe/ix01.html
/usr/local/share/gtk-doc/html/tomoe/left.png
/usr/local/share/gtk-doc/html/tomoe/right.png
/usr/local/share/gtk-doc/html/tomoe/style.css
/usr/local/share/gtk-doc/html/tomoe/tomoe-tomoe.html
/usr/local/share/gtk-doc/html/tomoe/tomoe.devhelp
/usr/local/share/gtk-doc/html/tomoe/tomoe.devhelp2
/usr/local/share/gtk-doc/html/tomoe/tomoe.html
/usr/local/share/gtk-doc/html/tomoe/up.png
/usr/local/share/locale/ja/LC_MESSAGES/tomoe.mo
/usr/local/share/tomoe/dict
/usr/local/share/tomoe/dict.dtd
/usr/local/share/tomoe/python
/usr/local/share/tomoe/recognizer
/usr/local/share/tomoe/xml2est.rb
/usr/local/share/tomoe/python/tomoe.defs
/usr/local/share/tomoe/recognizer/handwriting-ja.xml
/usr/local/share/tomoe/recognizer/handwriting-zh_CN.xml
I've tried:
export PKG_CONFIG_PATH=/usr/local/lib/tomoe:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=/usr/local/lib:$PKG_CONFIG_PATH
And neither of those seemed to work so I then set TOMOE_CFLAGS and TOMOE_LIBS and it indeed avoided the need to call pkg-config and the configure script went on, but I got the same problem for gucharmap, which I tried installing with pacman and then starting a new session, but it still didn't work so I had to set the environment variables to skip it and then the configure script finished, but make not so surprisingly failed.
So what should I do to get this to compile?
Last edited by sokuban (2008-11-24 02:48:46)

Zoulnix wrote:
Hello there, sokuban... just wanted to tell you that i have uploaded
scim-tomoe, tomoe, tomoe-gtk and uim-tomoe-gtk PKGBUILD's to the AUR.
... would be good if someone could test the pkgbuilds
out to see so everything works as it should.
tomoe-gtk had to be compiled without gucharmap. from what i could see the tomoe-gtk is not compatible with the latest version of gucharmap...
Thanks! The tomoe packages installs and works perfectly.
But now I've got another little problem. For some strange reason they decided that it would only load a dictionary when the locale is set to Chinese or Japanese. My computer currently runs on a ms_MY.utf-8 locale and while I wouldn't really mind putting it to ja_JP.utf-8 I'd prefer it if there is a way I can make it so that tomoe is always run with a Japanese locale no matter what locale the rest of my system is because I often randomly change it.
While I can directly run:
$ LANG=ja_JP.UTF-8 scim-tomoe
from a terminal and the dictionaries are loaded fine, I'd end up only being able to write in the terminal itself which is pretty useless. Right clicking on the scim icon and selecting handwriting recognition will give me the ms_MY version which doesn't have any dictionaries loaded.
Anyone know a way to do it?
EDIT: So I tried setting my whole locale to Japanese. Only problem is, Thunar has a bug with Japanese. Maybe its because the Japanese name for filesystem is too long, but the sidebar is stuck out too much and cannot be pushed in. Also since it is so long my filesystem icon on my desktop can't display its whole name, I wouldn't really call that a bug, but it isn't pretty to look at.
And I just noticed but xfce terminal fonts are messed up too. I'm too lazy to fix all this so I'm going back to English now. It would probbably be much easier to find a way to always run only this program with a Japanese locale than fix all the problems I'm getting with the whole system in a Japanese locale.
EDIT2: Solved by running scim itself in ja_JP.UTF-8 (why didn't I think of this earlier?).
Last edited by sokuban (2008-11-24 02:49:24)

Creating a package from Github source and install instructions

hello
I've read that the correct way to install things is to make a package from source if it's not in a repository.
Install instructions: https://github.com/yaxu/Tidal/blob/mast … l-linux.md
I copied /usr/share/pacman/PKGBUILD.proto into the source directory but was having difficulty getting it to work.
I've actually just done make clean; make like it says in the instructions since I was thinking it's not installing anything (since it's not "make install").
It seems to have changed a few things in /usr/local/include...
I guess I'd like help creating the package,
and possibly undoing what I did with make clean; make.
Thanks

Tidal itself does not have a Makefile (except for its docs), so I suppose you’re talking about Dirt’s makefile. From what I can see it shouldn’t touch /usr/local/include or anything outside the build directory as long as you don’t run “make install”.
Arch doesn’t put anything in /usr/local anyway, as far as I know, so you can probably easily see if Tidal or Dirt put something in there…
It might be easier for you to first build Dirt and Tidal manually and then make a PKGBUILD once you know the different steps required.

Update modules with compiling kernel from soure issue.

Compiling kernel from abs or aur take me much time, so i decide compile kernel from source, compilation and installation successfully but make initial RAM disk doesn't update full modules (crypto,lvm...). I specified -c option to /etc/mkinitcpio.conf but the result is the sam, non-autodectec doesn't help too. When i look into /lib/modules directory, 3.6.6-1-ARCH folder contain "kernel" folder which has a lot of things (arch, crypto, net..) and i think this is my extra modules were declared in HOOK array's mkinitcpio.conf. The another one only contain net folder so i can't boot into this kernel without having loaded others.
any suggestion for this problem? tks for reply.

am sorry, i re-tried with HOOK array without autodectect and it can load modules but there are two error:
==> ERROR: module not found: `dm-crypt`
==> ERROR: modules not found: `dm-snapshot`
ok i will try to load these modules by manually.
EDIT: i tried to load dm-mod, dm-crypt, dm-snapshot but it isn't helpful. Errors still remain. any suggestion?
Last edited by angelfalls (2012-11-12 23:33:53)

Compiling JDK 1.4.2 from source, under win32

Hi,
Here is how I compiled JDK 1.4.2 from source-code under win32. I hope this helps the many others who are interested in doing the same.
1) Download the sources from here: http://wwws.sun.com/software/communitysource/j2se/java2/download.html
Be sure to download all packages (SCSL source, SCSL binaries, mozilla binaries)
2) Download gnu make from here: http://ftp.gnu.org/pub/gnu/make/
3) Download Info-zip "zip" and "unzip" packages: http://www.info-zip.org/pub/infozip/UnZip.html and http://www.info-zip.org/pub/infozip/Zip.html
4) Request and evaluation copy of MKS Toolkit: http://www.mkssoftware.com/eval/
The key point here is that MKS Toolkit is a commercial product and even once you request an evaluation copy, it'll take a day or two for one of their salespeople to contact and harass you. Tell him whatever you must to get an evaluation copy out of him ("I might buy a copy in 3 months, honest!")... I personally wish Sun would move away from this commercial product and replace it with cygwin or something. It was very annoying getting past this stage.
5) Download the DirectX 9.0 SDK from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=124552ff-8363-47fd-8f3b-36c226e04c85&displaylang=en
Sun actually requires DirectX 7.0 SDK but I couldn't find a copy anywhere so we have no choice but use a newer copy. This is another issue Sun should really address.
6) Install DirectX SDK, MKS Toolkit, Info-zip zip and unzip
7) Unpack gnu make into a directory and build it using the special steps for the MKS Toolkit shell. If you're trying to build make 3.80 be sure to fix this bug before you proceed or else it won't build: https://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=1687
8) Set your build environment variables. Here are my personal settings:
call "C:\Program Files\Microsoft Visual Studio\VC98\Bin\vcvars32.bat"
set ALT_UNIXCOMMAND_PATH=c:\mksnt
set ALT_MSVCRT_DLL_PATH=c:\windows\system32
set ALT_BOOTDIR=c:\j2sdk1.4.2_04
set ALT_DEVTOOLS_PATH=c:\j2sdk1.4.2_04\source\utils
set path=C:\make-3.80\WinRel;%path%
set include=%include%;c:\program files\microsoft sdk\include
set JAVA_HOME=
9) You must build against Visual C++ 6.0 (Visual C++ .NET won't work because its missing non-standard header files used by Sun, such as iostream.h)
10) "cd <jdk source dir>\control\make"
11) Edit <jdk source dir>\j2me\make\common\Sanity.gmk line 1135. Replace:
ifeq ($(PLATFORM), windows)
with
ifeq ($(PLATFORM), windows_skip)
This will cause the build process to ignore the fact that you have DirectX 9.0 when it requires version 7.0
12) Start the build process: "make scsl"
13) If the build process dies because you have a different service-pack of Visual C++ 6.0 than it expects, edit <jdk source dir>\j2me\make\common\Sanity.gmk lines 71-72 and modify the expected version numbers to the ones you have.
14) If you see a "'c:\program' not found" error while compiling. Be sure that the paths set by VCVARS32.BAT use short-names not long-names, because make gets confused by paths with spaces.
15) If you see an error "No rule to make target `/usr/src/j2sdk-1_4_2-src-scsl/control/build/linux-i586/lib/fonts/LucidaTypewriterRegular.ttf'" it means you forgot to extract the "SCSL binaries" package into the source-code directory
I will post solutions to further compiler errors as I encounter them, I encourage you to do the same.

hey
i m trying to install JDK 1.5 from source under win XP
dev-sanity pass so i suppose i have all installed correctly
the problem is when i run the command "make scsl" to compile all
i got an error which is into "link.exe" at the begin of the compilation :
cd generated && NMAKE /NOLOGO /f C:\cygwin\Sources\hotspot\build\windows
\makefiles\generated.make DIR=.\generated BUILD_FLAVOR=product
link.exe kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib ad
vapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib Wsock32.lib winmm.lib /n
ologo /machine:I386 /opt:REF /opt:ICF,8 /map /debug /subsystem:console /out:adl
c.exe main.obj adlparse.obj archDesc.obj arena.obj dfa.obj dict2.obj filebuff.ob
j forms.obj formsopt.obj formssel.obj opcodes.obj output_c.obj output_h.obj
link: too many arguments
Try `link --help' for more information.
NMAKE : fatal error U1077: 'link.exe' : return code '0x1'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"c:\Program Files\Microsoft Visual Studio\VC98\bin\n
make.exe"' : return code '0x2'
Stop.
make[3]: *** [generic_build2] Error 2
make[3]: Leaving directory `/Sources/hotspot/make'
make[2]: *** [product] Error 2
make[2]: Leaving directory `/Sources/hotspot/make'
make[1]: *** [hotspot-build] Error 2
make[1]: Leaving directory `/Sources/control/make'
make: *** [scsl-build] Error 2
i installed visual studio professional 6 sp3 as required ine the "build-windows-i586.html" file ! is the file link.exe incorrect in the pack 3??
Thanks

[Solved] Apps compiled from source never work and a security question

Gentlemen,
I'm a Linux noob but in spite of that I managed to install Archlinux thanks to a fine How To Wiki.
1. I have a question regarding compiling from source in Arch - does it differ from other linuxdistros?
With other distros I normally install in /usr/local and that has worked flawless.
Take Pacman for instance: although I can see there is this Opera app available in the repo (via arch's home page -> search package), the 'pacman -S opera' tells me the app doesn't exist.
I've tried to download and install it from source following Opera's own 'how to' but the app fails to start, after a successful installation.
Same goes with other apps such as f-prot antivirus.
Did I miss something important here?
2. I installed Arch over FTP. How safe is it, considering I'm not behind a router and the iptables/firestarter was only installed after xfce4 was installed. What about open ports and such? I know there aren't many services enabled/listening but I noticed couple of daemons such as portmap being active during the installation process.
Thanks
Last edited by new2arch (2008-02-25 16:12:31)

kumico wrote:
you can add /usr/local to the path in /etc/profile to make it global or in your ~/.bashrc or ~/.bash_profile to make it available to your user session.
a pkgbuild is pretty simple once you get used to it,
you may be put off by packaging standards, you can ignore them, they are only for people intending to share
with other via the AUR for example.
you can copy one of the existign ones, either the prototypes or jsut anyone from the aur,
then change stuff you fidn necessary, like pkgname, pkgver, etc.
and add the same build commands you'd use otherwise to the build()
and usualy for a make install, just add DESTDIR=$startdir/pkg etc.,... just practice you'll get the hang of it very quickly
Hi Kumico, thanks for the tip.
Or I could try using Arch's default paths as long as the applications don't mind. But it's nice to have an alternative solution should any trouble arise.
Regarding pkgbuild, I'll probably start to use it when I feel more comfy with the Arch environment itself.
Using the terminal to perform...well, just about everything, rather than having a nice gui isn't actually bad, but there sure is a transition for a newbie to adapt to.

Trying to compile from source, several cpp files, but not a developer

First of, I'd like to start with this- I'm not a developer (only do BASH scripting and Python). I've done some basic packages in AUR and am working on a new one. I have the source, mainly a bunch of cpp files. I'm used to seeing a configure or autogen script, however the source I have does not provide these. I can do a PKGBUILD that works with the .deb file package, but I'd like to compile from source for AUR. I've tried looking at other C++ packages in AUR but I can't seem to find one that doesn't have a configure script with the source files. Google also did not help much.
Any advice or pointers to resources would be greatly appreciated. I've also got a message out to the developer about it- the more I can learn on this the better. The source isn't on the site yet, but the application is fred, located at:
https://www.pinguin.lu/
Thanks in advance!

Sorry I can't help. A list of filenames or at least file types could be useful. But I just checked my email, downloaded whatever that was and found that it was not a proper tarball and could not be extracted.
Edit: I must be really bored tonight. I passed whatever that was (the not-quite-tarball) through gnu strings and less, and sure enough I was able to scroll through most of the code. Along the way I saw a Makefile hack with a initial line "#!/usr/bin/make -f" which would run make and treat the contents of that file as a Makefile. Reading it in this way I could not determine what the filename was, but it may have ended in ".sh" or it might have been called "install". In any case you can do `grep '/usr/bin/make' * and run whichever file matches.
I'd also ask the developer to consider dropping that hash-bang invocation and just properly naming that file "Makefile".
edit2: there is also a reference to the ".pro" file which is used by qmake (I think) like a Makefile.
edit3: I just verified on a few properly made tarballs: `strings <name>.tar.gz | less` does not show anything remotely readable in any other tarballs, but run on yours I can read *all* of the code directly. I'm not sure how you made that tarball, but you may want to look into that.
Last edited by Trilby (2012-07-04 00:33:20)

Compiling Packages from Source

Similar Messages

Maybe you are looking for