[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 1 May 2013 20:00:28 +0400
From: Vasily Kulikov <segoon@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: PIE on x86_64
On Wed, May 01, 2013 at 16:21 +0200, Gilles Espinasse wrote:
>
>
> ----- Mail original -----
> > De: "Vasily Kulikov" <segoon@...nwall.com>
> > À: owl-dev@...ts.openwall.com
> > Envoyé: Mercredi 1 Mai 2013 09:46:54
> > Objet: Re: [owl-dev] PIE on x86_64
> >
> > On Tue, Apr 30, 2013 at 21:36 +0400, Vasily Kulikov wrote:
> > > The only one package which fails to build as-is on x86_64 --
> > > kernel.
> > > The -D__KERNEL__ check is present, though. Will try to figure it
> > > out
> > > (likely, tomorrow).
> >
> > Strange, %{DXXX:...} doesn't work in gcc specs file:
> >
> > vasya@...halot:~/src/gcc-test$ cat spec
> > *cc1:
> > %(cc1_cpu) %{profile:-p} %{DABC:%eABC is used!} %{!DABC:%eABC is
> > not %used!}
> >
> > vasya@...halot:~/src/gcc-test$ gcc -specs=spec -DABC -E -c -
> > gcc: error: ABC is not used!
> >
> > Probably the syntax of specs file or ability to process macros were
> > changed in gcc 4.x?
> >
>
> You somehow broke something as it work for me on gcc-4.4 or gcc-4.1.2
> Nota : the content of the spec file differ from the string displayed by '%' between not and used but that should not matter.
Sorry, it was mangled. The real specs file has no '%' between these words.
> [root@...vista tmp]# gcc -specs=spec -DABC -E -c -
> gcc: ABC is used!
> [root@...vista tmp]# gcc -specs=spec -E -c -
> gcc: ABC is not used!
> [root@...vista tmp]# gcc --version
> gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-54)
The same on Owl 3.0:
$ gcc --version | head -n1
gcc (GCC) 3.4.5
build@...halot:~ $ gcc -specs=gcc-specs -E -c -
gcc: ABC is not used!
build@...halot:~ $ gcc -specs=gcc-specs -DABC -E -c -
gcc: ABC is used!
But not on Owl current with gcc 4.6.3 and on Ubuntu 12.04 with gcc
4.6.3.
--
Vasily
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
