4:
5: /*top*/
6: extern int t(void);
7: int main(int argc, char **argv)
8: {
9: if (argc > 1000000) {
10: printf("%p", &t);
11: }
12:
13: return 0;
14: }
15: extern void PQconnectdb();
16: int t(void) { PQconnectdb(); return 0; }
/* end */
--------------------
```
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2 Febrero, 2019 09:44 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/9 "2019-02-02T09:44:56Z")
Your computer is having trouble compiling things if you read the first error there.
```
ld: warning: ignoring file /usr/local/lib/libpq.dylib, file was built for x86_64 which is not the architecture being linked (i386): /usr/local/lib/libpq.dylib
Undefined symbols for architecture i386:
"_PQconnectdb", referenced from:
_t in conftest-79115b.o
ld: symbol(s) not found for architecture i386
```
Try searching in Google for the relevant error, above.
---
### Author:  [@Chaboi\_3000](https://meta.discourse.org/u/Chaboi_3000)
#### Post date: [4 Febrero, 2019 09:45 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/10 "2019-02-04T09:45:19Z")
I can’t seem to run `bash <(curl -s https://raw.githubusercontent.com/techAPJ/install-rails/master/mac)`, and it returns an error `sh: syntax error near unexpected token `('`
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [4 Febrero, 2019 15:59 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/11 "2019-02-04T15:59:05Z")
Were any messages output before the error? You’ve not given any indication whether the script ran at all, or threw an error part-way.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [15 Febrero, 2022 17:02 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/12 "2022-02-15T17:02:22Z")
---
### Author:  [@Decorbuz](https://meta.discourse.org/u/Decorbuz)
#### Post date: [15 Febrero, 2022 19:00 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/13 "2022-02-15T19:00:21Z")
Me alegra que este tema se haya reactivado (puramente por coincidencia). Supongo que el problema ha existido durante un tiempo y no se limita a los Mac con Apple Silicon.
Tuve el mismo problema en mi iMac M1 siguiendo la misma guía que tú. @blake fue increíble y logró encontrar una solución para mí. 😀
> Pude hacer que funcionara en mi Mac M1. No estoy exactamente seguro de cuál es el problema, pero esta es una solución que puedes usar.
>
> Desde la primera pestaña de terminal ejecuta:
>
> ```plaintext
> bin/rails server --binding 127.0.0.1
>
> ```
>
> Desde la segunda pestaña de terminal. Cambia a este directorio dentro del directorio de discourse.
>
> ```plaintext
> cd app/assets/javascripts/discourse
>
> ```
>
> Luego ejecuta este comando:
>
> ```plaintext
> ember server --proxy http://127.0.0.1:3000
>
> ```
>
> Luego navega a [http://localhost:4200](http://localhost:4200)
---
### Author:  [@lin\_turing](https://meta.discourse.org/u/lin_turing)
#### Post date: [31 Marzo, 2022 02:03 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/14 "2022-03-31T02:03:34Z")
> [@Decorbuz](#):
>
> ```plaintext
> ember server --proxy http://127.0.0.1:3000
>
> ```
Tengo un nuevo error
---
### Author:  [@blake](https://meta.discourse.org/u/blake)
#### Post date: [31 Marzo, 2022 21:24 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/16 "2022-03-31T21:24:12Z")
No estoy seguro. Ya no deberías tener que usar `ember server --proxy` en los Mac M1. La forma normal ahora es usar una pestaña de terminal desde el directorio raíz de discourse y ejecutar `bin/ember-cli -u`. Esto ejecutará tanto el servidor de rails como el de ember con un solo comando. ¿Puedes intentar eso y ver si funciona?
---
### Author:  [@lin\_turing](https://meta.discourse.org/u/lin_turing)
#### Post date: [1 Abril, 2022 02:36 UTC](https://meta.discourse.org/t/cant-start-localhost-server-file-was-built-for-x86-64-which-is-not-the-architecture-being-linked-i386/108193/17 "2022-04-01T02:36:49Z")
> [@blake](#):
>
> bin/ember-cli -u
¡¡¡¡¡¡Gracias :cara\_sonriente: