Ie, we(OBSD developers/maintainers) have no time to send patches to
the GCC-patches, and you have no desire to help me to send them. I
understand correctly?
P.S.
2013/9/16 Marc Espie:
> Yes, USE THE FUCKING PORT.
...
> Look, you are obviously a clueless newbie.
...
> Or just shut up.
And you se
On Mon, Sep 16, 2013 at 10:02:15PM +0400, niXman wrote:
> And you seem to be a rude fellow.
Thank you. I have every right to be, by birth.
And you're an obvious troll, since you chose to quote parts of my emails
without the rest of the context.
Enough said.
byebye.
On Mon, Sep 16, 2013 at 03:35:04PM +0400, niXman wrote:
> 2013/9/11 niXman:
> > 2013/9/11 Tobias Ulmer:
> >> Because it's work. Do you volunteer?
> >
> > Yes, I will, if someone will coordinate me.
> > First of all, I need a description of what exactly problem is solved
> > by each patch.
>
Look,
On Mon, Sep 16, 2013 at 03:35:04PM +0400, niXman wrote:
> 2013/9/11 niXman:
> > 2013/9/11 Tobias Ulmer:
> >> Because it's work. Do you volunteer?
> >
> > Yes, I will, if someone will coordinate me.
> > First of all, I need a description of what exactly problem is solved
> > by each patch.
>
> ping
2013/9/11 niXman:
> 2013/9/11 Tobias Ulmer:
>> Because it's work. Do you volunteer?
>
> Yes, I will, if someone will coordinate me.
> First of all, I need a description of what exactly problem is solved
> by each patch.
ping?
--
Regards,
niXman
__
On 09/11/13 05:21, Stuart Henderson wrote:
On 2013/09/11 12:06, niXman wrote:
2013/9/11 Stuart Henderson
The error message gives quite a good clue:
relocation R_X86_64_32 can not be used when making a shared object; recompile
with -fPIC
Maybe, but it doesn't speak to me about anything. Can y
On Wed, Sep 11, 2013 at 04:14:23PM +0400, niXman wrote:
> 2013/9/11 Tobias Ulmer:
> > This is only the first of many many errors. There is no support for
> > OpenBSD in vanilla gcc.
>
> Why not send patches to gcc-patc...@gcc.gnu.org ?
Because it's work. Do you volunteer?
>
>
> --
> Regards,
2013/9/11 Tobias Ulmer:
> Because it's work. Do you volunteer?
Yes, I will, if someone will coordinate me.
First of all, I need a description of what exactly problem is solved
by each patch.
--
Regards,
niXman
___
Dual-target(32 & 64-bit) MinGW c
2013/9/11 Gregor Best :
> If you understood what -fPIC meant, and if you understood the message,
> it should be clear what you have to do.
Let's say you know that I need to rebuild with '-fPIC'...
Then tell me please, why gcc and libgcc are configured and built
successfully, but libgomp is not?
2013/9/11 Tobias Ulmer:
> This is only the first of many many errors. There is no support for
> OpenBSD in vanilla gcc.
Why not send patches to gcc-patc...@gcc.gnu.org ?
--
Regards,
niXman
___
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64
On Wed, Sep 11, 2013 at 02:01:23PM +0400, niXman wrote:
> 2013/9/11 Stuart Henderson
> > "recompile with -fPIC" seems clear to me. If this doesn't mean anything
> > to you, I don't think you should be trying to port GCC by yourself.
>
> I understand that. I do not understand what I have to rebuild
On Wed, Sep 11, 2013 at 02:01:23PM +0400, niXman wrote:
> [...]
> I understand that. I do not understand what I have to rebuild with '-fPIC'?
> GCC?
> [...]
If you understood what -fPIC meant, and if you understood the message,
it should be clear what you have to do.
Might I ask why you are tryin
2013/9/11 Stuart Henderson
> "recompile with -fPIC" seems clear to me. If this doesn't mean anything
> to you, I don't think you should be trying to port GCC by yourself.
I understand that. I do not understand what I have to rebuild with '-fPIC'?
GCC?
/tmp/ccgLXgHL.o?
Or something else?
--
Regar
On 2013/09/11 12:06, niXman wrote:
> 2013/9/11 Stuart Henderson
> > The error message gives quite a good clue:
> >
> > relocation R_X86_64_32 can not be used when making a shared object;
> > recompile with -fPIC
>
> Maybe, but it doesn't speak to me about anything. Can you help me?
"recompile wi
On Wed, Sep 11, 2013 at 12:06:20PM +0400, niXman wrote:
> 2013/9/11 Stuart Henderson
> > The error message gives quite a good clue:
> >
> > relocation R_X86_64_32 can not be used when making a shared object;
> > recompile with -fPIC
>
> Maybe, but it doesn't speak to me about anything. Can you he
2013/9/11 Stuart Henderson
> The error message gives quite a good clue:
>
> relocation R_X86_64_32 can not be used when making a shared object; recompile
> with -fPIC
Maybe, but it doesn't speak to me about anything. Can you help me?
--
Regards,
niXman
On 2013/09/11 10:07, niXman wrote:
> Hi,
>
> I try to build GCC-4.8.1 on pre 5.4 without ports and faced with the
> following error when libgomp is configured:
> configure:3664: checking for C compiler default output file name
> configure:3686: /home/nixman/build/./gcc/xgcc
> -B/home/nixman/build/
On Wed, September 11, 2013 10:07, niXman wrote:
> Hi,
>
> I try to build GCC-4.8.1 on pre 5.4 without ports and faced with the
> following error when libgomp is configured:
Any reason for building it outside ports-tree?
> configure:3664: checking for C compiler default output file name
> configur
Hi,
I try to build GCC-4.8.1 on pre 5.4 without ports and faced with the
following error when libgomp is configured:
configure:3664: checking for C compiler default output file name
configure:3686: /home/nixman/build/./gcc/xgcc
-B/home/nixman/build/./gcc/
-B/home/nixman/prefix/x86_64-unknown-openb
19 matches
Mail list logo
