Hello
You have requested a new password for the Ubuntu One
using the following email address:
gcc@gcc.gnu.org
This email address is however not associated with any Ubuntu One
accounts. If you want to create a new Ubuntu One account using
this email address, please go to:
https://login.launchpad
William Seurer 于2020年5月18日周一 下午10:52写道：
>
> On 5/18/20 9:35 AM, Hongyi Zhao via Gcc wrote:
> > Jonathan Wakely 于2020年5月18日周一 下午8:49写道：
> >> On Mon, 18 May 2020 at 13:34, Hongyi Zhao via Gcc wrote:
> >>> Hi,
> >>>
> >>> I want to compile qt4 on Ubuntu 20.04 which shipped with the following
> >>>
William Seurer 于2020年5月18日周一 下午10:52写道：
>
> On 5/18/20 9:35 AM, Hongyi Zhao via Gcc wrote:
> > Jonathan Wakely 于2020年5月18日周一 下午8:49写道：
> >> On Mon, 18 May 2020 at 13:34, Hongyi Zhao via Gcc wrote:
> >>> Hi,
> >>>
> >>> I want to compile qt4 on Ubuntu 20.04 which shipped with the following
> >>>
The Go front end fails to build for me on 10-branch with the error
below (and many others that look like they're cause by it). Git
log doesn't show any recent changes that might be responsible for
it. It looks like the code is guarded by the conditional #if
defined(HAVE_UNORDERED_MAP) and HAVE_U
TL;DR: How to preserve multilibs directory hierarchy for GCC 64 bit
configuration on AIX when 32 bit multilib exists in the top-level
directory, no explicit MULTILIB_DIRNAME.
Currently the powerpc-ibm-aix* port supports a 64-bit explicit
multilib and a 32 bit implicit, default multilib in the top-
Hi,
I have noticed LINK_SPEC is empty on x86_64-pc-elf and i[3456]86-pc-elf
targets. Lack of LINK_SPEC means -m16/-m32/-mx32/-m64 are not converted
to correct linker emulation mode. Is it expected behaviour?
If it's not, where would be the best place to define LINK_SPEC? Is it
okay to do that in
On 5/18/20 9:35 AM, Hongyi Zhao via Gcc wrote:
Jonathan Wakely 于2020年5月18日周一 下午8:49写道：
On Mon, 18 May 2020 at 13:34, Hongyi Zhao via Gcc wrote:
Hi,
I want to compile qt4 on Ubuntu 20.04 which shipped with the following
gcc version:
$ gcc --version
gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
But I'm
Jonathan Wakely 于2020年5月18日周一 下午8:49写道：
>
> On Mon, 18 May 2020 at 13:34, Hongyi Zhao via Gcc wrote:
> >
> > Hi,
> >
> > I want to compile qt4 on Ubuntu 20.04 which shipped with the following
> > gcc version:
> >
> > $ gcc --version
> > gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
> >
> > But I'm not sure
On Mon, 18 May 2020 at 13:34, Hongyi Zhao via Gcc wrote:
>
> Hi,
>
> I want to compile qt4 on Ubuntu 20.04 which shipped with the following
> gcc version:
>
> $ gcc --version
> gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
>
> But I'm not sure whether this gcc version is suitable for qt4. Any
> hints for th
Qt4 is an old release (the current one is almost Qt6). A newer compiler is
usually backward-compatible with older codes. So you should be able to
compile Qt4 on Ubuntu 20.04 with system-provided GCC right away.
пн, 18 мая 2020 г. в 14:34, Hongyi Zhao via Gcc :
> Hi,
>
> I want to compile qt4 on U
Hi,
I want to compile qt4 on Ubuntu 20.04 which shipped with the following
gcc version:
$ gcc --version
gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
But I'm not sure whether this gcc version is suitable for qt4. Any
hints for this problem?
Regards,
--
Hongyi Zhao
Hi everyone,
I've discovered, when building gcc10, that the tests in multilib directories
aren't launched correctly, at least in our configuration (powerpc-ibm-aix* with
ppc64 and pthread multilibs).
The tests are using the default compiler and the default library path instead
of using the mu
12 matches
Mail list logo
