From: Chuck R. <shi...@ro...> - 2007-12-20 03:59:09
|
On my intel ubuntu 7.04 linux system I'm trying to build ffmpeg for a connex, build 1161 (arm-linux-gcc), but it comes up with 3 undefined references: undefined reference to `roundf' undefined reference to `llrint' undefined reference to `lrint' collect2: ld returned 1 exit status make: *** [ffmpeg_g] Error 1 The linux man page says these things are defined in math.h, but it also says to use "-std=c99" and "-lm" on the compile line. How do I add -std=c99 onto my ffmpeg ./configure line, or is that not the problem? ./configure --cross-compile --cc=arm-linux=gcc --arch=arm --extra- cflags=-lm Thanks, Chuck |
From: Chuck R. <shi...@ro...> - 2007-12-20 00:52:13
|
On my intel ubuntu 7.04 linux system I'm trying to build ffmpeg for a connex, build 1161 (arm-linux-gcc), but it comes up with 3 undefined references: undefined reference to `roundf' undefined reference to `llrint' undefined reference to `lrint' collect2: ld returned 1 exit status make: *** [ffmpeg_g] Error 1 The linux man page says these things are defined in math.h, but it also says to use "-std=c99" and "-lm" on the compile line. How do I add -std=c99 onto my ffmpeg ./configure line, or is that not the problem? ./configure --cross-compile --cc=arm-linux=gcc --arch=arm --extra- cflags=-lm Thanks, Chuck |
From: David C. <d.c...@ie...> - 2007-12-20 17:14:55
|
Dear Chuck Randall, > From: Chuck Randall > Date: Wed, 19 Dec 2007 ... > On my intel ubuntu 7.04 linux system I'm trying to build ffmpeg for a > connex, build 1161 (arm-linux-gcc) ... > also says to use "-std=c99" and "-lm" on the compile line. How do I > add -std=c99 onto my ffmpeg ./configure line, or is that not the > problem? > > ./configure --cross-compile --cc=arm-linux=gcc --arch=arm --extra- > cflags=-lm I think you want ./configure --cross-compile --cc=arm-linux=gcc --arch=arm --extra-cflags='-lm -std=c99' (Or was it supposed to be double-quotes?) -- David Cary |
From: Chuck R. <shi...@ro...> - 2007-12-21 02:51:53
|
Thanks, David, that seems to have me gotten past that hurdle. And now, on to another one! Where or how does one enable "asm" variables in a gumstix build? flacenc.c: In function `find_optimal_param': flacenc.c:465: error: `asm' undeclared (first use in this function) make[1]: *** [flacenc.o] Error 1 make[1]: Leaving directory `/usr/build_1161/ffmpeg-export-2007-12-06/ libavcodec' make: *** [lib] Error 2 Here's the culprit: #elif defined(ARCH_ARMV4L) # define FASTDIV(a,b) \ ({\ int ret,dmy;\ asm volatile(\ "umull %1, %0, %2, %3"\ :"=&r"(ret),"=&r"(dmy)\ :"r"(a),"r"(ff_inverse[b])\ );\ ret;\ }) I'm compiling ffmpeg with -std=c99. Shouldn't C99 "know" about asm variables? Thanks! Chuck On Dec 20, 2007, at 9:14 AM, David Cary wrote: > Dear Chuck Randall, > >> From: Chuck Randall >> Date: Wed, 19 Dec 2007 > ... >> On my intel ubuntu 7.04 linux system I'm trying to build ffmpeg for a >> connex, build 1161 (arm-linux-gcc) > ... >> also says to use "-std=c99" and "-lm" on the compile line. How do I >> add -std=c99 onto my ffmpeg ./configure line, or is that not the >> problem? >> >> ./configure --cross-compile --cc=arm-linux=gcc --arch=arm --extra- >> cflags=-lm > > I think you want > > ./configure --cross-compile --cc=arm-linux=gcc --arch=arm > --extra-cflags='-lm -std=c99' > > (Or was it supposed to be double-quotes?) > > -- > David Cary > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2007-12-21 05:08:28
|
Hi Chuck, On Dec 20, 2007 6:51 PM, Chuck Randall <shi...@ro...> wrote: > Thanks, David, that seems to have me gotten past that hurdle. And > now, on to another one! > > Where or how does one enable "asm" variables in a gumstix build? > > I'm compiling ffmpeg with -std=c99. Shouldn't C99 "know" about asm > variables? No. asm is a gnu specific extension and not part of C99. __asm__ is valid all of the time. asm is only valid when gnu extensions are enabled. You can used --std=gnu99 to get C99 + gnu extensions. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chuck R. <shi...@ro...> - 2007-12-21 23:36:54
|
Hi Dave, Thanks for pointing me to --std=gnu99. This changes the scenario a bit: ffmpeg.c:118: error: initializer element is not constant Here is ffmpeg.c:118: static AVRational frame_rate = (AVRational) {25,1}; And here is the definition of AVRational, rational.h:33: /** * Rational number num/den. */ typedef struct AVRational{ int num; ///< numerator int den; ///< denominator } AVRational; I don't understand the error. Aren't 25 and 1 constants? Or is it complaining that AVRational is a struct? Chuck On Dec 20, 2007, at 9:08 PM, Dave Hylands wrote: > Hi Chuck, > > On Dec 20, 2007 6:51 PM, Chuck Randall <shi...@ro...> > wrote: >> Thanks, David, that seems to have me gotten past that hurdle. And >> now, on to another one! >> >> Where or how does one enable "asm" variables in a gumstix build? >> >> I'm compiling ffmpeg with -std=c99. Shouldn't C99 "know" about asm >> variables? > > No. asm is a gnu specific extension and not part of C99. > > __asm__ is valid all of the time. > asm is only valid when gnu extensions are enabled. > > You can use --std=gnu99 to get C99 + gnu extensions. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > |
From: Dave H. <dhy...@gm...> - 2007-12-22 04:49:24
|
Hi Chuck, > Thanks for pointing me to --std=gnu99. > This changes the scenario a bit: > > ffmpeg.c:118: error: initializer element is not constant > > Here is ffmpeg.c:118: > > static AVRational frame_rate = (AVRational) {25,1}; Under C99, the cast makes the struct non-const. If you do this instead: static AVRational frame_rate = {25,1}; then it will compile cleanly under C99. If you don't provide a --std= then it compiles cleanly as presented. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chuck R. <shi...@ro...> - 2007-12-28 03:56:23
|
Hi Dave, I made the casting change you suggested, but ffmpeg is being difficult. If I compile with --std=gnu99 (or no --std=) and link against -lm I get: undefined reference to `roundf' undefined reference to `llrint' undefined reference to `lrint' collect2: ld returned 1 exit status make: *** [ffmpeg_g] Error 1 If I compile with --std=c99 (to resolve the symbols), I get: flacenc.c: In function `find_optimal_param': flacenc.c:465: error: `asm' undeclared (first use in this function) make[1]: *** [flacenc.o] Error 1 This is same "asm volatile" issue of a few emails back. So --std=c99 is a dead end. The first way (no --std=) seems to be getting all the way to the linking of ffmpeg, but doesn't resolve those 3 symbols. I have libm-0.9.28.so (94912 bytes) and libm.a (229314 bytes) in my gumstix buildroot (v. 1161). nm shows that the gumstix libm.a has roundf.o in it, but no llrint or lrint, just lrintf.o. (I don't know how to check the contents of the .so.) In comparison, the ubuntu Linux version of / usr/lib/libm.a has all 3 symbols in it, but of course I can't link against that. Am I missing a required library, or does ffmpeg require a different buildroot or version of libm? Hopefully I'm just building this thing wrong. My gumstix is a connex 400MHz with stock buildroot 1161. Thanks for any suggestions. Chuck On Dec 21, 2007, at 8:49 PM, Dave Hylands wrote: > Hi Chuck, > >> Thanks for pointing me to --std=gnu99. >> This changes the scenario a bit: >> >> ffmpeg.c:118: error: initializer element is not constant >> >> Here is ffmpeg.c:118: >> >> static AVRational frame_rate = (AVRational) {25,1}; > > Under C99, the cast makes the struct non-const. If you do this > instead: > > static AVRational frame_rate = {25,1}; > > then it will compile cleanly under C99. > > If you don't provide a --std= then it compiles cleanly as presented. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2007-12-28 07:59:33
|
Hi Chuck, On Dec 27, 2007 7:56 PM, Chuck Randall <shi...@ro...> wrote: > Hi Dave, > > I made the casting change you suggested, but ffmpeg is being difficult. > > If I compile with --std=gnu99 (or no --std=) and link against -lm I get: > undefined reference to `roundf' > undefined reference to `llrint' > undefined reference to `lrint' > collect2: ld returned 1 exit status > make: *** [ffmpeg_g] Error 1 That's interesting. All 3 symbols exist in my 1574 revision of libm.a roundf, llrint and lrint are all GCC builtins as well. Are you sure that the -lm is actually making it to the linker command line? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chuck R. <shi...@ro...> - 2007-12-28 18:36:05
|
Hi Dave, Yes, the -lm is on the ld command line -- by default, even if I don't specify it in the ./configure (see log below). If buildroot 1574 libm.a contains these 3 symbols, then I guess this means that buildroot 1161 is too old to support ffmpeg? The exact configuration I'm using is a connex 400MHz with a netCF card and a console-st serial card. If you can recommend a buildroot that contains these libm functions and will support this 3-card configuration (connex+RJ45/CF+serial), then I'll try "reflashing" my gumstix (pray I don't brick it). Or will I need to get a verdex for this? Bottom line is I just need to downscale video resolution from a webcam and send a reduced version of the frames out over the ethernet to another system. If there's another way than ffmpeg, I'll try it. Chuck arm-linux-gcc \ -L"/usr/build_1161/ffmpeg-export-2007-12-06"/libavdevice \ -L"/usr/build_1161/ffmpeg-export-2007-12-06"/libavformat \ -L"/usr/build_1161/ffmpeg-export-2007-12-06"/libavcodec \ -L"/usr/build_1161/ffmpeg-export-2007-12-06"/libavutil \ -rdynamic -export-dynamic -Wl,--warn-common -Wl,--as-needed \ -Wl,-rpath-link,"/usr/build_1161/ffmpeg-export-2007-12-06"/ libavcodec \ -Wl,-rpath-link,"/usr/build_1161/ffmpeg-export-2007-12-06"/ libavformat \ -Wl,-rpath-link,"/usr/build_1161/ffmpeg-export-2007-12-06"/ libavutil \ -Wl,-Bsymbolic -g -o ffmpeg_g ffmpeg.o cmdutils.o \ -lavdevice -lavformat -lavcodec -lavutil -lz -lm -ldl -ldl libavcodec/libavcodec.a(atrac3.o): In function `av_clip_int16': libavutil/common.h:201: undefined reference to `roundf' libavcodec/libavcodec.a(atrac3.o): In function `atrac3_decode_frame': libavutil/common.h:201: undefined reference to `roundf' libavcodec/libavcodec.a(atrac3.o): In function `av_clip_int16': libavutil/common.h:201: undefined reference to `roundf' libavcodec/libavcodec.a(mpegaudiodec.o): In function `decode_init': libavcodec/mpegaudiodec.c:359: undefined reference to `llrint' libavcodec/mpegaudiodec.c:361: undefined reference to `llrint' libavcodec/libavcodec.a(wmaenc.o): In function `encode_block': libavcodec/wmaenc.c:207: undefined reference to `lrint' collect2: ld returned 1 exit status make: *** [ffmpeg_g] Error 1 On Dec 27, 2007, at 11:59 PM, Dave Hylands wrote: > Hi Chuck, > > On Dec 27, 2007 7:56 PM, Chuck Randall <shi...@ro...> > wrote: >> Hi Dave, >> >> I made the casting change you suggested, but ffmpeg is being >> difficult. >> >> If I compile with --std=gnu99 (or no --std=) and link against -lm >> I get: >> undefined reference to `roundf' >> undefined reference to `llrint' >> undefined reference to `lrint' >> collect2: ld returned 1 exit status >> make: *** [ffmpeg_g] Error 1 > > That's interesting. All 3 symbols exist in my 1574 revision of libm.a > > roundf, llrint and lrint are all GCC builtins as well. > > Are you sure that the -lm is actually making it to the linker > command line? > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > |
From: Dave H. <dhy...@gm...> - 2007-12-28 21:24:40
|
Hi Chuck, On Dec 28, 2007 10:36 AM, Chuck Randall <shi...@ro...> wrote: > Hi Dave, > > Yes, the -lm is on the ld command line -- by default, even if I don't > specify it in the ./configure (see log below). > > If buildroot 1574 libm.a contains these 3 symbols, then I guess this > means that buildroot 1161 is too old to support ffmpeg? The exact > configuration I'm using is a connex 400MHz with a netCF card and a > console-st serial card. If you can recommend a buildroot that > contains these libm functions and will support this 3-card > configuration (connex+RJ45/CF+serial), then I'll try "reflashing" my > gumstix (pray I don't brick it). Or will I need to get a verdex for > this? > > Bottom line is I just need to downscale video resolution from a > webcam and send a reduced version of the frames out over the ethernet > to another system. If there's another way than ffmpeg, I'll try it. I think that the latest buildroot will work for you. Is your connex an XM? You can always try building it, just to see if you can get things to build. The latest buildroot normally expects the newer 3 partition scheme, which needs u-boot to be updated. If you want, you can test out the new image with the new u-boot without actually changing your existing u-boot. Let me know if you want to go this route, and I can write down some instructions. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chuck R. <shi...@ro...> - 2007-12-28 22:54:25
|
Hi Dave, > I think that the latest buildroot will work for you. Is your connex > an XM? Yes, it's a connex 400xm. No bluetooth. > You can always try building it, just to see if you can get things > to build. That's a good idea. No rush to do the hard stuff until it's needed. Which buildroot would that be for the 400xm? 1578? > The latest buildroot normally expects the newer 3 partition scheme, > which needs u-boot to be updated. If you want, you can test out the > new image with the new u-boot without actually changing your existing > u-boot. Let me know if you want to go this route, and I can write down > some instructions. That would be great. Just thinking... would it be simpler to build a newer libm.a for 1161? Chuck |
From: Dave H. <dhy...@gm...> - 2007-12-29 17:33:46
|
Hi Chuck, > > I think that the latest buildroot will work for you. Is your connex > > an XM? > > Yes, it's a connex 400xm. No bluetooth. > > > You can always try building it, just to see if you can get things > > to build. > > That's a good idea. No rush to do the hard stuff until it's needed. > Which buildroot would that be for the 400xm? 1578? I'd try the latest. I don't have a connex with me to try it out, but I'm pretty sure it works. > > The latest buildroot normally expects the newer 3 partition scheme, > > which needs u-boot to be updated. If you want, you can test out the > > new image with the new u-boot without actually changing your existing > > u-boot. Let me know if you want to go this route, and I can write down > > some instructions. > > That would be great. I'd copy uImage, u-boot.bin, and rootfs onto the CF card, along with a copy of the 1161 version of rootfs. Then I'd load rootfs and program it into flash. Then I'd load the new u-boot.bin at location a2000000 and execute it (go a2000000). It will relocate itself to high memory and run from there. Then I'd load uImage and use the katinstall command. If anything goes wrong, just power cycle and you're back to the old u-boot and then you just need to reburn the 1161 rootfs. > Just thinking... would it be simpler to build a newer libm.a for 1161? There are probably lots of little issues along the way which need to be resolved, which are already taken care of by going to the latest buildroot. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chuck R. <shi...@ro...> - 2008-01-09 18:36:54
|
Hi Dave, It seems the gumstix wiki pages have changed to do things the OE way, so I installed gumstix OE on my linux ubuntu system and did a "bitbake gumstix-basic-version". I have no idea what version it built, or how I can specify it, but it says it worked: NOTE: Tasks Summary: Attempted 1359 tasks of which 1357 didn't need to be rerun and 0 failed. NOTE: build 200801082349: completed But now when I try to run ffmpeg's ./configure, it seems there's some sort of incompatibility: $ ./configure --cross-compile --cc=arm-linux=gcc --arch=arm arm-linux=gcc is unable to create an executable file. C compiler test failed. I followed the instructions on the wiki, updating my .bashrc, doing the chgrp for oe, etc. Also, with OE in place, how can I build against my original 1161 build like I used to? Chuck On Dec 29, 2007, at 9:33 AM, Dave Hylands wrote: > Hi Chuck, > >>> I think that the latest buildroot will work for you. Is your connex >>> an XM? >> >> Yes, it's a connex 400xm. No bluetooth. >> >>> You can always try building it, just to see if you can get things >>> to build. >> >> That's a good idea. No rush to do the hard stuff until it's needed. >> Which buildroot would that be for the 400xm? 1578? > > I'd try the latest. I don't have a connex with me to try it out, but > I'm pretty sure it works. > >>> The latest buildroot normally expects the newer 3 partition scheme, >>> which needs u-boot to be updated. If you want, you can test out the >>> new image with the new u-boot without actually changing your >>> existing >>> u-boot. Let me know if you want to go this route, and I can write >>> down >>> some instructions. >> >> That would be great. > > I'd copy uImage, u-boot.bin, and rootfs onto the CF card, along with a > copy of the 1161 version of rootfs. > > Then I'd load rootfs and program it into flash. > > Then I'd load the new u-boot.bin at location a2000000 and execute it > (go a2000000). It will relocate itself to high memory and run from > there. > > Then I'd load uImage and use the katinstall command. > > If anything goes wrong, just power cycle and you're back to the old > u-boot and then you just need to reburn the 1161 rootfs. > >> Just thinking... would it be simpler to build a newer libm.a for >> 1161? > > There are probably lots of little issues along the way which need to > be resolved, which are already taken care of by going to the latest > buildroot. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2008-01-09 18:57:10
|
> It seems the gumstix wiki pages have changed to do things the OE way, We haven't changed the wiki, it is still the place to go for buildroot documentation. Links and content are the same as always! As we make the transition, all gumstix-oe related material will appear at www.gumstix.net. The only content there now is preliminary documentation for those who would like an early start getting to know OE. > so I installed gumstix OE on my linux ubuntu system and did a > "bitbake gumstix-basic-version" Hmm . . . what instructions did you use to do the installation? There is no gumstix-basic-version in gumstix-oe. Do you perhaps mean gumstix-basic-image? To find out what revision you have do a svn status from the gumstix-oe directory. To find out what revision your gumstix is running do a cat /etc/gumstix-version from your gumstix command line. > But now when I try to run ffmpeg's ./configure, it seems there's some > sort of incompatibility: You shouldn't have to ever run configure manually. To build ffmpeg with gumstix-oe you would use the command: bitbake ffmpeg I'll give it a try to make sure there are no issues with that package, but it should be as simple as that. > Also, with OE in place, how can I build against my original 1161 > build like I used to? Buildroot and oe can co-exist on your machine. I have a gumstix subdirectory in my home directory and beneath that have gumstix-buildroot and gumstix-oe. You can bounce back and forth between systems with no problem. For your 1161 based efforts you should continue using buildroot. Regards, Steve |
From: Chuck R. <shi...@ro...> - 2008-01-11 04:43:46
|
Hi Steve, Thanks for your instructions! I was able to get gumstix OE downloaded and built. Took half a day, but it's done. > To find out what revision you have do a svn status from the gumstix-oe > directory. I'm not sure what's it's telling me here... $ cd gumstix/gumstix-oe $ svn status ? tmp M build/conf/auto.conf As for ffmpeg, 'bitbake ffmpeg' does cause it to build, but it errors out after an hour or so: NOTE: package ffmpeg-0.4.9-pre1-r1: task do_compile: started ERROR: function do_compile failed ERROR: log data follows (/usr/gumstix/gumstix-oe/tmp/work/armv5te- angstrom-linux-uclibcgnueabi/ffmpeg-0.4.9-pre1-r1/temp/log.do_compile. 24890) | NOTE: make | make -C libavcodec all | make[1]: Entering directory `/usr/gumstix/gumstix-oe/tmp/work/ armv5te-angstrom-linux-uclibcgnueabi/ffmpeg-0.4.9-pre1-r1/ ffmpeg-0.4.9-pre1/libavcodec' | arm-angstrom-linux-uclibcgnueabi-gcc -march=armv5te -mtune=xscale - O3 -Wall -isystem/usr/gumstix/gumstix-oe/tmp/staging/arm-angstrom- linux-uclibcgnueabi/include -fexpensive-optimizations -fomit-frame- pointer -frename-registers -Os -DHAVE_AV_CONFIG_H -I.. - D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -fPIC -DPIC - c -o common.o common.c | In file included from avcodec.h:14, | from common.c:28: | common.h:69: error: array type has incomplete element type | common.h:71: error: array type has incomplete element type | make[1]: *** [common.o] Error 1 | make[1]: Leaving directory `/usr/gumstix/gumstix-oe/tmp/work/ armv5te-angstrom-linux-uclibcgnueabi/ffmpeg-0.4.9-pre1-r1/ ffmpeg-0.4.9-pre1/libavcodec' | make: *** [lib] Error 2 | FATAL: oe_runmake failed Looking at common.h, lines 69 and 71 we have: 65 struct AVOption; 66 #ifdef HAVE_MMX 67 extern const struct AVOption avoptions_common[3 + 5]; 68 #else 69 extern const struct AVOption avoptions_common[3]; 70 #endif 71 extern const struct AVOption avoptions_workaround_bug[11]; I'm guessing that AVOption seems to have/be an 'incomplete element type'. Is there a compiler flag or other configuration option that's needed? Chuck On Jan 9, 2008, at 10:57 AM, Steve Sakoman wrote: >> It seems the gumstix wiki pages have changed to do things the OE way, > > We haven't changed the wiki, it is still the place to go for buildroot > documentation. Links and content are the same as always! > > As we make the transition, all gumstix-oe related material will appear > at www.gumstix.net. The only content there now is preliminary > documentation for those who would like an early start getting to know > OE. > >> so I installed gumstix OE on my linux ubuntu system and did a >> "bitbake gumstix-basic-version" > > Hmm . . . what instructions did you use to do the installation? > > There is no gumstix-basic-version in gumstix-oe. Do you perhaps mean > gumstix-basic-image? > > To find out what revision you have do a svn status from the gumstix-oe > directory. > > To find out what revision your gumstix is running do a cat > /etc/gumstix-version from your gumstix command line. > >> But now when I try to run ffmpeg's ./configure, it seems there's some >> sort of incompatibility: > > You shouldn't have to ever run configure manually. To build ffmpeg > with gumstix-oe you would use the command: > > bitbake ffmpeg > > I'll give it a try to make sure there are no issues with that package, > but it should be as simple as that. > >> Also, with OE in place, how can I build against my original 1161 >> build like I used to? > > Buildroot and oe can co-exist on your machine. I have a gumstix > subdirectory in my home directory and beneath that have > gumstix-buildroot and gumstix-oe. You can bounce back and forth > between systems with no problem. > > For your 1161 based efforts you should continue using buildroot. > > Regards, > > Steve > > |
From: Steve S. <sa...@gm...> - 2008-01-11 09:09:11
|
> To find out what revision you have do a svn status from the gumstix-oe > directory. My fingers weren't connected to my brain :-) I meant svn info I get the error on ffmpeg here too. I'll add it to my "to do" list. Steve |
From: thaGod <th...@gm...> - 2008-01-13 03:43:13
|
This may or may not be relevant, but the svn version of mplayer gives 2 of the same errors on normal x86 machines. There is one suggestion that worked on x86. It had to do with modifying the configure script to change some IFDEF's. I think that the configure script was confused as to where to get those definitions from and it was not using math.h like it should be. Our fix was to incorporate the roundf code that we could find through google searches and then just remove all other references to round-anything by commenting. Maybe you can apply some of the same philosophy to the lrint stuff. Hopefully it's a useful lead =) Erick Steve Sakoman wrote: > >> To find out what revision you have do a svn status from the gumstix-oe >> directory. > > My fingers weren't connected to my brain :-) I meant svn info > > I get the error on ffmpeg here too. I'll add it to my "to do" list. > > Steve > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/ffmpeg-undefined-references%3A-roundf%2C-llrint%2C-lrint-tp14430372p14781918.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chuck R. <shi...@ro...> - 2008-01-15 01:53:31
|
Thanks, Erick, that is exactly what I did. I just stuck the function definition code for llrint & roundf etc where they were needed, and it finally all built under buildroot 1161. Don't know why ld wasn't pulling them from libm. And I'm glad I didn't have to reflash my gumstix, as I would have going the OE route. Thanks! Chuck On Jan 12, 2008, at 7:43 PM, thaGod wrote: > > This may or may not be relevant, but the svn version of mplayer > gives 2 of > the same errors on normal x86 machines. There is one suggestion > that worked > on x86. It had to do with modifying the configure script to change > some > IFDEF's. I think that the configure script was confused as to where > to get > those definitions from and it was not using math.h like it should > be. Our > fix was to incorporate the roundf code that we could find through > google > searches and then just remove all other references to round- > anything by > commenting. Maybe you can apply some of the same philosophy to the > lrint > stuff. > > Hopefully it's a useful lead =) > > Erick > > > Steve Sakoman wrote: >> >>> To find out what revision you have do a svn status from the >>> gumstix-oe >>> directory. >> >> My fingers weren't connected to my brain :-) I meant svn info >> >> I get the error on ffmpeg here too. I'll add it to my "to do" list. >> >> Steve >> |
From: Dave H. <dhy...@gm...> - 2008-01-15 03:36:11
|
Hi Chuck, On Jan 14, 2008 5:53 PM, Chuck Randall <shi...@ro...> wrote: > Thanks, Erick, that is exactly what I did. I just stuck the function > definition code for llrint & roundf etc where they were needed, and > it finally all built under buildroot 1161. Don't know why ld wasn't > pulling them from libm. And I'm glad I didn't have to reflash my > gumstix, as I would have going the OE route. It could depend on the order of the libraries being specified on the command line. The linker is a single pass linker, and the order of the libraries does make a difference. -lm should be one of the last (if not the last) library specified on the command line. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chuck R. <shi...@ro...> - 2008-01-15 03:43:23
|
Hi Dave, The last portion of the ld line is this: -lavdevice -lavformat -lavcodec -lavutil -lz -lm -ldl The buildroot 1161 version of libm does have roundf, but ld never seemed to see it. Chuck On Jan 14, 2008, at 7:36 PM, Dave Hylands wrote: > Hi Chuck, > > On Jan 14, 2008 5:53 PM, Chuck Randall <shi...@ro...> > wrote: >> Thanks, Erick, that is exactly what I did. I just stuck the function >> definition code for llrint & roundf etc where they were needed, and >> it finally all built under buildroot 1161. Don't know why ld wasn't >> pulling them from libm. And I'm glad I didn't have to reflash my >> gumstix, as I would have going the OE route. > > It could depend on the order of the libraries being specified on the > command line. > > The linker is a single pass linker, and the order of the libraries > does make a difference. > > -lm should be one of the last (if not the last) library specified on > the command line. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > |