From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: a5c7b007eaa675cc904f5285291d2f8a597efc84
Date: Thu, 10 Jan 2008 06:51:55 -0500 [thread overview]
Message-ID: <478606DB.7060501@balister.org> (raw)
In-Reply-To: <478605A1.5030209@student.utwente.nl>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
I have gfortran installed already (must be the engineer in me) and I
also had to add the ugly hack in bug 3363.
Koen is right, there is something funny going on.
Philip
Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Holger Freyther schreef:
> | On Thursday 10 January 2008 11:45:10 Koen Kooi wrote:
> |> ~ * gfortran is NOT needed to build a gfortran cross-compiler, something
> |> else is wrong.
> |
> | Hi,
> |
> | feel free to disapprove it, there are at least two open bug reports
> regarding
> | fortran that we will have to look into.
>
> I don't have a (better) solution on how to pull in the deps needed or
> fix the -native ones in OE, so it can stay as it it, I just wanted to
> raise some awareness of the issue and why fortran was enabled.
>
> regards,
>
> Koen
>
> - --
> koen@dominion.kabel.utwente.nl will go go away in december 2007, please
> use k.kooi@student.utwente.nl instead.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFHhgWhMkyGM64RGpERAmgBAKC1Io3+VFpqG24HTkGELawUFaJeiwCgqkzi
> 2x2WvpLfnAY5o8cbMs4iZzU=
> =65Fg
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-01-10 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 10:45 a5c7b007eaa675cc904f5285291d2f8a597efc84 Koen Kooi
2008-01-10 11:21 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Holger Freyther
2008-01-10 11:46 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Koen Kooi
2008-01-10 11:51 ` Philip Balister [this message]
2008-01-11 18:24 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Leon Woestenberg
2008-01-11 19:53 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Michael 'Mickey' Lauer
2008-01-11 20:05 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Leon Woestenberg
2008-01-12 0:02 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Paul Sokolovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=478606DB.7060501@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.