Does anybody meet undefined reference to `WebCo:CSSParser::lex()' while compiling android source?

by 鍝侀洩 » Mon, 22 Dec 2008 10:12:36 GMT

Sponsored Links
 Mac OS X Leopard 10.5.5, flex 2.5.35 and bison 2.4 from macports,
xcode 3.1.2

It always stop as:

target SharedLib: libwebcore (out/target/product/generic/obj/
libwebcore_intermediates/css/CSSParser.o: In function
external/webkit/WebCore/css/CSSParser.cpp:3558: undefined reference to
collect2: ld returned 1 exit status
make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/
libwebcore_intermediates/LINKED/] Error 1

I can compile the source in Ubuntu Linux and seems the source code are
exactly same. And I did compiled once in another Leopard machine which
is not available for me now. So that I guess it is environment issue
instead of a bug.


Other Threads

1. What kind of device should Linux udev set up for G1 linked via USB


I am trying to get adb to see my Android G1 Dev Phone when I attach it
to a Fedora 10
x86 Linux PC. I have followed recommendations about adding a 50-
android.rules file
in /etc/udev/rules.d directory. I have also enabled the applications
debug mode under
the G1's Settings/Applications menu.

On the Fedora 10 x86 PC I run

tail -f /var/log/messages

and watch the output as I attach the G1 via USB. The G1 is set up as a
SCSI mass storage
by udev. Is this what should happen ? Can anyone from Google answer
what kind of device should udev  set up so that the command  adb
devices actually sees the G1 ?
What kind of device does adb expect to talk to over USB ?


PS I have had similar experiences/frustrations trying this out with
Ubuntu 8.10.

2. sensors HAL/single input device for multiple kernel drivers

Hi all,

I am in the process of writing a sensors HAL based on the new cupcake
module structure.  One restriction of the sensors HAL is that there
can only be a single input device used for all sensors.  Can anyone
provide any assistance and/or example on how this might be done with
multiple kernel drivers.  Each sensor kernel driver has its own misc
device for ioctl calls.  Would I have the first driver allocate the
input device and the rest of the drivers register to the same device?


3. Theme.Dialog for PreferenceScreen child does not work

4. adb stopped working (Ubuntu 8.10)

5. JMI and android

6. How to get Available Device RAM

7. building kernel, the android method.