Bug 83233 – synce works perfectly on amd64 when you change a very minor thing.

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Taylor Morrow 2005-02-24 13:57:15 UTC]

I installed the following packages, all of which work great.  The only two things I changed were to remove all of the "-Werror" flags and I added a "-fPIC" flag to libmimedir.


app-pda/synce
app-pda/synce-serial
app-pda/synce-dccm
app-pda/synce-kde
app-pda/synce-rra
dev-libs/libmimedir
app-arch/unshield
app-pda/synce-librapi2
app-pda/dynamite
app-pda/orange

Reproducible: Always
Steps to Reproduce:




Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.4.3,
glibc-2.3.4.20050125-r0,2.6.10-cko3 x86_64)
=================================================================
System uname: 2.6.10-cko3 x86_64 AMD Athlon(tm) 64 FX-55 Processor
Gentoo Base System version 1.6.9
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Feb 18 2005, 19:00:29)]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r3
sys-devel/libtool:   1.5.10-r5
virtual/os-headers:  2.6.8.1-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-fx -mtune=athlon-fx -O3 -pipe -fomit-frame-pointer -fweb"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-fx -mtune=athlon-fx -O3 -pipe -fomit-frame-pointer -fweb"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://gentoo.osuosl.org"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="amd64 X acpi aim alsa berkdb bitmap-fonts cdr crypt cups curl dvd dvdr f77
famfont-server foomaticdb fortran gif gpm imagemagick jack java joystick jp2
jpeg junit kde libwww lirc lzw lzw-tiff motif mp3 msn multilib ncurses nls nptl
opengl pam perl png ppds python qt readline sdl ssh ssl tcpd tetex tiff truetype
truetype-fonts type1-fonts usb userlocales xml2 xmms xpm xrandr xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

[Comment 1 Carsten Lohrke (RETIRED) 2005-02-24 14:38:56 UTC]

um..

[Comment 2 Alastair Tse (RETIRED) 2005-03-08 09:35:24 UTC]

can amd64 folks test?

[Comment 3 Alexander Roos 2005-03-29 04:03:14 UTC]

How can I remove the -Werror-Flag?
Always when I

[Comment 4 Alexander Roos 2005-03-29 04:03:14 UTC]

How can I remove the -Werror-Flag?
Always when I´m emerging "unshield" my changes in Makefile are overwritten.

[Comment 5 Alexander Roos 2005-03-29 04:04:10 UTC]

How can I remove the -Werror-Flag?
Always when I

[Comment 6 Alexander Roos 2005-03-29 04:04:10 UTC]

How can I remove the -Werror-Flag?
Always when I´m emerging "unshield" my changes in Makefile are overwritten.

[Comment 7 Taylor Morrow 2005-03-29 05:49:09 UTC]

Start the emerge, and when it finishes unpacking the tarball, hit ctrl-z.  Edit the makefile, and then type fg.

[Comment 8 Alexander Roos 2005-03-29 06:48:44 UTC]

The suggested solution with removing "-Werror" and adding "-fPIC" to libmimedir works great.

Synce now works under AMD64.

[Comment 9 Taylor Morrow 2005-05-15 09:06:23 UTC]

umm, bump?

[Comment 10 Alexander Roos 2005-06-05 04:06:07 UTC]

synce works great under AMD64

[Comment 11 Simon Stelling (RETIRED) 2005-06-05 05:14:16 UTC]

adding -fPIC to CFLAGS is not a correct solution, we need a patch which enables
-fPIC only for shared objects. sorry.

[Comment 12 Taylor Morrow 2005-06-05 12:05:25 UTC]

libmimedir doesn't include anything but a shared object, does it?

I'm not saying to add -fPIC to cflags for all of it, just libmimedir.

[Comment 13 Simon Stelling (RETIRED) 2005-06-05 13:43:20 UTC]

you're right, in fact, i didn't even need to add -fPIC for libmimedir, but i'd
rather write patches than take the -Werror out...

unshield is ~amd64, needed a little patch
synce-libsynce is also ~amd64

i'll have a look at the rest later

[Comment 14 Simon Stelling (RETIRED) 2005-06-05 14:29:48 UTC]

synce-serial marked ~amd64

[Comment 15 Simon Stelling (RETIRED) 2005-06-05 14:36:28 UTC]

synce-serial and dynamite marked ~amd64

[Comment 16 Simon Stelling (RETIRED) 2005-06-08 11:33:36 UTC]

here are quite a lot of casts from pointers to int and back (at least in
synce-librapi2), i'm pretty sure this will break the package. could you please
provide a patch for that? upstream is aware of this issue, at least the have a
comment in the code saying it causes troubles on 64bit arches... otherwise, we
will have to wait until this is fixed upstream

[Comment 17 Simon Stelling (RETIRED) 2005-06-09 13:25:30 UTC]

please reopen with a patch

[Comment 18 Nigel Hannam 2005-08-14 05:15:56 UTC]

Providing the -fPIC change is made to libmimedir-0.4,
synce-librap2-0.9.1 (http://bugs.gentoo.org/show_bug.cgi?id=101370) builds on
amd64 without error.

In fact with that one change to libmimedir, all the synce 0.9.1 stuff seems to
compile and work ok.  The only thing that I needed to build with -Werror removed
is synce-gnomevfs which is still on 0.9.0.
Given that not everybody will want the gnome gui bits, is it worth getting the
basic synce stuff ~amd64 keyworded when the version bump is released?

[Comment 19 Nigel Hannam 2005-08-14 05:24:43 UTC]

I beleive the -fPIC change to libmimedir was required to get synce-rra to compile.