07-04-2012, 11:20 AM | #16 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
True there may be exceptions
THIS ENTIRE PAGE IS ABOUT GETTING X-COMILERS TO WORK (OR NOT) GO TO PAGE 3 FOR MORE AUDIO TIPS
I think he's referring to the bulk rather than the specific. Last edited by twobob; 07-10-2012 at 09:21 AM. Reason: ADDED TOPPOST |
07-04-2012, 11:46 AM | #17 | |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
Quote:
Sigh. May just build a 32 build OS and get on with the job. |
|
07-04-2012, 12:02 PM | #18 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Finally gave up and added a 32-bit system to the clutter of installed "stuff". Nice that Linux makes "multi-boot" so easy. There should be a 32-bit Slackware out there. Things were getting confusing here, so I finally added in different "default" window managers to the different systems so I would be reminded of what I was using at any moment. |
|
07-04-2012, 06:33 PM | #19 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
still not having fun :)
EDIT: THIS SECTION IS ABOUT GETTING KDEVELOP CROSS COMPILING
WHICH NEVER WORKED: I GOT NEW TOOLS FROM THE KEK PROJECT FEEL FREE TO SKIP OVER THESE POSTS TO THE SOUND INFO I really am at a loss how in to include my cross-compiled alsa-libs to the CodeSourcery Gcc. Spoiler:
seems to cover all eventualities for actually finding the libs. perhaps I need to run libran or something? Meh. Any clues to this noob would be great. Of course this could all simply be to do with the fact that the vast majority of stuff just does not want to "work" out of the box on my current OS config. Sigh Anyways if someone could just confirm that I am indeed referencing the -lasound and it's location(s), correctly that would be great. Googling didn't help as I seem to get conflicting answers and nothing specific to my issue. many thanks. EDIT: I NEVER GOT THIS WORKING UNDER KDEVELOP. I GOT NEW TOOLS FROM THE KEK PROJECT RESULT: Spoiler:
Which doesn't really tell me a lot; other than guesses: incompatible library revisions? object not found? Paths incorrectly specified ? I'm at a loss. which is a shame as I am at a place where I can now deliver random bytes to the dsp via alsa on my local installation and would very much like to get it to compile to check if it works on the kindle. It's basically just an alsa-test configured correctly for the kindle. Any takers on either a) helping me to get the file to compile. or b) compiling it for me would be great. I don't suppose trying the -lasound option in tcc would hurt if anyone can direct me how to get the libraries from tcc/includes/sound included that would also be great Code:
[root@kindle tcc]# tccmake -lasound -B/mnt/us/tcc -B/mnt/us/tcc/include/sound -B/mnt/us/tcc/include/ ./salsa.c doesn't appear to cut it... In file included from ./salsa.c:19: ./include/sound/asoundlib.h:42: include file 'asoundef.h' not found apologies for the sprawling nature of the post. Last edited by twobob; 07-10-2012 at 07:34 AM. Reason: legibility - code length - added spoilers to hide lengthy rubbish |
07-04-2012, 06:48 PM | #20 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Tells what is wrong.
The compiler can't find the header files, at least in the big code post. One or two questions: Did you build the "missing" library yourself? If so; What did you use for the --prefix= path to configure? The proper path so that "make install" would install **both** the library and the header files to the Cs toolchain location? Did you include any DESTDIR= environment variable while doing "make install" Duh,,, Too many ways this might have gotten to this state to give a winning answer on the first reply. |
07-04-2012, 06:57 PM | #21 | |||
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
teething troubles
EDIT: THIS SECTION IS ABOUT GETTING KDEVELOP CROSS COMPILING
WHICH NEVER WORKED: I GOT NEW TOOLS FROM THE KEK PROJECT FEEL FREE TO SKIP OVER THESE POSTS TO THE SOUND INFO Quote:
Quote:
Quote:
WHAT HAPPENED: Spoiler:
Thanks for some feedback. at least I could answer the questions coherently so I do I have some understanding of the process. Even if none if the answers. other questions gratefully accepted. erm. not at the harm of other projects please though. thanks I am certain this will be user error Last edited by twobob; 07-10-2012 at 07:33 AM. Reason: added output as requested. - added spoilers to hide lengthy rubbish |
|||
07-04-2012, 07:00 PM | #22 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Add the option -v to your gcc options, capture the output, check what the include and library search paths are that the compiler is trying to use.
Pick any small file (hello.c ?) otherwise you'll be overwhelmed by the output. My thoughts here are . . . That compiler is location independent, so it must have a sysroot= defined in its configuration and that may be messing with the "normal" (what a person expects) search order. Last edited by knc1; 07-04-2012 at 07:06 PM. |
07-04-2012, 07:25 PM | #23 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
EDIT: I NEVER GOT THIS WORKING UNDER KDEVELOP.
I GOT NEW TOOLS FROM THE KEK PROJECT Spoiler:
Code:
--prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/nsidwell/arm/linux/install/arm-none-linux-gnueabi/libc Last edited by twobob; 07-10-2012 at 07:28 AM. Reason: Top posted conclusion - added excerpt -added KEK reference |
07-04-2012, 07:34 PM | #24 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
perhaps I mis-understood where to install the libs?
Sigh I'm an audio guy. who does code. not the other way round. sadly. but I'm trying. probably the patience of saints Last edited by twobob; 07-04-2012 at 07:39 PM. Reason: added why I'm so rubbsh |
07-04-2012, 07:44 PM | #25 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Oh, wait, the admin is yourself. Well, go yell at the image in the mirror. You might not be the only one - There have been about 80 downloads of the archives, but only 7 downloads of the "getting started" (directions) guide. |
|
07-04-2012, 07:50 PM | #26 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@twobob: Not sure what happened after #19, but here's what it's telling you:
You're trying to link against a library that depends on other libraries. Except you're linking statically, and there's no dependency tracking for static libraries [if you forget libtool and its horrible .la files], so you *need* to have them passed to your compiler/linker *in the right order*. Let's say hello.c depends on libasound. libasound depends on libm, libdl, libpthread. You'll need to do something like gcc -c hello.c -o hello -lasound -lpthread -ldl -lm (Keep the *in the right order* thing in mind, AFAIR, libdl/lm/libpthread are more or less standalone, usually, but let's say libm depends on libdl, you'd have to do -lm -ldl, not the other way around). It's explained in more details somewhere in the GCC manual, but it can be a bit tricky. (Usually, autotools (or any other proper, real buildsystem) takes care of it, but for small Makefile only projects, you may need to get your hands dirty). (ELF) Static linking is *FUN* EDIT: And, yeah, of course you do need to set the proper searchpaths for headers & libs, using the proper env vars: -I/custom/path/include in CPPFLAGS for the headers -L/custom/path/lib in LDFLAGS for the libs (I've never had to play with -B) (You may need to just squish everything into CFLAGS for some broken buildsystems) EDIT²: Granted, knowing more or less to which library the undefined symbols belong to helps a bit. If you're not sure, a man/man 3 on the symbol name usually helps . From what I gather from your logs, you need at least libm, librt, libdl and libpthread EDIT^3: I saw a few mentions of configure/prefix. When using autotools, the prefix you pass is more or less the destination directory (it'll in fact be used to set DESTDIR). On a native system, it's usually /usr or /usr/local or /opt. When crosscompiling, you'll probably want to set it to a staging sysroot to keep things clean. Don't forget to pass the right toolchain triplet (apparently arm-none-linux-gnueabi in your case) to --host to use the proper toolchain . Last edited by NiLuJe; 07-04-2012 at 08:09 PM. |
07-04-2012, 08:17 PM | #27 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
The above "start-group and end-group" is probably not the proper option names, just what they do in English. You'll need to look the proper option names up. Also, don't forget the trailing '-' on the arm-none-linux-gnueabi when setting the CROSS_COMPILE (or whatever the proper name is) variable. Sorry for being so inexact, its been an 18 hour work day here. |
|
07-04-2012, 08:27 PM | #28 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Yep, although not every package out there obey the CROSS_COMPILE env var (busybox & openssl do, among others), but when they do, and that's usually because they have a custom buildsystem, they expect the extra dash, unlike autotools --host, true .
|
07-05-2012, 09:36 AM | #29 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
Thanks boys. I still can't get Kdevelop to swallow it, but I took another tack and simply downloaded the Kek provided version of Eclipse and configured it all again.
Compiles not a problem on the host. Further tests ongoing. Yay for Kek. |
07-05-2012, 09:47 AM | #30 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
That is what my intent is - one-stop-shopping for development stuff that "just works". Well, as close to: "just works" as one can reasonable expect in the world of complex, cross-system, program development. The last K does mean "Kit" - I.E: user must supply the tweaks. |
|
Tags |
stupid root mistakes |
Thread Tools | Search this Thread |
|