public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] glibc problem with amd64
@ 2006-02-09 11:40 Nadav Horesh
  2006-02-09 15:23 ` Hemmann, Volker Armin
  2006-02-09 17:07 ` Richard Fish
  0 siblings, 2 replies; 4+ messages in thread
From: Nadav Horesh @ 2006-02-09 11:40 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 2811 bytes --]

I tried to compile openv (Intel's computer vision library) on amd64 (64 bit mode) and it failed  with the gollowing message:
 
 g++ -shared /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crti.o /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/crtbeginS.o  .libs/cxalloc.o .libs/cxarithm.o .libs/cxarray.o .libs/cxcmp.o .libs/cxconvert.o .libs/cxcopy.o .libs/cxdatastructs.o .libs/cxdrawing.o .libs/cxdxt.o .libs/cxerror.o .libs/cxjacobieigens.o .libs/cxlogic.o .libs/cxlut.o .libs/cxmathfuncs.o .libs/cxmatmul.o .libs/cxmatrix.o .libs/cxmean.o .libs/cxmeansdv.o .libs/cxminmaxloc.o .libs/cxnorm.o .libs/cxouttext.o .libs/cxpersistence.o .libs/cxprecomp.o .libs/cxrand.o .libs/cxsumpixels.o .libs/cxsvd.o .libs/cxswitcher.o .libs/cxtables.o .libs/cxutils.o  -L/usr/x86_64-pc-linux-gnu/lib -L/usr/x86_64-pc-linux-gnu/bin -ldl -lpthread -L/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4 -L/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64 -L/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../.. -L/lib/../lib64 -L/usr/lib/../lib64
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so -lm -lc -lgcc_s /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/crtendS.o /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crtn.o  -march=k8 -mfpmath=sse -msse3 -o .libs/libcxcore.so.0.9.7
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crti.o: In function `_init':
 /var/tmp/portage/glibc-2.3.5-r2/work/build-amd64-x86_64-pc-linux-gnu-linuxthreads/csu/crti.S:11: multiple definition of `_init'
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crti.o:/var/tmp/portage/glibc-2.3.5-r2/work/build-amd64-x86_64-pc-linux-gnu-linuxthreads/csu/crti.S:11: first defined here
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crti.o: In function `_fini':
 /var/tmp/portage/glibc-2.3.5-r2/work/build-amd64-x86_64-pc-linux-gnu-linuxthreads/csu/crti.S:(.fini+0x0): multiple definition of `_fini'
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crti.o:/var/tmp/portage/glibc-2.3.5-r2/work/build-amd64-x86_64-pc-linux-gnu-linuxthreads/csu/crti.S:(.fini+0x0): first defined here
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/crtbeginS.o:(.data.rel+0x0): multiple definition of `__dso_handle'
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/crtbeginS.o:(.data.rel+0x0): first defined here
 collect2: ld returned 1 exit status
 
 I would like to note that:
  * The cmpilation went smoothly on a P4 (32 bit) with the same glibc (2.3.5-r2)
  * I saw several post on this glibc issue with other distros. One suggested to compile glibc with -funit-at-a-time.  but this option aborted glibc compilation.
 
 Any idea?
 
    Nadav.
 
		
---------------------------------
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

[-- Attachment #2: Type: text/html, Size: 3050 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-user] glibc problem with amd64
  2006-02-09 11:40 [gentoo-user] glibc problem with amd64 Nadav Horesh
@ 2006-02-09 15:23 ` Hemmann, Volker Armin
  2006-02-09 17:07 ` Richard Fish
  1 sibling, 0 replies; 4+ messages in thread
From: Hemmann, Volker Armin @ 2006-02-09 15:23 UTC (permalink / raw
  To: gentoo-user

On Thursday 09 February 2006 12:40, Nadav Horesh wrote:
>  

retry with O2 and without mfpmath and -msse3?

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-user] glibc problem with amd64
  2006-02-09 11:40 [gentoo-user] glibc problem with amd64 Nadav Horesh
  2006-02-09 15:23 ` Hemmann, Volker Armin
@ 2006-02-09 17:07 ` Richard Fish
  1 sibling, 0 replies; 4+ messages in thread
From: Richard Fish @ 2006-02-09 17:07 UTC (permalink / raw
  To: gentoo-user

On 2/9/06, Nadav Horesh <nadavh2000@yahoo.co.uk> wrote:
> I tried to compile openv (Intel's computer vision library) on amd64 (64 bit
> mode) and it failed  with the gollowing message:
>
>  g++ -shared
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/crti.o
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/crtbeginS.o

AFAIK the build should not be calling out crti.o, crtbeginS.o, and
crtendS.o directly.  These are added by gcc automatically.  Maybe the
-nostdlib flag can help here...

CFLAGS=-nostdlib emerge ...

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-user] glibc problem with amd64
@ 2006-02-10 16:22 Nadav Horesh
  0 siblings, 0 replies; 4+ messages in thread
From: Nadav Horesh @ 2006-02-10 16:22 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

Still can not compile opencv:
 1. Tried with CFLAGS="-O2 -march=k8 -pipe" as recommended in "Gentoo Linux/AMD64 FAQ". The compilation fails at the same point.
 2. (Richard Fish): The links to crti.o and crtbeginS.o are in the glibc, they are not in the opencv makefile.
 
 Any more Ideas?
 Should it be addressed to the gentoo developers ?
 
   Nadav.
  
		
---------------------------------
Yahoo! Photos – NEW, now offering a quality print service from just 8p a photo.

[-- Attachment #2: Type: text/html, Size: 846 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-02-10 16:31 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-09 11:40 [gentoo-user] glibc problem with amd64 Nadav Horesh
2006-02-09 15:23 ` Hemmann, Volker Armin
2006-02-09 17:07 ` Richard Fish
  -- strict thread matches above, loose matches on Subject: below --
2006-02-10 16:22 Nadav Horesh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox