ssh-dss
AAAAB3NzaC1kc3MAAACBAMOlZO6Wlr3VmMHaM45cN504kZbhoSaYrc8cGQfSM7c8gmVIIypb9xfkB/SDUe+AvRR8clUqX0WZT8HkwxYKg+EpyqIr4PScyIIY/eFNB6YnicqN4xFw3HNoJq03bt+yguSDzU6EVzTkcm812UZDLP3yUrGrzmOUwhM2P9Q1ynZjAAAAFQDgMR4oPGUopWODpzcGmaMjdMimrQAAAIAgGdI9ogeJxBvCgUnBjZPYjkzk/WCimRtkmsNBcpT3vGUimcPD6qY/tm8LMB1NAPf2mqBYlaIFw/sQs9dbhKjn3SIgehlugGfB2SOKDBd9LM4XufaRNYl8X9aQ4q0jaLtKIZID2DqCMNVALMHYYfyFTMi07N7b55/9TpK8IzeUzgAAAIEAkg2L3aS3dH2ec8L37rJvOLCxEJmjgw4vgu/r4UTCUlp2htVS6SE0CcOmoPWOp7Vk2GkXlPNkCkUGAUBBy/QfohndzjQQW0Rge0fSu37SB+BIiyzkeGeO1xtGe98EF0WrWSXRJv0lU3F+lfFKvLuLF4EQf9Ci0SXeYHcJo2pirbk=
[EMAIL PROTECTED]

That's siren's new key. I'll manually add the one for my other workstation
after I get setup.

On Sat, Jun 28, 2008 at 12:39 PM, Stephen R Marenka <[EMAIL PROTECTED]>
wrote:

> On Thu, Jun 26, 2008 at 09:16:42PM -0400, Michael Casadevall wrote:
> > Reading up on the changes made to GCC for gnu99/c99, I've been
> researching
> > workarounds and such, and I may have hit paydirt;GCC has an option which
> > causes the code to use the gnu89 linkage over the current gnu99 while
> still
> > allowing the code extensions of gnu99.
> >
> > In other words, it will allow c99/gnu99 to be compiled against our aging
> > glibc :-). If this works, I can cook up a patch that will force this open
> > (it probably just need a tweak to the spec file to cause the proper
> option
> > to be set). Unfortanately, I don't have access to an m68k or even a
> general
> > Linux box to build a cross-compiler to test my theory. If someone wishes
> to
> > donate access to a machine to test my theory, it will be appericated;
> until
> > tell, I'm going to see if I can bootstrap the required compiler from
> Windows
> > so I can at least see if the code will build.
> > Michael
>
> If you haven't got access yet, please send me a public key and I'll set
> you up.
>
> --
> Stephen R. Marenka     If life's not fun, you're not doing it right!
> <[EMAIL PROTECTED]>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIZmlFVKM4J7YoSbMRApLrAKCE5e3cufdUjw30fpvml7B9F/os4gCfTzp0
> Tydvu6800t3DnIltNoXuvzE=
> =KXho
> -----END PGP SIGNATURE-----
>
>

Reply via email to