here is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the
Mozilla/Firefox/Thunderbird build on x86_64 and various other
processors: GCC is treating the builtin functions such as “memset”
and “memcpy” as having hidden visibility in certain circumstances
that are hard to figure out. GCC bug 20297 covers the issue, though
the patch in the bug doesn’t fix all the problems and I haven’t
seen any action by the GCC maintainers to get the patch landed or
fixed. I tried to provide a patch to detect this bug in Mozilla bug
307168, but apparently my configure test is not good enough to
catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
afaafafaafdafahere is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the Mozilla/Firefox/Thunderbird build on x86_64 and various other processors: GCC is treating the builtin functions such as “memset” and “memcpy” as having hidden visibility in certain circumstances that are hard to figure out. GCC bug 20297 covers the issue, though the patch in the bug doesn’t fix all the problems and I haven’t seen any action by the GCC maintainers to get the patch landed or fixed. I tried to provide a patch to detect this bug in Mozilla bug 307168, but apparently my configure test is not good enough to catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
here is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the Mozilla/Firefox/Thunderbird build on x86_64 and various other processors: GCC is treating the builtin functions such as “memset” and “memcpy” as having hidden visibility in certain circumstances that are hard to figure out. GCC bug 20297 covers the issue, though the patch in the bug doesn’t fix all the problems and I haven’t seen any action by the GCC maintainers to get the patch landed or fixed. I tried to provide a patch to detect this bug in Mozilla bug 307168, but apparently my configure test is not good enough to catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
here is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the Mozilla/Firefox/Thunderbird build on x86_64 and various other processors: GCC is treating the builtin functions such as “memset” and “memcpy” as having hidden visibility in certain circumstances that are hard to figure out. GCC bug 20297 covers the issue, though the patch in the bug doesn’t fix all the problems and I haven’t seen any action by the GCC maintainers to get the patch landed or fixed. I tried to provide a patch to detect this bug in Mozilla bug 307168, but apparently my configure test is not good enough to catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
I am aaafdaf, jkljkl;jkl;, and aefra
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
afaafafaafdafahere is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the Mozilla/Firefox/Thunderbird build on x86_64 and various other processors: GCC is treating the builtin functions such as “memset” and “memcpy” as having hidden visibility in certain circumstances that are hard to figure out. GCC bug 20297 covers the issue, though the patch in the bug doesn’t fix all the problems and I haven’t seen any action by the GCC maintainers to get the patch landed or fixed. I tried to provide a patch to detect this bug in Mozilla bug 307168, but apparently my configure test is not good enough to catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
here is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the Mozilla/Firefox/Thunderbird build on x86_64 and various other processors: GCC is treating the builtin functions such as “memset” and “memcpy” as having hidden visibility in certain circumstances that are hard to figure out. GCC bug 20297 covers the issue, though the patch in the bug doesn’t fix all the problems and I haven’t seen any action by the GCC maintainers to get the patch landed or fixed. I tried to provide a patch to detect this bug in Mozilla bug 307168, but apparently my configure test is not good enough to catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
here is a bug in GCC 4.0 (and 4.0.1 and 4.1) which breaks the Mozilla/Firefox/Thunderbird build on x86_64 and various other processors: GCC is treating the builtin functions such as “memset” and “memcpy” as having hidden visibility in certain circumstances that are hard to figure out. GCC bug 20297 covers the issue, though the patch in the bug doesn’t fix all the problems and I haven’t seen any action by the GCC maintainers to get the patch landed or fixed. I tried to provide a patch to detect this bug in Mozilla bug 307168, but apparently my configure test is not good enough to catch all instances of the bug.
In the meantime, if you experience the error “relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used” or something similar while building mozilla, use the following hackaround:
ac_cv_visibility_pragma=no path/to/mozilla/configure –enable-options-here
or put this in your mozconfig:
ac_cv_visibility_pragma=no (Don’t prefix this with ac_add_options!)
This entry was posted on 27 Oct, 2005 at 1:17 pm and is filed under planetmoz. Trackback. Atom Feed for Comments 17 Responses to “GCC4.0 - relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′ can not be used”
1. gandalf Says:
October 27th, 2005 at 2:52 pm
Thankssssssssss! Finally, I’ll be able to do coding on my laptop *^^*
2. James Curbo's Weblog Says:
November 5th, 2005 at 4:15 am
Error building Firefox on Linux amd64
I’ve been trying to build Firefox on Debian amd64 for a while and keep getting the same error, a compiler error containing ‘relocation R_X86_64_PC32 against `memcpy@@GLIBC_2.2.5′. Benjamin Smedberg wrote about a solution so I thought I’d at leas…
3. James Says:
November 6th, 2005 at 8:22 pm
thunderbird-1.5rc1 compiles but unfortunately it won’t run. :-(
It always shows an “Thunderbird is already running, but is not responding…” dialog even after rebooting.
I am aaafdaf, jkljkl;jkl;, and aefra
