Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 173003 Details for
Bug 248398
sys-apps/vbetool: fails with forced --as-needed
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Build log
vbetool-1.0:20081123-095837.log (text/plain), 5.38 KB, created by
Diego Elio Pettenò (RETIRED)
on 2008-11-23 16:15:03 UTC
(
hide
)
Description:
Build log
Filename:
MIME Type:
Creator:
Diego Elio Pettenò (RETIRED)
Created:
2008-11-23 16:15:03 UTC
Size:
5.38 KB
patch
obsolete
>>>> Unpacking source... >>>> Unpacking vbetool_1.0-0ubuntu1.tar.gz to /var/tmp/portage/sys-apps/vbetool-1.0/work > [32;01m*[0m Running eautoreconf in '/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0' ... > [32;01m*[0m Running aclocal ... >[A[72C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Running autoconf ... >[A[72C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Running automake --add-missing --copy --foreign ... >[A[72C [34;01m[ [32;01mok[34;01m ][0m >>>> Source unpacked. >>>> Compiling source in /var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0 ... > * econf: updating vbetool-1.0/config.guess with /usr/share/gnuconfig/config.guess > * econf: updating vbetool-1.0/config.sub with /usr/share/gnuconfig/config.sub >./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-x86emu --build=i686-pc-linux-gnu >checking for a BSD-compatible install... /usr/bin/install -c >checking whether build environment is sane... yes >checking for a thread-safe mkdir -p... /bin/mkdir -p >checking for gawk... gawk >checking whether make sets $(MAKE)... yes >checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc >checking for C compiler default output file name... a.out >checking whether the C compiler works... yes >checking whether we are cross compiling... no >checking for suffix of executables... >checking for suffix of object files... o >checking whether we are using the GNU C compiler... yes >checking whether i686-pc-linux-gnu-gcc accepts -g... yes >checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed >checking for style of include used by make... GNU >checking dependency style of i686-pc-linux-gnu-gcc... gcc3 >configure: creating ./config.status >config.status: creating Makefile >config.status: executing depfiles commands >make -j14 >i686-pc-linux-gnu-gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"vbetool\" -DVERSION=\"0.3\" -I. -g -Wall -pedantic -std=gnu99 -O2 -pipe -MT vbetool.o -MD -MP -MF .deps/vbetool.Tpo -c -o vbetool.o vbetool.c >vbetool.c: In function 'do_get_panel_id': >vbetool.c:519: warning: format '%ld' expects type 'long int', but argument 3 has type 'unsigned int' >mv -f .deps/vbetool.Tpo .deps/vbetool.Po >i686-pc-linux-gnu-gcc -g -Wall -pedantic -std=gnu99 -O2 -pipe -lz -lx86 -Wl,-O1 -o vbetool vbetool.o -lpci >vbetool.o: In function `do_vbe_service': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:158: undefined reference to `LRMI_int' >vbetool.o: In function `do_get_panel_id': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:514: undefined reference to `LRMI_alloc_real' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:515: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:516: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:521: undefined reference to `LRMI_int' >vbetool.o: In function `__save_state': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:301: undefined reference to `LRMI_int' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:312: undefined reference to `LRMI_alloc_real' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:321: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:328: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:329: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:334: undefined reference to `LRMI_int' >vbetool.o: In function `restore_state_from': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:246: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:247: undefined reference to `LRMI_base_addr' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:250: undefined reference to `LRMI_int' >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:257: undefined reference to `LRMI_free_real' >vbetool.o: In function `restore_state': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:282: undefined reference to `LRMI_alloc_real' >vbetool.o: In function `do_real_post': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:201: undefined reference to `LRMI_call' >vbetool.o: In function `vbetool_init': >/var/tmp/portage/sys-apps/vbetool-1.0/work/vbetool-1.0/vbetool.c:40: undefined reference to `LRMI_init' >collect2: ld returned 1 exit status >make: *** [vbetool] Error 1 > [31;01m*[0m > [31;01m*[0m ERROR: sys-apps/vbetool-1.0 failed. > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 49: Called src_compile > [31;01m*[0m environment, line 2923: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m emake || die "emake failed" > [31;01m*[0m The die message: > [31;01m*[0m emake failed > [31;01m*[0m > [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. > [31;01m*[0m A complete build log is located at '/var/log/portage/sys-apps/vbetool-1.0:20081123-095837.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-apps/vbetool-1.0/temp/environment'. > [31;01m*[0m
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 248398
: 173003